Q:
Windows XP ping computer name resolves to VPN IP instead of local address
In a windows XP professional, connected to a fortissl VPN.
The machine is connected to a router that gives local addresses with DHCP.
The machine is not in a domain. No domain controller.
From <computer name>, ping <computer name> gives the address of the VPN virtual adapter (when connected) instead of the IP of the local network. Note I ping from the SAME MACHINE, so it's an internal resolution.
Defining in hosts or lmhosts does now work.
Any ideas?
The machine is connected to a router that gives local addresses with DHCP.
The machine is not in a domain. No domain controller.
From <computer name>, ping <computer name> gives the address of the VPN virtual adapter (when connected) instead of the IP of the local network. Note I ping from the SAME MACHINE, so it's an internal resolution.
Defining in hosts or lmhosts does now work.
Any ideas?
ASKED:
Jan 8 2009 10:45 AM GMT
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
A:
RATE THIS ANSWER
-1
Click to Vote:
-1
Click to Vote:
0- -1
When you are connected to the vpn, try to type in a command line the instruction "route print" and locate de "default gateway" line (near of bottom of the output). Your default gateway maybe be the same as the gateway for the red 0.0.0.0 (near of the top of the command output). If so, then delete that route using the sentence "route delete 0.0.0.0 x.x.x.x.x" where x.x.x.x is the default gateway seen in the "route print" command output.
If this don't change your situation, try to change the metric of your network devices (phisical and virtual) giving the prority 1 to your phisical adapter.
Best regards.
Browse IT Answers by Topic
