When a user access OWA internally, what do they actually put in the URL?
Is is just the host name like: http://webmail/Exchange ??
Or is it a FQDN like: http://webmail.domain.com/Exchange ??
If you are only using the host name, my guess is the gateway does not know how to resolve the host name directly and needs to append a domain search suffix. You can do this by editting resolv.conf and changing/adding the line at the end to:
Mine looks like this:
### END AUTOGENERATED CONFIG
search lordchariot.com lordchariot.local
That said, internal traffic to servers that the clients can route to in the first place generally should not be proxied at all. Most people will put exclusions in the browser settings so internal hosts do no get proxied.
When a user accesses OWA internally they enter the FQDN.
For some reason it was configured that you could only access OWA internally by going through ISA, hence this rule. It was put in place by our current network admin's predecessor. I will need to check with him again to see if he knows why it is setup this way.
Bringing this back up again.
Still no luck. I have tried excluding the webmail address (https://webmail.domain.com/Exchange) in the browser from going through the proxy.
Is there any way of redirecting a single address to go through another proxy? I was wondering if I could just redirect this address to go the the proxy at 192.168.1.6:8080 (our ISA server).
Try using wildcards like *.webmail.domain.com*
Also since it's HTTPS, is your SSL scanner turned on?
Thanks for your suggestions. I had already put the wildards in before, but that doesn't make any difference.
Also we aren't using the SSL scanner, but I tried turning it on to test and got the same result.
Feeling kind of dumb right now, but good news is that I worked out what the problem was.
For some reason I needed to add the FQDN to point to the internal IP address in the Hosts file on the gateway. I thought this would have already been handled by our internal DNS, but didn't seem to be the case.
Hi, can you send me or show the entire process you used to deploy OWA through the Webgateway?