Proper config for incoming SSL to Exchange server

[sduffey]

If I want SSL connections passed to my exchange server (OWA and Outlook Anywhere)what is the proper config of Wingate to allow me to do so without breaking the SSL connection?

[sduffey]

To clarify I can get OWA coming in using a tcp-mapping form a non-standard port to 443 on the backend. Howver with Outlook Anywhere it won't accept a url like this https://your domain.com:2999/owa

It only will accept something along the lines of https://email.yourdomain.com How can I manage to do this securely with Wingate without having the whole world knocking on port 443 on my Exchange 07 server?

[adrien]

Hi

The default port for https is 443, so it's the only port you can use if you can't specify a port number in the URL.

You can use policy in the TCP mapping proxy however to only allow certain IPs to access the OWA server if you know the IPs. Otherwise, you may be better off using a redirect in Extended Networking Port Security to allow the exchange server to learn the client IP (don't translate source IP), then you can apply IP-based security policies at the exchange server.

Regards

Adrien

[sduffey]

Hmm I am not familiar with that feature in Exchange, I'll have to look into it.

I imagine that most admins that are looking to use Outlook anywhere are in the same boat (having 443 banging on their server)

[adrien]

if you can get OWA to run on another port, you may be able to map that same port through to OWA.

It then should be generating links in the pages it sends back with the port number in it.

[sduffey]

OWA via https worked on another port, sort of. It would work for awhile and then stop.