Advertisement
We’re long overdue for a new server for DC (and file sharing) VMs for about 100 users, but we’re internally discussing a move from on-prem to a hybrid cloud storage solution like Egnyte so that will determine the specs (primarily storage needs). That said, I can’t quite jump on purchasing anything just yet.<\/p>\n
In the meantime, I’m having a hard time making sure what we have in place doesn’t feel like a house of cards. We’ve got a 2012 R2 server that acts as AD/DC and file server and the FSMO roles have been transferred to it. All is “working” - however, all clients are still pointing to an ever older 2008 server (DC1) based on “set L” and \"nltest /dsgetdc:domain, nor do clients failover to DC2 when DC1 is disconnected, so there seems to have been a step missed in the transfer. The DHCP server is properly assigning DC2 as DNS1 and DC1 as DNS2, so I’m exactly sure why this is happening. Things appear to be syncing across DCs properly and repl tests confirm that. There are no sysvol or NETLOGON shares on DC2 though after the role transfer.<\/p>\n
When I run dcdiag on DC2, I see this error;<\/p>\n
Testing server: Default-First-Site-Name\\DC2
\nStarting test: Advertising
\nWarning: DsGetDcName returned information for \\DC1.domain.local
\nwhen we were trying to reach DC2
\nSERVER IS NOT RESPONDING or IS NOT CONSIDERED SUITABLE.
\n…DC2 failed test Advertising<\/p>\n
AND<\/p>\n
Starting test: NetLogons\n Unable to connect to the NETLOGON share! (\\\\DC2\\netlogon)\n [DC2] An net use or LsaPolicy operation failed with error 67,\n The network name cannot be found..\n<\/code><\/pre>\nI know the only real solution is to replace this ancient setup immediately, but while that gets approved, I’m looking to hopefully sort this issue out and to get some AD/DC redundancy in place in short order, ideally without blowing everything up. I have another 2012 R2 Poweredge onsite that is not in use – should I provision that with a new server OS and set that up as DC? Thanks in advance.<\/p>","upvoteCount":6,"answerCount":34,"datePublished":"2025-02-23T23:27:10.918Z","author":{"@type":"Person","name":"spiceuser-80l","url":"https://community.spiceworks.com/u/spiceuser-80l"},"suggestedAnswer":[{"@type":"Answer","text":"
We’re long overdue for a new server for DC (and file sharing) VMs for about 100 users, but we’re internally discussing a move from on-prem to a hybrid cloud storage solution like Egnyte so that will determine the specs (primarily storage needs). That said, I can’t quite jump on purchasing anything just yet.<\/p>\n
In the meantime, I’m having a hard time making sure what we have in place doesn’t feel like a house of cards. We’ve got a 2012 R2 server that acts as AD/DC and file server and the FSMO roles have been transferred to it. All is “working” - however, all clients are still pointing to an ever older 2008 server (DC1) based on “set L” and \"nltest /dsgetdc:domain, nor do clients failover to DC2 when DC1 is disconnected, so there seems to have been a step missed in the transfer. The DHCP server is properly assigning DC2 as DNS1 and DC1 as DNS2, so I’m exactly sure why this is happening. Things appear to be syncing across DCs properly and repl tests confirm that. There are no sysvol or NETLOGON shares on DC2 though after the role transfer.<\/p>\n
When I run dcdiag on DC2, I see this error;<\/p>\n
Testing server: Default-First-Site-Name\\DC2
\nStarting test: Advertising
\nWarning: DsGetDcName returned information for \\DC1.domain.local
\nwhen we were trying to reach DC2
\nSERVER IS NOT RESPONDING or IS NOT CONSIDERED SUITABLE.
\n…DC2 failed test Advertising<\/p>\n
AND<\/p>\n
Starting test: NetLogons\n Unable to connect to the NETLOGON share! (\\\\DC2\\netlogon)\n [DC2] An net use or LsaPolicy operation failed with error 67,\n The network name cannot be found..\n<\/code><\/pre>\nI know the only real solution is to replace this ancient setup immediately, but while that gets approved, I’m looking to hopefully sort this issue out and to get some AD/DC redundancy in place in short order, ideally without blowing everything up. I have another 2012 R2 Poweredge onsite that is not in use – should I provision that with a new server OS and set that up as DC? Thanks in advance.<\/p>","upvoteCount":6,"datePublished":"2025-02-23T23:27:10.992Z","url":"https://community.spiceworks.com/t/dc-errors-and-short-term-redundancy-for-peace-of-mind/1178431/1","author":{"@type":"Person","name":"spiceuser-80l","url":"https://community.spiceworks.com/u/spiceuser-80l"}},{"@type":"Answer","text":"