Link to home
Start Free TrialLog in
Avatar of hmcnasty
hmcnasty

asked on

Server 2003 VPN DHCP Question

If I have one DC configured to give out DHCP but my  VPN comes in on a different DC.  How do I tell the VPN DC where the DHCP server is?
Avatar of knightrider2k2
knightrider2k2

If it is on the same subnet then you do not need to specify anything. If the dhcp server is on a different subnet then you can specify the DHCP relay agent under the IP Routing
Avatar of hmcnasty

ASKER

That's weird. That's what I thought.  Their on the same subnet but when I VPN in I get on of those bogus ip addesses.  I mean it still works and everything but it's not getting the IP from the DHCP server.
When I specify it in Ip Routing.  Do I use the one in NAT/Firewall?

>Do I use the one in NAT/Firewall?

Sorry I did not understand what you mean
ASKER CERTIFIED SOLUTION
Avatar of megs28
megs28
Flag of Canada image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
For whatever reason the  VPN server is not seeing the DHCP server so I was going to try and specify it under IP routing.  I assume you mean IP routing in RAS.  Where in IP rounting would I specify the DHCP server?
megs28.

Yeah that works.  I had it like that before but I was unable to resolve netbios names.  However, for some reason it's working now.  

Thanks
Ensure netbios over tcp/ip is enabled for EVERYTHING - adapter on RRAS server, network adapter on client, VPN connection on client, etc. etc.  There's always the quick and dirty way around the name resolution thing, which is a static entry in the hosts file (I'm not an advocate of this).  You can create a simple logon script to add entries that are necessary.

I don't know off the top of my head the configuration for the RRAS in 2k3 as I rarely ever have to look at the config, and I'm nowhere near a server right now.  Sorry.

FYI - RAS - Remote Access Server...RRAS - Routing and Remote Access.  Same crap, different pile (depending on the OS).
Thank you

I got it to work by putting the DNS suffix in TCP/IP.  In other words it'll take the FQDN if each machine but not the netbios name.  So by inserting the suffix in there it seems to work fine. Although I woudl like to know why at some point.

Wes
When you make a connection from the client side check to see if netbios over tcp/ip is enabled (ipconfig /all....don't trust how the connection is configured to give you a proper response).  If it isn't, this is why the FQDN works and the netbios name doesn't.  With my 2k3 RRAS server, I often find this issue to be a hit or a miss.....and I could never figure out exactly why even though netbios over tcp/ip was enabled on every adapter and every connection for the bloody thing.  I chalked it up to the fact that I have an NT network and 2k3 rras servers.  meh.