alright, I had to revert back to http access until I can get this https situation sorted out.
Here is the problem: I have followed the instructions found here: http://www.isaserver.org/tutorials/Using-2006-ISA-Firewall-RC-Publish-OWA-Sites-Part1.html From the internal side of things when SSL was enabled (on both servers), things were working fine, users could access webmail (internally) via https, the login form would come up, login, and there's there email.
Now external email is really causing a problem here. When I goto https://mail.gelcellcapsules.com/exchange, I get the ISA OWA login screen, if I try putting in a wrong password or username, it comes back with the right things, so I know it's authenticating fine. Now when I enter the correct login info, my firefox gives me a nice error about 'can not redirect'. No matter what I try, I can't get the secure OWA working correctly.
As per our internal setup: 1) sonicwall router/firewall (which IS allowing http, https, smtp, etc) for both incoming and outgoing traffic) 2) ISA (setup as a back-to-back setup) - smtp relay is setup and working fine. 3) Exchange server (on the internal network).
our internal mail name is: mail.gelcellcapsules.com our external mail name is: mail.gelcellcapsules.com I've looked through event logs, ISA logs, and can't find a particular error as to why it's giving me this error. I'm stumped.
I have the same problem. I get a web site that says "ISA Server 2006" when I type in the external address from an external client. Typing in wrong user password with user name brings back the same page with an error, letting my know that ISA server has tried to autheticate the user and it failed due to wrong password. When I type in the right password, I get the 403 error after a few seconds. I was running wireshark pacaket analyzer on both the ISA Server Internal NIC and the Exchange Server NIC and NO packets were exchanged between the two machine except ICMP pings which are setup to validate connectivity only.
is that my ISA server 2006 is part of my AD Domain, and has a DNS Server installed with an AD stub zone for internal name resolution. My ISA is not an edge firewall, so nothing is exposed externally.
Adding "/exchange" to the end of my URL fixed the problem. Created a Link Translation so that users would only have to type in "https://webmail.netsecdesign.com"
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
Printable Version
All Forums >> [ISA 2006 Publishing] >> Exchange Publishing >> Please help with https access 
Please help with https access - 
New Messages
No New Messages
Hot Topic w/ New Messages
Hot Topic w/o New Messages
Locked w/ New Messages
Locked w/o New Messages
Post New Thread