Welcome to WebmasterWorld Guest from 18.104.22.168
Forum Moderators: phranque
I just a friend, and old client, call me saying that she can't get to her site, and that a customer had come in and told her that he couldn't get there either.
I then went to the site, and got there no problem. I then typed in the URL, including the www, and couldn't get to the site. Then a minute or two later, I went back and checked it again, and I could get to the site.
I called her back and told her that I could access the site, and to check if she could get there now. Still couldn't get there. I asked a co-worker if they could get to the site, and they could access it.
I pinged the site.....everything seems okay.
The person who can't reach the site is in a different state, using a cable modem.............does anyone have any ideas what is going on?
sounds like a server issue.. but could be a router problem, jumping up and down. Keep an eye on it - and if it persists much longer contact the hosting company.
are there any other domains that you know of on the server? are they having the same problems?
2) is the site setup properly? I ask due to it not showing up for www.site but showing for //site
please understand I am guessing here since I only have what you posted to go by..
have you added any new sites to the server? this could have jacked with the mapping.. (virtual hosted right?)
there is a down router somewhere, in that case all you can do is wait for it to be fixed.. in my experience this happens rather quickly
or.. hmm.. can you email me the link? I will see if I can get it.
You can verify this by running a tracert to it periodically, say once an hour. There are tools out there that can agregate several traceroute records and tell you the delays even the route changes.
If the ISP was messing with the DNS and sent some new records or resent them this could possibly cause problems but not likely.
You can detect this unless you monitor each port with a tool, or sit on top of the monitor. You might consider an SNMP monitoring tool or some log server tool that monitors the health of the box.
Can't do didly about this. If this is a big cheese then you can ping/traceroute their public IP for a while and watch dropped packets, and route changes, but you might just get banned. It won't tell you anything about the connection to the server UNLESS you do this tracing from the server.
See above. You can run dig, and find out if their records were updated recently. Can ping the DNS servers, and see if they are acting up, but again can do didly.
"We have added many sites to the co-located server over the past year. If this was the problem, how would I be able to reach the site, and not her? Wouldn't it be down for both of us? "
something could have messed up just that one record... it's not common but it does happen, took us forever to figure it out when it happened to us, fixing the record solved the problem...
For the record - I cannot get the site either, not via browser or tracert.
The next afternoon he was able to reach the site normally.
How long has the client been unable to reach her site? Has anyone else had problems?
Try to soothingly and patiently explain the idea of "temporary network problems" to her if it's only been a day or two. Also, give her instructions for doing a treaceroute from her location.
you said that your client could access other sites you host fine, but it was just one site that had problems. well, try this cuz it worked for me. simply create another site, directory, permissions, and all. and then transfer all the files and settings from the "bad" site to the new one. hope this helps. make sure that u use different name for the site, and even the parent directory name should be different. if that works, then if u need to, change the names back to original.
i got a question now: how do u fix routing problems? how do u check the routing tables?
Assuming that this is the problem, the differing routes used by different access methods may account for the wierd access errors
Worth a shot