DC02 - Done
DC1 - It already has 127.0.0.1 in the list. Is this not sufficient?
DC01 - Again, already has 127.0.0.1
DSPatrick answered
On DC02 I'd add the server's own static ip address (10.91.150.52) listed for DNS then do ipconfig /flushdns, ipconfig /registerdns, restart the netlogon service
On DC1 I'd add the server's own static ip address (10.91.150.2) listed for DNS then do ipconfig /flushdns, ipconfig /registerdns, restart the netlogon service
On DC01 I'd add the server's own static ip address (10.91.150.51) listed for DNS then do ipconfig /flushdns, ipconfig /registerdns, restart the netlogon service
I see Error 5008 in the DFS Replication logs on every server:
The DFS Replication service failed to communicate with partner DC1 for replication group Domain System Volume. This error can occur if the host is unreachable, or if the DFS Replication service is not running on the server.
Partner DNS Address: DC1.morgan911.net
Optional data if available:
Partner WINS Address: DC1
Partner IP Address: 10.91.150.2
The service will retry the connection periodically.
Additional Information:
Error: 1722 (The RPC server is unavailable.)
We run a 3rd party time sync software on our DCs and all of our domain servers and workstations. We require higher time accuracy than can be achieved from the Windows time service.
IPv6 disabled on DC02
AD02 is currently the only authorized DHCP server on the network. The goal is to have 2 and DC02 is supposed to eventually be the 2nd DHCP server. DHCP server has been installed but not configured.
If I try to demote DC02 I get an Error:
Error validating Credentials: Verification of user credential permissions failed. Failed to examine the Active Directory forest. The error was: The operation cannot continue because the LDAP connect/bind operation failed: Error 1326 (The user name or password is incorrect).