Advertisement
I have a 4 DC environment. 2 DC remote and 2 local (DC1 & DC2). Replications and DNS are working. DC1 local decided it did not want to work. DC1 local was causing other issues losing its secure channel and constantly having to reset the network password using netdom so I had to shut it down at this time. The AD roles, print and data were moved to DC2 local. I try logging into my computer and it takes a very long time to log in. almost 15 minutes. If DC1 is offline shouldn’t DC2 pick up the slack with authentication. DC1 and DC2 are located in the same building and on the same network. I restarted the Netlogon service and updated DHCP but that is on our router not the DC. What am I missing?<\/p>","upvoteCount":0,"answerCount":14,"datePublished":"2024-05-20T23:13:35.590Z","author":{"@type":"Person","name":"RSorrentino","url":"https://community.spiceworks.com/u/RSorrentino"},"acceptedAnswer":{"@type":"Answer","text":"
If it were me, I would do this for DNS<\/p>\n
DC1 Site 1: DC2 Site 1, DC1 Site 2, 127.0.0.1
\nDC2 Site 1: DC1 Site 1, DC2 Site 2, 127.0.0.1
\nDC1 Site 2: DC2 Site 2, DC1 Site 1, 127.0.0.1
\nDC2 Site 2: DC1 Site 2, DC2 Site 1, 127.0.0.1<\/p>\n
This way you check the other DC in the same site first, then a DC in the other site, then itself last.<\/p>","upvoteCount":1,"datePublished":"2024-05-21T14:58:47.752Z","url":"https://community.spiceworks.com/t/client-long-time-logging-into-dc/1077325/10","author":{"@type":"Person","name":"PatrickFarrell","url":"https://community.spiceworks.com/u/PatrickFarrell"}},"suggestedAnswer":[{"@type":"Answer","text":"
I have a 4 DC environment. 2 DC remote and 2 local (DC1 & DC2). Replications and DNS are working. DC1 local decided it did not want to work. DC1 local was causing other issues losing its secure channel and constantly having to reset the network password using netdom so I had to shut it down at this time. The AD roles, print and data were moved to DC2 local. I try logging into my computer and it takes a very long time to log in. almost 15 minutes. If DC1 is offline shouldn’t DC2 pick up the slack with authentication. DC1 and DC2 are located in the same building and on the same network. I restarted the Netlogon service and updated DHCP but that is on our router not the DC. What am I missing?<\/p>","upvoteCount":0,"datePublished":"2024-05-20T23:13:35.664Z","url":"https://community.spiceworks.com/t/client-long-time-logging-into-dc/1077325/1","author":{"@type":"Person","name":"RSorrentino","url":"https://community.spiceworks.com/u/RSorrentino"}},{"@type":"Answer","text":"
Where is DNS pointing on your client computer?<\/p>","upvoteCount":0,"datePublished":"2024-05-20T23:37:30.680Z","url":"https://community.spiceworks.com/t/client-long-time-logging-into-dc/1077325/2","author":{"@type":"Person","name":"James404d","url":"https://community.spiceworks.com/u/James404d"}},{"@type":"Answer","text":"
The computers are pointing to the new DC.<\/p>","upvoteCount":0,"datePublished":"2024-05-20T23:46:31.107Z","url":"https://community.spiceworks.com/t/client-long-time-logging-into-dc/1077325/3","author":{"@type":"Person","name":"RSorrentino","url":"https://community.spiceworks.com/u/RSorrentino"}},{"@type":"Answer","text":"
After you log in, if you open up a command prompt and type SET<\/p>\n
What does it show your logonserver is?<\/p>","upvoteCount":0,"datePublished":"2024-05-21T00:29:54.933Z","url":"https://community.spiceworks.com/t/client-long-time-logging-into-dc/1077325/4","author":{"@type":"Person","name":"PatrickFarrell","url":"https://community.spiceworks.com/u/PatrickFarrell"}},{"@type":"Answer","text":"
I couple I checked were pointing to the new DC. I have a couple that still point to the old server. Can I force the logonserver?<\/p>","upvoteCount":0,"datePublished":"2024-05-21T00:42:48.092Z","url":"https://community.spiceworks.com/t/client-long-time-logging-into-dc/1077325/5","author":{"@type":"Person","name":"RSorrentino","url":"https://community.spiceworks.com/u/RSorrentino"}},{"@type":"Answer","text":"
No, logon server will be picked at random from a domain controller in the same site as the client computer (providing the subnet the client computer is in is asociated with the site in AD Sites and Services). I’m more concerned about your general AD health. What you described with the DC is obviously not normal. I’m going to say check DNS because so many times it’s DNS<\/p>\n