I am assisting someone who has a new installation of Windows Server 2011 Essentials. He installed and configured the DHCP role but it is not working. What I have observed is that if you run ipconfig /release && ipconfig /renew on a workstation (we have tried several different computers) it comes up with a 169. address.
I looked at the DHCP configuration on the server and all appears well. It is active, it has a valid scope (I deleted the scope and recreated it as 192.168.3.50 to 192.168.3.99; server IP is 192.168.3.2), and I have restarted the service. It is set to listen on all interfaces (there are two net cards, one is disabled). I didn't see any restrictions (by MAC address, for example) on the DHCP server. The only other potential DHCP server on the network is the router, but we have DHCP disabled there.
If you set a workstation up with a 192.168.3.x static IP address, it can ping and otherwise access the server properly.
The server has IPv6 set up to retrieve the address from a DHCP server, but IPv6 is not configured in DHCP so no IPv6 address is received. I mention this for thoroughness, but presume that it should not be an issue.
I have set up DHCP numerous times on Windows servers without serious issue. It seems pretty straightforward and logical.
Our workaround is to disable DHCP on the Windows Server and enable it on the router instead. This is not the approach we'd like to use.
What should I be looking at to fix this?