Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

I'm currently attempting to connect one of our computers in the office to a client VPN. My development machine is running Windows 7, and can connect and see resources just fine. The problem computer is running Windows XP. They're both within the same network.

Using the same credentials at both computers, the VPN connection (using the built in Windows network connections) works just fine. So far, so good. An IP address is assigned, and comparing both machines shows they're still in the same subnet.

The problem is that the XP machine cannot see ANY of the computers in the client network. I tried a tracert to a target machine on the Windows 7 box, and the first item that comes up is the .0 address. Pinging it gives responses. Trying it on the Windows XP machine, however, comes up with just timeouts.

Trying to trace to www.google.com allows the address to resolve (probably part of the cached resolutions), but results in just timeouts.

I double-checked to make sure that the Windows firewall was not on, and trying to open the settings brings up a notification that the firewall service wasn't running, which leads me to believe that it's definitely not on.

From my best guess, I've managed to connect the XP machine to a black hole of some sort. There's obviously something strange going on, but I'm not sure where I should be looking.

share|improve this question
    
Do you have the same problem when you are not connecting through the VPN? That is, the windows 7 computer just being on the same network as the xp machine, can you access the windows 7 machine via the xp machine? Or is it solely an issue with the VPN? Also, are you running the pro version of windows? –  imtheman Jul 5 '12 at 20:50

1 Answer 1

Turns out the issue is with the client network; I've managed to reproduce the issue several times on multiple machines in the office. I can't maintain a stable VPN connection for even an hour; it will drop the connection entirely, or it will start displaying these symptoms again.

I can work around the problem by disconnecting from the VPN, and reconnect. This does not always solve the issue, but when it does not, I request a switch reboot from the client, and then it works.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.