DNS order in XP on a VPN connection (not using VPN DNS servers)

Hi,
We have a bunch of clients running XP who connect to our 2003 VPN server.
Previously this was working fine but recently, when they connect the DNS
servers dont resolve the private network names.

When doing an IPCONFIG /ALL our DNS servers are listed against the VPN
connection, but when running an NSLOOKUP it keeps querying the DNS server
belonging to the ISP.

I have seen a few articles about mucking about with the registry and such,
but I have worked in IT for a long time and dealt with a lot of different
networks and never hit this issue (DNS always just works when connecting to a
VPN).

Is there anything I could check from the server end, or is this limited to
client configuration?

Thanks in advance for any light you might be able to shine on this problem.

Hi Bob,
When doing IPCONFIG /ALL computers list their local nic with local DNS
servers and the VPN adapter with the proper DNS servers for the work network.

However if I do an NSLOOKUP, the computer will look at the ISP DNS server..
BUT if from the command line I ping a work server by name, it resolves the
name and pings it properly SO LONG AS the DNS suffix is specified in the TCP
parameters of the VPN connection.

We do not run Windows DHCP, the RAS server hands out IP addresses from a
specific range.. this might be why we are seeing this problem?

Any thoughts on this?

Cheers!

Hi Bob,
When doing IPCONFIG /ALL computers list their local nic with local DNS
servers and the VPN adapter with the proper DNS servers for the work network.

However if I do an NSLOOKUP, the computer will look at the ISP DNS server..
BUT if from the command line I ping a work server by name, it resolves the
name and pings it properly SO LONG AS the DNS suffix is specified in the TCP
parameters of the VPN connection.

We do not run Windows DHCP, the RAS server hands out IP addresses from a
specific range.. this might be why we are seeing this problem?

Any thoughts on this?

Cheers!