I've set up OWA with Exchange 2003, and ISA 2006. I can see the OWA page when I go the the external web site from outside my network. I can get the log in internally using https://servername/exchange, but when I try to reach the external address while I'm in my network, I get "the requested URL could not be retrieved." I even added it to the hosts file on my workstation.
with ISA Server 2006 it turns out that it is possible to access from an internal/perimeter host the published instance of a Web server through HTTP and HTTPS. This seems to work if the internal client access the web site as a Web Proxy, or a Firewall client or even as a SecureNAT client.
Of course, you should make sure there is an access rule in place allowing the client anonymous access to the Web listeners on the ISA external interface. Also, if ISA is doing name resolving on behalf of the client (Web Proxy and Firewall client), the used FQDN must resolve to the Web listeners on the ISA external interface.
< Message edited by spouseele -- 9.Dec.2006 7:20:56 AM >
I don't have any internal networks set up on the ISA server. The ISA server is in the DMZ of my network, a PIX being the firewall. We just have the ISA to publish OWA. Since I didn't set up any networks, I think it sees the traffic from my internal network as external because it doesn't recognize it. Is that correct?
I'm having trouble logging in externally through the ISA server. I was hoping to access the web address from my internal workstation to test the site. Otherwise, I have to drive to the coffee shop across the street to access their wireless network.
I think I may be a certificate problem. In my first attempt to set up OWA, I had already created a certificate on my Exchange server, and copied it to the ISA server. When I couldn't log in, I deleted everything and started over using Tom's step-by-step instructions. However, when I recreated the certificate following his instructions, three appeared. ? Was that supposed to happen?