Outlook Web Access to Exchange Server 2003 via SonicWall TZ 170

I am trying to get Outlook Web Access (OWA) to work in order to access mailboxes on an Exchange 2003 Server.  This Server is on a small Windows 2003 network behind a SonicWall TZ 170 firewall.  Internally on the network, OWA works fine by going to the address, http://servername/exchange.

Outside of the network, OWA does not work when going to the address, https://publicIPaddress/exchange, where "publicIPaddress" is a public IP address that is set as a one-to-one NAT address that points at the private IP address of the Exchange server.  Also, http://publicIPaddress/exchange does not work as well.

On the SonicWall TZ 170, I have a Firewall - Access Rule for Source (*) to Destination (private address of Exchange Server for the Service HTTPS

Any thoughts as to why I can't get OWA to work?

thanks in advance,
Who is Participating?
Nenad RajsicConnect With a Mentor Commented:
your example links show http: and then in your last paragraph you say that your firewall rule says https:
is https configured on your exchange? what is the port number that you are forwarding to your exchange server is it 443 or 80?
mbarsheshat01Connect With a Mentor Commented:
to test access from outside, set the hosts file on that machine to point the the external address of the server. By adding an entry to the hosts file:
notepad c:\windows\system32\drivers.\etc\hosts
and add this line: servername
where is the external IP address of your server.
test the entry in the hosts file by pinging the name and see that it resolves correctly. After this you can try and access your owa from your web browser by
 http://servername/exchange or  https://servername/exchange.
if this works than the problem is with your IIS configuration. Configure the website to accept from any address and not just the internal name.  Let me know if this is the case and if you need instructions on how to configure your IIS. Good Luck!
Shreedhar EtteConnect With a Mentor Commented:

First the Sonic Fire wall logs and see whether the request for the OWA reaching the firwall or not.

Hope this helps,
cbentsenAuthor Commented:
I figured out that I was missing a Firewall Access Rule for port 80 traffic to get to the Exch server for OWA.  All three posters added to me figuring out what was the issue.
cbentsenAuthor Commented:
I was missing a Firewall - Access Rule to allow port 80 web traffic to get to the Exch server for OWA to work.  
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.