• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

How is DHCP clients internet traffic routed?

E

eryco

Junior Member

I wanted to setup a Windows 2003 DHCP server in my office, but was wondering if all of the clients'
internet traffic will be routed through the DHCP server and then to the gateway, or directly to the gateway. The reason that this is important, is that the server also stores several databases that are accessed frequently and I didn't want to slow down the server too much. I have about 30 WinXP & Win2000 clients that will be connecting to this server. They all have internet routeable IPs at the moment, and they all connect to the same gateway that the server connects to (all in same subnet).

Thanks,
eryco
 
A dhcp server is normally configured to hand out

IP address
Mask
Gateway
DNS/WINS servers
Netbios Node type
Domain

The gateway address is a router on the PCs LAN that "routes" the packets to wherever they need to go. Once the DHCP server has handed out the information to the PC that DHCP server is not involved with the client.

So no worries for you!
 
I have to point out an exception to this, what spidey said is true. The only time it is not is when both the router and the DHCP server are the same box. This is what you have with most SOHO broadband gateways, the router and the DHCP server are the same box. The software DHCP server still only hands out the DHCP info, it still does not router traffic.
 
amdfanboy:
Thanks for the info...
In this case the router and the server are not the same. We're using a Cisco router for our subnet.

Another question I have:

I just setup the DHCP service in Windows 2003, but before I enable it I was wondering if there was a way to restrict which clients can lease an IP from the server? I only want IPs to be leased to clients that belong to the same Windows domain that the server belongs to. This is the first time I set up a DHCP server, so I'm not totally familiar on how to implement this type of restriction. The only thing I saw in the DHCP snap-in, was how to statically assign an IP to a MAC address. But I didn't see a way to set an allowed list of MAC addresses (in a similar fashion to a DSL/Cable router). Is this even possible with a Windows-based DHCP server?

One idea I had was to block UDP ports 67 & 68 to all clients using an IPSec policy (through domain group policy), and afterwards creating another policy to allow domain members access to these ports.

What do you think about this idea, or do you have any other way to do this?...

Thanks.

 
You must log in or register to reply here.

TRENDING THREADS

Back
Top