DHCP Server - Windows Server 2012, Router, or both?

Hi all,

I'm building a home lab with a Windows Server 2012 and an Asus router. From the research I've done, it seems i should let the Server handle the DHCP role, and turn off DHCP on the router.

But what if I want people access to our network w/o joining the domain. For example - I'd like people to join the wireless network and be able to surf the internet. Or maybe allow access to a server folder w/o joining the domain.

How should I handle this? Do I enable DHCP Server roles on both the Server and the Router, with each handling a different pool of addressed?

Thank in advance.

You can still do this by using the Windows Server only, no special setup required,

You can still do this by using the Windows Server only, no special setup required,

If the point of the lab is to replicate a real world environment, I'd argue that most businesses don't want untrusted/unmanaged devices having access to the same LAN as their trusted devices. They segment them into a separate LAN (much like a DMZ or guest network) and have a firewall only allowing necessary traffic to specific resources. In such a setup, that segment would have its own DHCP server. This is easy to reproduce with Hyper-V, VLANs, and a small linux VM doing DHCP duties.

So Windows Server will automatically hand out IP addresses to dumb devices like printers? I just plug in a printer and the Server handles it?

Guests who log onto our wireless network w/o joining our domain (not even being aware of the Server) will be given IP addresses by the Server as well?

DHCP is a broadcast protocol so, by default, there is no difference between a domain joined machine and a printer. Yes, they will get IP addresses. *HOWEVER* each user or device legally still requires a CAL. The setup I proposed above kills two birds with one stone. It is more secure and helps ensure you stay legal.

Ok - thank you. Yes, I'm good with the CALs and such.

Share this

Related Posts

There was an error in this gadget