Unfortunately, it happened again. All those who logged into this server, by name, do not work. When the server is turned off, everything starts working.
KB5046616 on Domain Controller -> rdp to hostname fails ip address works
KB5046616 on Domain Controller -> connect rdp to hostname fails ip address works
Windows for business | Windows Server | Directory services | Active Directory
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
4 answers
Sort by: Most helpful
-
Anonymous
2024-12-05T13:48:34+00:00 -
Anonymous
2024-12-03T23:28:50+00:00 Hello,
Thanks for your reply.
I am glad that your problem has been solved.
Thank you very much for your support of Microsoft products and your selfless sharing.
Best Regards,
Yanhong Liu
-
Anonymous
2024-12-03T17:30:29+00:00 Thank you.
DNS is OK.
The domain controller was just installed (Windows server standart 2022). Updates were installed.
Time is synchronized. No problems with this.
NLA did not help.
I have not removed the updates yet. It was enough to turn off the installed DC for a while. Then turn it on. So far everything works by name and IP
-
Anonymous
2024-12-02T02:03:03+00:00 Hello,
Thank you for posting in Microsoft Community forum.
It sounds like you're experiencing an issue where Remote Desktop Protocol (RDP) connections to a domain controller using the hostname fail, but connections using the IP address work. Here are a few potential solutions you can try:
DNS Issues: Ensure that the DNS records for the domain controller are correct. You can use nslookup to verify that the hostname resolves to the correct IP address. Also, check for any duplicate DNS entries.
Kerberos Authentication: This issue might be related to Kerberos authentication. Sometimes, a domain controller might lose its Kerberos token. You can try running the following commands on each domain controller:
nltest /sc_query:your_domain
Test-ComputerSecureChannel -Server "DC_Name"
If you find a problem with the security channel, you can try using the Reset-ComputerMachinePassword command to reset the computer account password.
Time Synchronization: Kerberos requires that the clocks on the client and server are synchronized within a few minutes. Check for any time drift between the domain controller and the client machine.
Credential Manager: Clear any cached credentials for the hostname in the Credential Manager on the client machine.
Network Level Authentication (NLA): Disabling NLA on the RDP target might help but be aware that this could pose a security risk.
Windows Update Issues: Some updates can cause issues with RDP. Ensure that all your systems are fully updated. If the problem started after a specific update, you might need to consider uninstalling that update.
I hope the information above is helpful.
Best Regards,
Yanhong Liu