![]() The Windows DHCP server however listens for DHCP servicing on all network interfaces. There is a virtual machine running on that LAN segment which is servicing the DHCP requests. However, I have a second NIC that I’m passing through to virtual machines that I do not want the DC to even have an IP address, much less to service DHCP requests. In my case, I do want the DC’s DHCP server to service requests on one of the LAN segments which is on one of the NICs. By default, when the Windows DHCP server detects a rogue DHCP server, it shuts itself down reporting Event IDs 10. If more than one server on a LAN segment is responding to DHCP requests then all hell breaks loose. One of the built-in features to Window’s DHCP server is rogue DHCP server detection. The root cause as reported in the event log was an EventID 1053 stating: “The DHCP/BINL service has encountered another server on this network with IP Address, x.x.x.x, belonging to the domain. The DHCP server on my Windows Server 2012 R2 Essentials domain controller shutdown (Event ID 1054) when I added an additional NIC and plugged it in.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |