![]() ![]() ![]() I have pointed the problem DC3 to use DC1 as primary DNS, as you can see from the cut-and-paste, but still same problem. If you have feedback for TechNet Subscriber Support, that I have already done. Please remember to mark the replies as answers if they help and unmark them if they provide no help. Warm Reminder: The article links in the thread was no longer available, I will try to see if there has a replacement. I would suggest you refer to the following thread, try to configure DNS server as other DC to see if it helps and check event viewer to see if there has some error event logged. Trusted DC Connection Status Status = 1311 0x51f ERROR_NO_LOGON_SERVERS Then I restart the server and do a check again Trusted DC Connection Status Status = 0 0x0 NERR_SuccessĬ:\Windows\system32>nltest /sc_query:HOME.LOCAL If I run the command nltest /sc_reset:HOME.LOCAL then the server respons is ok as you can see below.īut If I restart the DC then the problem is back.Ĭ:\Windows\system32>nltest /sc_reset:HOME.LOCAL The other 2 domain controllers are reporting ok on the command The DNS service is running and will permit me to ping other domain controllers. The domain controller is pointing to itself for DNS, it is a global catalog (all servers in the domain are). I read another question on the forum that the problem had solved it selft after a couple of days, but now our domain controller has not been rebooted for 4 days, so I guess it will not self heal itself :) All replication seems fine, and can not see anything spesific error in dcdiag or repadmin.īut when we run the command "Nltest /dsregdns" we are getting this errorĬonnection Status = 1311 0x51f ERROR_NO_LOGON_SERVERS We have replaced our domain controller in site B, so it is now running Windows Server 2016. 3 domain controllers, 2 in site A, 1 in site B ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |