I have Exchange Server 2003 SP2 installed with OWA running. We are using a Router/Firewall to port the public to our internal private IP address via port 443 for the OWA access. I just added a second server to our AD and moved some mailboxes to the new server. All of the users on the second server are unable to connect to OWA from outside of the office. They are able to use it in the office, but not outside. The OWA automatically forwards them to the new server (creating a url based on the internal server name)and then it times out. Can you please help??? We are using an internal certificate authority. Here is what I have: Exchange server 1: Certificate name = owa.ourpublicdomain.com connect to owa = owa.ourpublicdomain.com/exchange The internal server name is actually RST12345.OurPlace.Setup.local Exchange server 2: Certificate name & server name = RST54321.OurPlace.Setup.local When a user on the second server connects to owa.ourpublicdomain.com/exchange, they are redirected to RST54321.OurPlace.Setup.local/exchange This is an internal domain and server name, so it cannot resolve for the user publically. What can I do to change this behavior, or is this by design. I have also tried to allow the second server to run independently with its own public address and port mapping owa2.ourpublicdomain.com/exchange and it doesn't work. Thanks