DNS server search order when connected to RRAS

[Guest]

When a Windows XP client connects to VPN, it still uses the Internet
connection DNS server as the primary DNS server instead of the DNS servers
sent by RRAS.

This creates a problem if the same hostname is registered with different IP
addresses on the intranet vs. internet. It also creates a problems with many
wi-fi access points because they always return a positve DNS response to
redirect web-browsers to their login page.

Is there a way to force XP to use the VPN issued DNS servers first?

Alternatively, is there a way to block other routes and only allow the VPN
route?

 

[Robert L [MS-MVP]]

Make sure RRAS has correct DNS setup. Also check "use default gateway on remote network" these links may help,

routing issues on vpn Or check "Use default gateway on Remote Network" on VPN connection. Can't access the remote network from VPN clients. Symptoms: Your VPN client can ...
www.chicagotech.net/routingissuesonvpn.htm

Troubleshooting DNS Which DNS does a VPN client use Which ports are used for DNS Why am I getting 127.0.0.0 as the DNS. Why do I have to point my domain controller to itself ...
www.chicagotech.net/dnstroubleshooting.htm



Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
When a Windows XP client connects to VPN, it still uses the Internet
connection DNS server as the primary DNS server instead of the DNS servers
sent by RRAS.

This creates a problem if the same hostname is registered with different IP
addresses on the intranet vs. internet. It also creates a problems with many
wi-fi access points because they always return a positve DNS response to
redirect web-browsers to their login page.

Is there a way to force XP to use the VPN issued DNS servers first?

Alternatively, is there a way to block other routes and only allow the VPN
route?

 

[Guest]

this problem have bug me for the past 2 years.
and after spending 4 hours reading on this topic, i think i have finally the
solution.

this have fix the problem and is 100% BETTER then /etc/host fix or putting
your remote site's DNS in your lan dns setting.

http://support.microsoft.com/kb/311218/en-us

this have work well for me.

let me know and spread the word. too many people suffer from this, and i
don't think Microsoft have word it correctly on the knowledgebase. I sure
hope Visita won't have this behavior.

-Louis