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 Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Cannot access Default Web Site from Internal network

Status
Not open for further replies.

pogi05

IS-IT--Management
Jul 12, 2006
71
US
Setup: Windows 2003 server w/ Exchange 2003 (I know it's not a recommended config but it's what was here when I arrived); SonicWall Firewall device set to forward port 80 and 443 to Exchange server; RPC over https configured; OWA configured and works externally; OMA and PocketPC ActiveSync works only over externally over the internet.


Problem: We are unable to access OWA or use PocketPC ActiveSync while on the internal network.

In an IE Browser from the internal network, comes up with "Page cannot be displayed" "DNS Error" "Server cannot be found".

In an IE Broswer from the external network, works great.

When pinging externalFQDN from the internal network, the domain name is resolved to our external IP as it should.

The only recent changes have been to our DNS. I had originally put in a externalFQDN forward look-up zone, with a A name entries of mail.externalFQDN and but that caused a lot of problems with e-mails and other programs and we had to delete it.

**Where is the hang-up with accessing the default web site internally?? If the DNS is resolving correctly internally, what's stopping it from connecting to the server?


Thanks much,
Chris
 
I assume your windows 2003 server is on your local lan with a private ip and you have your firewall configured to translate a public ip to private ip. If this is the case you need to add an A record on your internal dns server for the web server using the private ip address.

Jim W MCSE CCNA
Network Manager
 
case closed finally!

I couldn't exactly create a DNS A record because it would create problems with e-mailing and reaching our other offices but I had put in a local loopback rule that would translate any service outgoing from the Lan Subnets to the Wan IP:

Original Source: LAN Subnets
Translated Source: Primary WAN IP
Original Destination: Primary WAN IP
Translated Destination: ServerPrivateAddress
Original Service: Any
Translated Service: Original
Inbound Interface: LAN
Outbound Interface: Any

**This was done using our SonicWall firewall/gateway

Thanks for the posts
 
Just add an A record in DNS called www and point it to the internal IP address of your web server
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top