Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

OWA - unable to access externally, internal access OK

Status
Not open for further replies.

Selina8

IS-IT--Management
Jan 11, 2006
2
GB
Hi all,

I am newbie and have just joined this forum.

I cannot access webmail from my Exchange server externally but can access webmail internally.

The server is pingable from other subnets and the DNS record and IP settings are all correct. No changes have been made to the firewall etc therefore I am unsure where else to look.

I know that you need to check certain IIS services, can someone please tell a newbie what the next things to check are. My knowledge of IIS is not that great.

Thanks

Selina
 
If you have a firewall you might check to see if Port 80 is being blocked on the Wan interface.

If you are using one of the private IP address ranges internally you may also need to setup a NAT rule to point to the IIS server.

What Version of Exchange are you running? If you could please post more information regarding your setup it would be helpful.


Thanks JC
 
Hi JC

Thanks for your reply. I am sorry I should have mentioned which version of Exchange I am using Exchange 2000.

I have checked the settings on the firewall and port 80 is allowed for WAN traffic.

Any other suggestions would be really great.

Cheers

Selina
 
Do you have a static route set up for an external IP address to point to that of the internal IP address of the server? You need to do this on the firewall.
 
Selina
lengoo is correct if you are using a private IP address class for your LAN you will need to setup a NAT (Network Address Translation) rule on your fire.

The private IP Address ranges are as follows.

192.168.0.0 - 192.168.255.255
172.16.0.0 - 172.31.255.255
10.0.0.0 - 10.255.255.255

The private ranges cannot be routed on the internet and need to use NAT to make communication to the internet happen.

However if you are using public ip addresses your Internal DNS server should resolve the name to ip address fine.

Have you tried to ping by the FQDN and IP address of the OWA server from the WAN side?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top