06-10-2005 09:09 AM - edited 02-21-2020 12:12 AM
I have an XP Pro notebook with Cisco VPN 4.6 loaded on it. The VPN appears to connect fine, but once it's connected, I cannot ping anything on the network, or access any resources. Also can't access the Internet. Without the VPN turned on, network access is fine.
I'm stumped! Any ideas??
Thanks,
Walt
06-13-2005 09:34 AM
Has any other pc connected to the vpn successfully? If yes, do they see the network? Are you running XP SP2? Is anyone else?
06-13-2005 09:48 AM
We have several other VPN users who are not having a problem. They can see the network just fine. They are all using XP Pro; SP-2.
The problem machine is also XP Pro; SP-2. I have turned OFF the Windows Firewall and that made no difference. I have also had a network engineer verify that our VPN is working properly. At this point, I think it's a Windows issue, but still don't know what to do about it.
Thanks,
Walt
06-14-2005 05:08 AM
So you cannot ping anything through the tunnel, even by ip? I would enable debug logging on the pix and crank up logging on the software vpn client. The pix has a debug icmp command as well, which you can use to watch icmp traffic through the pix
06-14-2005 05:49 AM
I had our engineer check the debug logging while I tried to connect. He could see the connection being made; everything looked good from that end. I think at this point it's a Windows problem. I'm now researching from that perspective.
Thanks for your input.
Walt
08-05-2005 09:22 AM
Walt...have u figured this out yet? I'm in the same boat. I have one 4.7.1 3030 working fine but I'm working on a new on and I get logged in....and authenticated but thats about it. Can ping anything by ip or dns. I've compair the configs of both 3030s and they are pretty much the same.
BB
08-16-2005 04:07 AM
I would look at the routing table on your local machine when you are connected to the VPN and see if the Virtual adapter and the Local adapter have the same metric. If they are the same you will be able to connect but not pass traffic. Here is the bug ID and info.
CSCea65393
Symptom:
Using the 4.0 VPN Client with the virtual adapter (Windows 2000 or Windows XP) in a multiple NIC
environment, the client may not pass data while connected.
Conditions:
When the client PC has multiple network interfaces and the default gateway is on the non-VPN
interface the default gateway metric will not be incremented. This may result in data that is
bound for the VPN going to the non-VPN default gateway and getting dropped. This problem is
clearly identifiable by looking at the routing table while a VPN (All Tunneling) connection is
active where the two default routes appear with equal metrics.
Workaround:
The easiest workaround is manually increment the local interface metric by '1'. Once this is done
the clients virtual adapter will have a lesser metric and be the best route.
08-17-2005 08:33 PM
please post the config
08-18-2005 04:09 AM
Hello. This issue occurred 2 months ago, so I don't have any configs to post. I ended up reloading Windows XP to fix the problem.
Thanks,
Walt
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide