Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I am taking over responsibility for the network at a small medical practice. I understand how the network is configured, but I want to know more about the why.

The network currently is Cisco modem -> pfsense router -> Windows Server 2003 R2

In this configuration, what are the advantages to having the DHCP server be on the windows machine? There are only 10 clients on the network.

share|improve this question

3 Answers 3

up vote 5 down vote accepted

Assuming that you have Active Directory in place, the Windows clients would need to have the Windows server be listed as their DNS server. The router may not be able to do this.

This is needed because Active Directory works very heavily off of DNS for finding things like domain controllers, etc within the domain.

share|improve this answer
1  
pfSense's DHCPd can update MS DNS if you have security on the zone disabled. MS DHCPd is needed for secure updates if the clients do not support secure updates. –  Chris S Nov 29 '11 at 20:05

As a Windows Admin, I think it's just cleaner. As mrdenny said, you can occasionally get issues where the router won't handle certain DHCP options or hand those options out in a way Windows likes. I prefer having my DNS and DHCP handled by one of my Domain Controllers because it's just easier to troubleshoot later in my opinion.

share|improve this answer

I agree with Driftpeasant - makes life easier - one machine to look at if you get issues, and you can easily set up reservations with very specific options for unusual situtations/devices. pfSense 2.0 lets you set up DHCP options (e.g. option 66 which specifies a TFTP server) to your heart's content for all devices although I believe it is not quite as flexible when setting up reservations.

To answer mrdenny Both 1.2.3 and 2.0 let you specify your preferred DNS server for the clients. I agree with mrdenny that you want to use a Windows DNS server for this - as well as the clients registering themselves so they can be found by other clients/servers by a DNS lookup against your local windows DNS server, there will also be a heap of DNS SRV records relating to your AD envoironment that windows automatically maintains but are a PITA to set up in pfSense.

(If you do decide to use pfSense for DHCP, on the client pc's, open up properties for the NIC, check TCP/IPv4 properties, then click advanced, then go to the DNS tab, ensure the check box at the bottom that says Register this connection's addresses in DNS is ticked to ensure the clients actually do register)

Also in my experience, Windows boxes seem to take longer to get leases from some *nix DHCP servers including pfSense - I remember sometimes seeing the requests take so long windows would show the warning triangle by the NIC icon in the system tray then almost immediately afterwards sort itself out.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.