[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1068
  • Last Modified:

OWA accessible from internal network, not externally

I am running Exchange 2007 on MS Server 2003 R2 Standard - both fully updated.  Due to another software failure, I had to uninstall all .Net components.  Concurrently, I installed Exchange 2013 on another server, which required some changes to the domain.  During this time period OWA stopped working (having previously worked fine for years).  After many attempted fixes, I uninstalled and reinstalled the Exchange Client Access Role and IIS.  I can now access OWA internally via https://servername/owa, but cannot access OWA externally via https://mail.publicname.org/owa.  I have a SonicWall TZ215 firewall, but no changes have been made to it during this process, so I do not believe it is a firewall issue.  I can ping the public IP and the mail.publicname.org externally.  Attempting to access OWA externally gives me an error:  "Internet Explorer cannot display the webpage."  I can telnet to ports 80 and 443 internally, but not ports 80 or 443 externally, which MAY be a firewall issue.  I suspect this is an IIS issue.
0
sksaathoff
Asked:
sksaathoff
1 Solution
 
kpoinealCommented:
If you can access it internally it is not an IIS issue. This is a routing issue. Check all of your firewall rules and make sure they are pointing to the right ip of the exchange server.
0
 
sksaathoffAuthor Commented:
This was a firewall issue, with a NAT policy needing to be created to pass through traffic on 443.  Why it wasn't needed before and/or how it got deleted off the firewall, I'll never know.
0

Featured Post

Receive 1:1 tech help

Solve your biggest tech problems alongside global tech experts with 1:1 help.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now