D
Damdor_
Guest
Hello Everyone
We have two domain controllers running Windows Server 2012.
Both of them had DHCP installed and we configured a normal load balancing failover between the two servers for a IPV4 scope. This have been working really good for quite some time now. But after some recent security updates all of a suddan the primary DHCP controller is unable to communicate with the other DHCP server. If it had anything to do with the updates I do not know.
But in the eventviewer of the primary DHCP controller the following two error messages was written.Both of the servers are using an external NTP pool that works well they are at the exact same time.
The server detected that it is out of time synchronization with partner server: dc04 for failover relationship: 169.254.153.80-dc04. The time is out of sync by: 480 seconds .
The failover state of server: 169.254.153.80 for failover relationship: 169.254.153.80-dc04 changed from: NORMAL to COMMUNICATION_INT.
I tried to remove the failover configuration but the primary DHCP controller won't let me. I tried a few different scenarions.
But if i choose deconfigure Failover this is what happens.
Check status of the failover relationship..............Failed.
The DHCP Server service is not running on the target computer.
Deconfigure failover failed. Error 1722. The DHPC server is not running on the target computer.
I then tried to change the status of the failover server to Partner down to be able to remove it. But the primary DHCP server cannot even change that. It replies with.
The DHCP service is not running on the target computer.
At this point DHCP service was running fine on both servers and both used the same timeservers and the time matched correctly. After this I tried to remove my DHCP scope to create it again but it says I cannot remove it as long as I got a failover configured.
The last thing we tried was removing the DHCP failover from the secondary DHCP server and that worked. However our primary DHCP server still thinks it has a failover setup with the secondary DHCP server. We uninstalled the DHCP server role from the secondary DHCP server and still no luck.
Anyone know how to force a removal of an old failover configuration so we can set up a new one and maybe someone understand the time difference it mentions?
Thanks.
Kind Regards!
Continue reading...
We have two domain controllers running Windows Server 2012.
Both of them had DHCP installed and we configured a normal load balancing failover between the two servers for a IPV4 scope. This have been working really good for quite some time now. But after some recent security updates all of a suddan the primary DHCP controller is unable to communicate with the other DHCP server. If it had anything to do with the updates I do not know.
But in the eventviewer of the primary DHCP controller the following two error messages was written.Both of the servers are using an external NTP pool that works well they are at the exact same time.
The server detected that it is out of time synchronization with partner server: dc04 for failover relationship: 169.254.153.80-dc04. The time is out of sync by: 480 seconds .
The failover state of server: 169.254.153.80 for failover relationship: 169.254.153.80-dc04 changed from: NORMAL to COMMUNICATION_INT.
I tried to remove the failover configuration but the primary DHCP controller won't let me. I tried a few different scenarions.
But if i choose deconfigure Failover this is what happens.
Check status of the failover relationship..............Failed.
The DHCP Server service is not running on the target computer.
Deconfigure failover failed. Error 1722. The DHPC server is not running on the target computer.
I then tried to change the status of the failover server to Partner down to be able to remove it. But the primary DHCP server cannot even change that. It replies with.
The DHCP service is not running on the target computer.
At this point DHCP service was running fine on both servers and both used the same timeservers and the time matched correctly. After this I tried to remove my DHCP scope to create it again but it says I cannot remove it as long as I got a failover configured.
The last thing we tried was removing the DHCP failover from the secondary DHCP server and that worked. However our primary DHCP server still thinks it has a failover setup with the secondary DHCP server. We uninstalled the DHCP server role from the secondary DHCP server and still no luck.
Anyone know how to force a removal of an old failover configuration so we can set up a new one and maybe someone understand the time difference it mentions?
Thanks.
Kind Regards!
Continue reading...