smoakin
asked on
unable to access external website from inside corporate network
Running Windows Server 2008 R2 with AD. Website is externally hosted. Everything was working fine until our external nameservers were deleted. We recreated them and reentered all the DNS records. External devices can access the website with no problem. Devices inside our network can't find the website. Pinging from any internal computer resolves to the correct IP, but the website still will not come up. No other changes to our internal DNS server, firewall have been made. Any help at all would be appreciated!
ASKER
I ran a tracert from both inside and outside the LAN to the website URL. Both were almost identical except the tracert from inside the LAN timed out at the end. The external tracert had the final hop to the web site IP.
Trying to access the website from inside the LAN using the IP address fails in the same way. Trying to access the website from outside the LAN brings up a default error page, presumably from the hosting server.
Trying to access the website from inside the LAN using the IP address fails in the same way. Trying to access the website from outside the LAN brings up a default error page, presumably from the hosting server.
If this is a public web site can you share the URL?
When you try to access the site are you using a URL like http://www.mysite.com or http://mysite.com.
If you do an nslookup on the URL, I assume it does not resolve, correct?
Try "telnet URL 80"
hit a few characters and carriage returns.
Do you get a response something like...
HTTP/1.1 400 Bad Request
Content-Type: text/html; charset=us-ascii
Server: Microsoft-HTTPAPI/2.0
Date: Tue, 29 Oct 2013 10:09:58 GMT
Connection: close
Try the same using the ip address.
When you try to access the site are you using a URL like http://www.mysite.com or http://mysite.com.
If you do an nslookup on the URL, I assume it does not resolve, correct?
Try "telnet URL 80"
hit a few characters and carriage returns.
Do you get a response something like...
HTTP/1.1 400 Bad Request
Content-Type: text/html; charset=us-ascii
Server: Microsoft-HTTPAPI/2.0
Date: Tue, 29 Oct 2013 10:09:58 GMT
Connection: close
Try the same using the ip address.
ASKER
I hope you don't mind but I would rather stay under the radar on the website URL.
I've tried both www.mysite.com and mysite.com. Both fail inside and both succeed outside the LAN.
nslookup on the URL is successful from both inside and outside the LAN.
telnet to the website URL failed from both inside and outside the LAN
telnet to the website ip address from inside the LAN failed to connect
telnet to the website ip address from outside the LAN was a little different but also eventually failed.
I've tried both www.mysite.com and mysite.com. Both fail inside and both succeed outside the LAN.
nslookup on the URL is successful from both inside and outside the LAN.
telnet to the website URL failed from both inside and outside the LAN
telnet to the website ip address from inside the LAN failed to connect
telnet to the website ip address from outside the LAN was a little different but also eventually failed.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
This external website is on a DMZ in your LAN? maybe you have a routing problem between LAN and DMZ.
ASKER
I will have to try these options when I get to the office tomorrow.
The website is not on a DMZ.
The website is not on a DMZ.
ASKER
As it turned out, it was a problem with the website hosting company. They made a correction on their end and the problem was resolved.
Can you access the website using the ip (http://x.x.x.x) instead of the URL?