XP VPN - Force nslookup to use DNS servers supplied by RRAS?



Hello -

I've got a peculiar problem. Quick overview of the setup: Windows XP Pro
client connecting to office LAN via Windows VPN connection (PPTP), with "use
default gateway on remote network" unchecked. Typically, in this
configuration, the client will attempt to connect to a server on the LAN by
name, and a DNS lookup will occur - first to the client's primary internet
connection's defined DNS servers, and since that usually fails (due to the
FQDN being of an unregistered domain like machine.domain.local or something
like that), a DNS lookup is attempted using the DNS servers supplied by the
RRAS server, which provides the correct LAN IP address for the server, and
connectivity can be established.

Well...a few of my users, who frequently use the Windows VPN connection to
connect to the office to connect to the Exchange server, gain access to
network shares, etc., began having an issue whereby their ISP's DNS servers
had begun returning a PUBLIC IP for any host they were attempting to look
up - even those with fake names. Basically, you could type nslookup
blah.bogusfqdn.com (which I have checked, and doesn't exist) and it would
happily return a public IP (I don't know which IP it acutally is, possibly
their ISP DHCP assigned IP). While the client is still able to gain basic
TCP/IP connectivity to the LAN, in essence, they've lost the ability to look
up any host on the LAN.

It seems to be an SBC DSL problem specifically, as users who have, for
example, Comcast bandwidth do not experience the same behavior.

I know that we can counteract this by re-checking the "use default gateway
on remote network" setting, but our office bandwidth isn't the greatest, so
we don't get the best results with that. Is there any other way to
automatically force the client to look up hosts that match a certain domain
name (i.e. our AD domain) to use the DNS hosts specified by the RRAS server?

Thanks!

- Eric McWhorter


.



Relevant Pages

  • Network Admin-Myrtle Beach, SC
    ... SofTec I.T. has a terrific permanent opportunity with a premier client ... for a Senior Network Administrator. ... Configures and maintains the organizations LAN server and LAN ...
    (comp.dcom.sys.cisco)
  • Re: Cant browse the network over VPN?!
    ... running WINS on the LAN, WINS will have an entry for the Domain Master ... If the client has the correct WINS address, ... > server, and you attempt to connect to a computer using a PPTP/VPN client, ... > opening Network Knighthood. ...
    (microsoft.public.windows.server.networking)
  • Re: SBS 2003 R2 Install
    ... so what I'd planned was to set up the new sbs box exactly the same ... each client, then log off each client, then just remove the old sbs box ... the lan and replace it with the new box. ... 2003 server setup, ensure it is named exactly the same as your original ...
    (microsoft.public.windows.server.sbs)
  • Re: How to network home and office without terminal services??
    ... The browser service does not use DNS. ... the remote client). ... >> As Phillip has already pointed out, you can't browse the remote LAN ... > On the server side port 1723 is forwaded from the router to the ...
    (microsoft.public.windows.server.networking)
  • Re: smbclient timeout, file truncated / 9.1 Pro (was Re: libpopt.so.0 conflict...
    ... >and the OS/2 machines on the LAN. ... NETBEUI was invented to allow windows clients to use an OS/2 server. ... 9 buffer small read and write requests until the buffer is full ... Acknowledgment Timeout ...
    (alt.os.linux.suse)