Actions: Add Comment
29 May 2009 17:02 UTCFri 29 May 2009 - 5:02 pm UTC
I know a lot about web programming, but not a lot about networking. A client of mine had their web host changed and they can no longer view the site internally. Can you give me a few options as to why this might be happening so I can troubleshoot it. I know a bit about dns.
29 May 2009 17:19 UTCFri 29 May 2009 - 5:19 pm UTC
Just to clarify, are you saying that when your client, from their in-house computers, types in their own url, they can't access their site? What do they get instead...a standard 404 error?
Also, when did they make the switch to a new web host? It's not unusual for the switch-over to take a full 24 hours to propogate itself, during which time, all sorts of bugs can pop up. These usually resolve without any action after just a day, though.
Let us know a bit more detail on what's going on.
29 May 2009 17:26 UTCFri 29 May 2009 - 5:26 pm UTC
> Just to clarify, are you saying that when your client,
> from their in-house computers, types in their own url,
> they can't access their site?
Yes, that is exactly what I am saying.
I just asked them if they get a 404 or not. So I will let you know asap.
They made the switch to the new host two weeks ago. So its prob not a propagation error.
29 May 2009 18:52 UTCFri 29 May 2009 - 6:52 pm UTC
Ok, my client told me what they get when they try to access their site internally. They said it takes a long time and then they just get a message saying "oops the link appears to be broken".
She sent me her screenshot of the error page. I put it up at xaevir.com/broken-link.jpg
The site they are trying to view is equityretailbrokers.com
29 May 2009 19:15 UTCFri 29 May 2009 - 7:15 pm UTC
At least they aren't losing traffic. The site appears to work fine from the outside.
Something in their system must be directing users to the old host. I don't know how large a network your client has, but have they done a complete reboot of the system, and cleared cache, cookies, history, and temp files since the change over?
Also, make sure browsers are configured to check for newer versions of cached pages with every new visit. In IE7, this would be under the Browsing History settings in the Tools menu.
A colleague of mine also notes the following (thanks, mt): "If the site is normally reachable from other ISPs but not the "in-house"
connection, it suggests some sort of hosts file exists in the internal
network that is directing requests to the former dot4 IP address and thus
circumventing a DNS lookup of the new Web host address."
Let me know if any of that helps.
30 May 2009 14:29 UTCSat 30 May 2009 - 2:29 pm UTC
Try the instructions here -
WWW FAQs: Why can't I access my home-hosted website from my own computer?
Will look forward to hearing if that solves it,
1 Jun 2009 17:57 UTCMon 1 Jun 2009 - 5:57 pm UTC
Thank you guys. You were all supremely helpful. As always, uClue has always been good to me. My client is fine now.
1 Jun 2009 18:33 UTCMon 1 Jun 2009 - 6:33 pm UTC
If you can, let us know which particular comments helped you solve the problem, so that the appropriate researcher can collect the fee for an answer.
If it was a combination of advice, let us know that as well, and we'll figure it out amongst ourselves.
1 Jun 2009 18:38 UTCMon 1 Jun 2009 - 6:38 pm UTC
davidsarokin, and zzzreyes helped the most. But the others did contribute some.
1 Jun 2009 21:18 UTCMon 1 Jun 2009 - 9:18 pm UTC
Thanks, xaevir. Glad we could be of help.
Actions: Add Comment