btm02sf
asked on
Windows 2016 Server - The DFS Replication service failed to contact domain controller error - Event ID 1202
On a Windows 2016 Server Standard, single server, which also functions as the domain controller for a small office, upon each restart I get Event ID 1202 shown below
"The DFS Replication service failed to contact domain controller to access configuration information. Replication is stopped. The service will try again during the next configuration polling cycle, which will occur in 60 minutes. This event can be caused by TCP/IP connectivity, firewall, Active Directory Domain Services, or DNS issues.
Additional Information:
Error: 160 (One or more arguments are not correct.)"
While searching for solutions or tips on this Event ID, I saw an advice on running the following command: Dfsrdiag pollad /verbose. When I run the command, I get the expected result -Operation Succeeded - see attached screenshot. This error happens upon each reboot. It clearly says that the service will run again in 60 minutes. The error doesn't come back in 60 minutes, so apparently there is no issue. Does anyone have an explanation why do these errors come up upon reboot on a single domain server?
Thank you.
Dfsrdiag_command_results.jpg
"The DFS Replication service failed to contact domain controller to access configuration information. Replication is stopped. The service will try again during the next configuration polling cycle, which will occur in 60 minutes. This event can be caused by TCP/IP connectivity, firewall, Active Directory Domain Services, or DNS issues.
Additional Information:
Error: 160 (One or more arguments are not correct.)"
While searching for solutions or tips on this Event ID, I saw an advice on running the following command: Dfsrdiag pollad /verbose. When I run the command, I get the expected result -Operation Succeeded - see attached screenshot. This error happens upon each reboot. It clearly says that the service will run again in 60 minutes. The error doesn't come back in 60 minutes, so apparently there is no issue. Does anyone have an explanation why do these errors come up upon reboot on a single domain server?
Thank you.
Dfsrdiag_command_results.jpg
It sounds like the replication is coming up and running before the NIC is full operational, do you have any issues other than the error?
Hello
According to the id of the error, it is due to network connectivity problems. Please perform the following tests that appear in the indicated link
https://social.technet.microsoft.com/wiki/contents/articles/1206.dfsr-event-1202-dfs-replication.aspx
I paid attention to your observations.
According to the id of the error, it is due to network connectivity problems. Please perform the following tests that appear in the indicated link
https://social.technet.microsoft.com/wiki/contents/articles/1206.dfsr-event-1202-dfs-replication.aspx
I paid attention to your observations.
ASKER
Brian M - thank you for responding. there is no side effect (at least visible) after the error is registered in the EventViewer after a reboot.
RAFA - thank you for the link. I actually didn't do the nslookup command to verify if it returns a response. When I ran it it returned "Server Unknown" and an IPv6 address. I removed the IPv6 address set it to DHCP, so now when running the nslookup command I get the appropriate response. I cannot reboot the server right now, but will do that later today, and will come back with more details.
RAFA - thank you for the link. I actually didn't do the nslookup command to verify if it returns a response. When I ran it it returned "Server Unknown" and an IPv6 address. I removed the IPv6 address set it to DHCP, so now when running the nslookup command I get the appropriate response. I cannot reboot the server right now, but will do that later today, and will come back with more details.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
By the way, if that does not help and you have no side effects or impact you can ignore this error, IMHO.
ASKER
Thank you Kirschi, for the suggestion on setting up the DFS to automatic Delayed startup. I will not be at the customer for another week, so next time when I will be on site, I will set the DFS service to Automatic Delayed, and see what happens. Will post back the results
ASKER
KIrschi, I returned to the client today, and I've set to Delayed Start the DFS, rebooted the server, and the error went away. Thank you for your help.