unable to access owa externally

I am able to access email through my owa client sitting on my local network but only by the local ip address.  Not sure why, but I can't access the site by name nor can I access the site externally by public IP.  I have checked everything. My external DNS records are correct, I can resolve the name to the correct ip address and my firewall is open on port 443 as needed.  I'm not an IIS person, but everything is pointing to it as the problem.  How does IIS advertise itself?  How does the firewall know that https requests need to go to the exchange server?
Who is Participating?
SembeeConnect With a Mentor Commented:
IIS doesn't annouce  itself, you have to send the traffic to it.

First - the internal and external DNS records need to be different.
Internally you need your clients to look at the internal IP address of the Exchagne server. This is achieved by adjustign the DNS as required.
If you are using a generic name for OWA (mail.domain.com for example) but the server is called something else (server1.domain.com) then add an additional entry in to your local DNS for mail.domain.com and point it at the IP address of the Exchange/OWA server.

Externally the clients need to be pointing at the external IP address of your connection. If you have mutiple IP addresses then it needs to be the one assigned to the Exchange/OWA server.

This is known as split DNS.

Confirm that it is working as you like internally, and then move forwards to get external to work.

Next. Your firewall.
You are probably using NAT/Port Forwarding. Configure the firewall to forward requests on port 443 received on the relevant external IP address to the internal IP address of your Exchange/OWA server.
You haven't said which firewall you are using, but if you have already setup forwarding for port 25 (SMTP) then I would just copy the configuration and change the port to 443.

sunny10Author Commented:
Your line of questioning got me started on the right track, when I went back and checked the router I noticed that the port forwarding had been set up incorrectly.  Once I fixed the IP address everything worked.  Thanks for your help.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.