Re: Persistent VPN name resolution problem

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Jerry Paquette (nospampaquette_at_uwo.ca)
Date: 03/12/04 

Date: Fri, 12 Mar 2004 16:10:59 -0500

I finally found the solution to this problem last night and I am posting
this to try to spare anyone else the difficulty I've had in arriving at
a solution. On the DNS tab of TCP/IP properties>advanced is a "Register
this connection's addresses in DNS." By default this box is checked.
It apparently places the fully qualified domain name of the client XP
machine in the DCHP cache of the server--and it appears that (at least
with Win2k SP4 the cache is searched before WINS). Unchecking the box
on the XP clients eliminates the problem. Ping and winsock apps like
terminal server work fine from server to client over a VPN using just
the client NetBios machine name once this box is unchecked.

I hope this eventually helps someone else.