Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm doing a small trial of Exchange Server at work, and I am having a few issues with associated ports on OWA.

I am being asked to use a different port for SSL, so I don't cause any conflicts with existing sites. I modified the bindings in IIS to use 4443 instead of 443 for ssl, and modified the address in the EMC, and it doesn't seem to want to work. Is there something that I am missing?

share|improve this question

Microsoft really really wants you to stay on TCP/443 for SSL, as that's where Outlook and any ActiveSync clients are hard coded to find it. You'll have better luck binding a second IP address to your IIS/OWA server and binding OWA on the new IP.

share|improve this answer
I agree with this. Use separate IPs to avoid port conflicts, don't try to run Exchange on non-standard ports. – Paul Cunningham Feb 3 '11 at 22:25

Restarting the IIS should do the trick.

share|improve this answer
Tried, didn't work. – user58459 Feb 3 '11 at 19:09

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.