Emtpy Bindings on DHCP Server despite Static IPv4 Address is configured.

_{Thursday, December 4, 2014 10:27 AM}

My Gen2 2012 R2 DHCP Server VM (running on Hyper-V 2012R2), is unable to bind to IPv4, statically configured adapters.

Relevant ipconfig /all:

[gw01]: PS C:\Users\amatesi\Documents> ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : gw01
   Primary Dns Suffix  . . . . . . . : contoso.com
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : Yes
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : contoso.com

Ethernet adapter wLAN:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft Hyper-V Network Adapter #4
   Physical Address. . . . . . . . . :  AA-BB-CC-00-11-22
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 192.168.1.11(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.1.254
   DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter isatap.lan.pwrusr.com:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : contoso.com
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter 6TO4 Adapter:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft 6to4 Adapter
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{13C3CE9D-7550-4DB7-94CC-4C2B81E4219E}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter IPHTTPSInterface:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : IPHTTPSInterface
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::216f:11cc:847:1734%23(Preferred)
   Default Gateway . . . . . . . . . :
   NetBIOS over Tcpip. . . . . . . . : Disabled

Event viewer also reports the dreaded ERROR Event ID 1041:"The DHCP service is not servicing any DHCPv4 clients because none of the active network interfaces have statically configured IPv4 addresses, or there are no active interfaces."

*But I have already assigned a Static IP Address!*.

I even went as far as to read the Tcpip key on the registry and can confirm the MULTI_STRING value w/IPv4 Addresses reports 192.168.1.11!

So far, I tried the following procedure:

1. Removed the DHCP Server role & Restarted.

2. Checked/Made sure the registry was clear of DHCP Server remnants off HKLM[..]\Services\DHCP Server

3. Removed C:\Windows\System32\dhcp.

4. Restarted again.

5. Re-installed the DHCP Server role.

Everytime 1..5 was repeated, I (consistently) experienced the issue (No IPv4 Addresses reported on the bindings).

[Updates]:

1. Of course, the ETH Cable is connected to the port and ping/nslookup works.4

2. The VM has 2 Virtual Nics, but even with one NIC enabled and the other one disabled, I experience the same ISSUE.

Help anyone?!

Thanks.

Regards,

Andrea.

_{Thursday, December 4, 2014 11:48 AM}

After investigating a little bit further:

1. I've ran into a tool that detects rogue dhcp servers on my LAN. -> Results: No rogue DHCP Servers found (all green).

2. I've analysed the logs at C:\Windows\System32\dhcp\

Log extract:

00,12/04/14,22:05:02,Started,,,,,0,6,,,,,,,,,0
**64,**12/04/14,22:05:02,No static IP address bound to DHCP server,,,,,0,6,,,,,,,,,0
55,12/04/14,22:05:02,Authorized(servicing),,contoso.com,,,0,6,,,,,,,,,0

According to technet (http://technet.microsoft.com/en-us/library/dd759178.aspx):

Given the above, I'd exclude both "The server has not been configured with at least one static IP address for one of its installed and active network connections." AND "The server has not been configured with at least one static IP address for one of its installed and active network" connections.

Anyone knows the meaning of:"

The network connections of the server are either not installed or not actively connected to a network.

"?!

_{Friday, December 5, 2014 6:32 AM}

Hi Andrea,

Based on your description, the event viewer report error event ID 1041 even if you have configured IPv4 IP address.

Here are some troubleshooting thoughts which you could try,

1. Ping the IP address of the local computer to verify that it was added to the network correctly.

2. Check if the DHCP server service are starting before the network card is starting.

3. Check if the DHCP server service works fine and if the dependencies of this service is up.

4. If you have configured IPv6 scopes, maybe it’s expecting a static IPv6 address.

5. Update the network card driver.

Here are a thread discussed similar issues.

https://social.technet.microsoft.com/Forums/en-US/4067755e-1631-424d-9a32-f3b672c13c43/problems-with-dhcp-dns-on-2008r2-dc

For more details about how to delay loading of specific services, please refer to the kb article below,

http://support.microsoft.com/kb/193888

Best Regards,

Tina

Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

_{Friday, December 5, 2014 12:40 PM}

Hi Tina and thank you for your suggestions.

1. Ping the IP address of the local computer to verify that it was added to the network correctly.

- Pinging the IP address of the local computer works both locally and remotely.

2. Check if the DHCP server service are starting before the network card is starting.

- Not sure how to check that, 'though I tried to set the DHCP Server service (on services.msc) to "Automatic (Delayed Start)" and the IPv4 bindings are still empty.

- The "Wait for network to come up"-GPO has been successfully deployed/applied.

3. Check if the DHCP server service works fine and if the dependencies of this service is up.

- The DHCP Server dependencies seem to be up and running normally.

Specifically:

- "COM+ Event System" reported as running.

- "Remote Procedure Call (RPC)" reported as running.

- "Security Accounts Manager" reported as running.

- "Windows Event Log" reported as running.

- Couldn't find the "TCP/IP Protocol Driver" among the services.

4. If you have configured IPv6 scopes, maybe it’s expecting a static IPv6 address.

- I have no Static IPv6 Scopes, 'though I configured a Static ::/64 IPv6 Address on my adapter and it shows up on the bindings (while IPv4 is still empty).

5. Update the network card driver.

- Couldn't find any updated synthetic network adapter drivers.

_{Wednesday, August 1, 2018 9:03 PM}

Andrea,

I have a similar issue.  How did you fix it?

Thanks

_{Thursday, August 2, 2018 12:18 AM}

Hi Mutthu, this is a very "old" issue (reported by me in 2014 - it is now 2018 at time o/t writing).

I must've fixed it by rebuilding the gateway server (unfortunately I don't exactly recall whether that is the case, but I bet you that is the most likely route & sorry to be the bearer of not so great news).

Thanks.

Regards,

Andrea.

_{Wednesday, August 29, 2018 6:06 PM}

Stumbled across this thread by accident, however empty binding in DHCP may be a cause of dynamic IP's, I may be mistaken but I don't believe you can have a dynamic IP address on a DHCP server. it needs to be a static IP for bindings to work.

_{Friday, April 10, 2020 4:42 AM}

Hello! I got tht same problem after recovering virtual machine from backup.
I solved the problem by next actions:

1. copy newest NIC drivers to server local disk
2. stop DHCP Server service
3. Open Device Manager
4. Delete the Network adapter and check "Uninstall drivers"
5. Rescan new devices
6. Find network adapter and install drivers 
7. Setup IP address/netmask/gateway/etc
8. Start DHCP Server service and bind NIC