Can't join new devices to DC, users can't login (Migrated Windows Server 2008 to Server 2019)

Lukadmin 1 Reputation point
2020-12-30T23:49:54.337+00:00

Hi,

I am having an issue with my domain controller. Recently successfully migrated my Windows Server 2008 (which holds DNS and DHCP roles). DCPROMO demotion failed so I had to manually remove the old DC, did the metadata cleanup, and disconnected it from the network. I also, assigned the static ip address of the old server to new server. FSMO was transferred successfully. DNS and DHCP seems to be working, I can ping my domain controller from the device I want to join.
Dsdiag /test:dns passed successfully

The users can’t login to their accounts (“We can’t sign you with this credential because your domain isn’t available…”). I can’t join new devices to the domain ("network path was not found")

Also, as a domain admin user I can login/logoff to devices but it takes too long to do so.
In the event viewer could not see any recent errors.
Any help would be appreciated. Thanks.

Windows Server 2019
Windows Server 2019
A Microsoft server operating system that supports enterprise-level management updated to data storage.
3,470 questions
Windows Server 2016
Windows Server 2016
A Microsoft server operating system that supports enterprise-level management updated to data storage.
2,379 questions
Active Directory
Active Directory
A set of directory-based technologies included in Windows Server.
5,899 questions
Windows DHCP
Windows DHCP
Windows: A family of Microsoft operating systems that run across personal computers, tablets, laptops, phones, internet of things devices, self-contained mixed reality headsets, large collaboration screens, and other devices.DHCP: Dynamic Host Configuration Protocol (DHCP). A communications protocol that lets network administrators manage centrally and automate the assignment of Internet Protocol (IP) addresses in an organization's network.
1,023 questions

5 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Dave Patrick 426.1K Reputation points MVP
    2020-12-31T01:02:38.007+00:00

    Please run;

    Dcdiag /v /c /d /e /s:%computername% >c:\dcdiag.log
    repadmin /showrepl >C:\repl.txt
    ipconfig /all > C:\dc1.txt
    ipconfig /all > C:\dc2.txt
    ipconfig /all > C:\problemworkstation.txt

    then put unzipped text files up on OneDrive and share a link.

  2. Hannah Xiong 6,231 Reputation points
    2021-01-01T01:37:37.383+00:00

    Hello,

    Thank you so much for posting here.

    To further troubleshoot, we need to check whether our AD environment is healthy. We could run the commands as Dave mentioned to check if all DCs work fine and if AD replication works properly.

    Looking forward to your feedback. Thanks so much.

    Best regards,
    Hannah Xiong

  3. Dave Patrick 426.1K Reputation points MVP
    2021-01-04T16:37:20.463+00:00

    Looks Ok, I'd check that the domain controller and problem members both got the Domain network firewall profiles. If not try restarting the Network Location Awareness (NlaSvc)

    --please don't forget to Accept as answer if the reply is helpful--

    0 comments
  4. Hannah Xiong 6,231 Reputation points
    2021-01-07T06:21:06.09+00:00

    Hello,

    Thank you so much for your kindly reply.

    There is only one DC, right? And now we could not join new devices to the domain, right?

    Have we checked the C:\Windows\Debug\Netsetup.log on the devices?

    Best regards,
    Hannah Xiong

  5. Edward Dake 76 Reputation points Microsoft Employee
    2021-04-20T02:24:28.257+00:00

    I'm not sure, but I think you might have a subnetting issue. From the logs you provided, the client machine is in subnet 255.255.252.0 which is a Class B Subnet, which would provide the following IP range:
    191.168.0.1 - 191.168.3.254

    Your client is within this range, as is your DC, but the DC has a different subnet.

    Your DC is 255.255.255.0 which is a Class C Subnet, which gives only the following IP range:
    192.168.1.1 - 192.168.1.254

    Your client is not in this range, so it might be why it is getting the errors that you are seeing.

    Have you tried to change the subnet for the DC to match the subnet for the clients? 255.255.252.0 and see if that allows them to communicate with one another?

    Hope this helps....

    Edward

    0 comments