Connection Issues Between Win10 Workstations and Windows 2016 Servers

Mark Lee 1 Reputation point
2021-03-28T01:31:03.737+00:00

Hi, I'm having some weird issues following updating a couple of Windows 10 workstations to feature update 20H2 and wondering if anyone can give me some pointers. Network Configuration 2 Windows 2016 servers that are configured as domain controllers and running DNS (let's call them DC1 and Dc2). Both are up to date with updates. DC1 is the primary. Workstation 1 Windows 10 laptop running feature update 20H2. This device does not have any issues showing up in the Event Viewer and can see/browse all other resources in the network EXCEPT DC2. Attempts to access this device via RDP fail immediately with the error "An Internal Error Occurred" This machine has a static IP address and an entry in DNS This machine is no longer available to browse DC2 from the "Network" icon (double-clicking DC2). If I try \dc2 that also fails with a diagnostic error 0x80070035. I've followed all the solutions I could find that make sense for my environment and everything checks out. I'm also allowing SMB1 on this laptop. Again, even with the RDP error there's nothing in the Event Log. I CAN browse it by using the IP address i.e. \192.168.1.9 but CANNOT connect to it using RDP with the IP address. Workstation 2 Windows 10 desktop running update 20H2. This machine CAN browse DC2 from both the "Network" icon AND IP address, however, it has recently started throwing a dialog at login that says "The security database on the server does not have a record for this computer". If I remove the ethernet cable and log in with cached credentials, then reconnect the cable, everything is fine until the next login. DC1 This server has no problems browsing DC2 and I can RDP to DC2 from this box without problems. There are no issues in the Event Viewer and DNS appears to be replicating. DC2 This server can browse all network resources and can RDP to DC1 without issue. I have made sure all necessary services are running and that it is replicating with DC1. No issues in the Event Viewer. I ran an sfc/scannow on DC2 but this did not reveal any integrity problems To me, this still sounds like DNS and I'm tempted to flatten and rebuild DC2 but that's a pain I just don't need in my life right now, so I'm wondering if anyone else has some suggestions? Thanks in advance

Windows Server 2016
Windows Server 2016
A Microsoft server operating system that supports enterprise-level management updated to data storage.
2,370 questions
Windows 10 Network
Windows 10 Network
Windows 10: A Microsoft operating system that runs on personal computers and tablets.Network: A group of devices that communicate either wirelessly or via a physical connection.
2,272 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,021 questions
0 comments

4 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Dave Patrick 426.1K Reputation points MVP
    2021-03-28T01:40:15.597+00:00

    Might check the domain health is 100% (dcdiag /repadmin) tools. If help were needed then 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.

    0 comments
  2. GettnBetter 6 Reputation points
    2021-03-28T03:17:06.107+00:00

    Remove the computer from the domain, make it a workgroup computer. Then delete the AD computer object and make sure all AD servers are sync'd "repadmin /syncall /Adep". Then add the computer back to the domain and bob should be your uncle :p

    0 comments
  3. Sunny Qi 10,896 Reputation points Microsoft Vendor
    2021-03-29T06:26:00.303+00:00

    Hi,

    Thanks for posting in Q&A platform.

    Based on provided information, my understanding is workstation 1 windows 10 client cannot access to resources in DC2 by \hostname of DC2 but can access by \IP of DC2. If my understanding is wrong, please correct me.

    Please run command nslookup + hostname of DC2 to see if the name can be resolved by DNS server which was configured on Windows 10.

    If not, could you please help post the result of ipconfig /all in Windows 10 client for further troubleshooting.

    And regarding of error "The security database on the server does not have a record for this computer", I would suggest you could post a new thread in our forum for help since we may focus on one issue in one thread. Thanks for your understanding.

    Best Regards,
    Sunny

    ----------

    If the Answer is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments
  4. Mark Lee 1 Reputation point
    2021-03-29T17:24:18.413+00:00

    My sincere thanks to everyone for their prompt replies. I also apologize for the delay in my response.

    This weekend the HDD in DC2 failed completely. Of course, there was no backup (what did we learn? :) ) I had a spare mechanical 1TB drive lying around, so I just built it again from scratch.

    Not surprisingly, this fixed the issue with the workstation not being able to connect via RDP. There were some issues joining the new server to the domain but disabling IPv6 on the adapter fixed that.

    Just got done promoting it to a DC and adding DNS, so I plan on letting things sync up and will report back in a day or so once the dust has settled.

    Thanks everyone