Getting OWA to work when 443 is already in use
Posted on 2011-02-21
Got an SBS 2003 machine on a network where port 443 is already in use by a LOB application. After discussing changing the port that SBS uses for OWA, people here on EE decided that wouldn't be a good idea, as it would break some of the key features of SBS. So, the suggestion was made to get a 2nd external IP address that we COULD forward 443 on - which I have done.
So now, I have a second IP adress, with a second router, on which I have forwarded port 443 to the Exchange server The primary router on the original IP address NAT's to the 192.168.x.x range, so I set the second one to NAT to the 172.16.x.x range, and I have assigned a 172.16.x.x address as a second address on the exchange server NIC.
Unfortunately, this is not working. I'm THINKING it has something to do with needing to set up a Route for the replies on the 172.16 net to get back out to the appropriate router, but A) I'm not sure that's it, and B) I Have no idea how to do it.
If I add a 172.16 address to machine on the internal LAN, it works fine from the internal machine, but I'm suspecting that has something to with the fact that those machines are also still on the 192.168 LAN and are getting responses that way.
Thoughts? Help? Suggestions???