local machine name resolution fails when cisco vpn starts

local machine name resolution fails when cisco vpn starts

Post by Dave » Sat, 20 Sep 2003 11:37:44


I have a few XP machines on a home network that can see each other fine
using "net view", UNC paths, Network Neighborhood etc. until I start the
Cisco VPN client on my main machine.

Then I can still ping the others and if I previously used the machines and
their names have not expired from the netbios cache I can still use them.

But if the cache name times out or I start VPN right off I cannot do name
resolution over the local network anymore.

As soon as I bring down the tunnel it all works fine again.

The 192.168.1.x and 192.168.0.x subnets are not sucked into the tunnel but
some how VPN interferes with the subnet broadcast which is how the local
subnet name resolution works.

Any suggestions? I can get around this using static IP's and DNS addresses
on all my machines and a hosts file on the VPN machine but do not want to do
that.

Thanks,
Dave
 
 
 

local machine name resolution fails when cisco vpn starts

Post by BobC » Sat, 20 Sep 2003 23:20:53

"Dave" < XXXX@XXXXX.COM > wrote in


Check the default gateway setting. When using VPN the default gateway may
be at the remote location and that gateway does not have a route to your
LAN.

 
 
 

local machine name resolution fails when cisco vpn starts

Post by Dave » Sun, 21 Sep 2003 00:32:49


BobC, Thanks. With the tunnel up, an "ipconfig /all" shows that I have DNS
and WINS servers from my corp network, but my IP, gateway and DHCP server
still all show my local 192.168.0.XXX network. Dave