Unable to connect to specific ip address -- but only from one location
Posted on 2004-10-13
We have a new client (about a week) who has transfered their web hosting over to us. No problems at all the last week.
Today, about 15 minutes before closing time, we received a call that they were unable to connect to their admin area (receiving dns error in browser). We checked and all was well for us. Logged into one of their servers via terminal services and sure enough, could not connect to our webserver. Tried connecting to specific ip adresses was a no go as well. Able to connect to one ip address up and down so no problems there. Called the NOC and no problems there. Using Terminal Services, I connected to 5 other clients, spread out around the country and tried hitting the website in question and no problems there. Used AOL to receive new vpn and no problems there. Tried a few other vpn's and no problems there. Got to thinking maybe it was something up with time warner in their area (their isp). Called a couple of businesses in the area that are friends and that use TW and had them pull up the site in question -- no problems at all. So now we're down to it being their office...
Had them reset their modem -- but the girl didn't get the part about turning it back on and she went home. So tomorrow morning, I'll see if things are back to normal and if not, plan to do a /flushdns and poke around with nslookup. I'm thinking that's not going to fix anything though, as the problem is office wide, not just one specific machine.
Does anyone have any ideas as to what this could be? Is there something on the machine providing internet access to the rest of the office that could somehow be blocking a specific ip address and if so, where would I look? Any other ideas, no matter how trivial?