VPN DHCP and Name Resolution

[Guest]

I have a W2K VPN server that is setup with DHCP enabled. The DHCP Relay
option is setup to forward requests to the DHCP server. The DHCP server
scopes are setup with DNS, Wins, and routing options.

When I connect to the VPN, I get a correct IP address from the configured
pool and I can work. However, when I run ipconfig /all I see that DHCP is set
to 'No' for the PPP connection.

Also, ipconfig shows that the DNS servers given are the name servers for the
actual NIC in the VPN server, and not the ones listed in DHCP. For example,
the NIC has 2 addresses bound to it on the actual server (10.1.1.1 and
10.1.1.2). DHCP has the 2 DNS servers listed as 10.1.2.1 and 10.1.2.2.

Why does the VPN connection use the DNS servers bound to the NIC instead of
the ones configured with DHCP? Why does it say 'No' for DHCP if it's giving
me an IP address in the first place?

Lastly, how do I configure this connection to use the VPN DNS server first,
instead of the clients local DNS? My name resolution for the connection is
using the client side DNS instead of the PPP assigned DNS. The VPN connection
is set to be the default gateway.

 

[Phillip Windell]

Why does the VPN connection use the DNS servers bound to the NIC instead of
the ones configured with DHCP? Why does it say 'No' for DHCP if it's giving
me an IP address in the first place?

You have to enable and configure the DHCP Relay Agent in RRAS on the VPN
server. Without that it will only give the user "basic" TCP/IP settings.

Remember that an RRAS user (which a VPN user is) doesn't not get anything
from DHCP directly. RRAS gets a "group" of IP#s from DHCP in *advance*
before any user ever connects and binds them to each of its Remote Access
Ports and that is what the users gets. In order for the user to get
addional Scope Options or DHCP Server Options the DHCP Agent in RRAS has to
get that information from the DHCP server.

 

[Guest]

The DHCP Relay Agent is configured with the IP address of the working DHCP
server. This DHCP server seems to be working w/o problems as when I logon
locally on site, I get all the correct parameters.

 

[Phillip Windell]

The only other thing I can think of is this:

In the RRAS Admin right-click on the server name and choose Properties.
Choose the IP Tab
At the very bottom there is an "Adapter" selection for what DHCP, DNS, &
WINS is supposed to be associated with. sometimes it is defaulted to
"Internal Connection". This is incorrect,...it needs to be set to the
connection associated with the Interal LAN nic and it goes by the same name
as seen in Network Places.

There is nothing else that I know of that would have anything to do with the
DHCP issues.