Windows 10: All in a sudden RDP to hostname cannot login with error message "Your credentials did not...

Hi there,We got 4 sites with 4 different subnets, all sites/subnets connected via IPSec VPN. All computers/servers joined to the same AD domain.Say I'm in site1, I can ping/trace with hostname without suffix to rest of the 3 sites. All in a sudden, since last Wed, I cannot RDP to servers in other 3 sites via hostname, but I can RDP to servers in other 3 sites via ip address. I can RDP to local subnets server via hostname or ipaddr without any problem.Tried with other win10/win11 computers in site1 also same result, so it seems not related to my win10 computer only.Tried to contact firewall

:)

 

RDP Credential Manager: Delay in accepting credentials

Hi,



Thank you for writing to Microsoft Community Forums.



We understand the difficulties you are facing a lag in time in accepting the credentials to RDP. Thank you for providing us the screenshot of the issue.



However, we would suggest you to post your query in TechNet
forums, where we have expertise and support professionals who are well equipped with the knowledge on RDP Credential Manager to assist you with the appropriate troubleshooting steps.



We await your response.



Aditya Roy

Microsoft Community – Moderator

 

RDP Client Hanging Before Prompting for Credentials

I help manage a small Windows environment of about 15-20 workstations/laptops, and the oldest desktop we have all of a sudden started hanging from anywhere between 1 to 5 minutes after entering the IP or hostname before functioning as expected.

Outline of Problem: Open mstsc, enter an IP, hostname, or FQDN, then click "Connect". Once the "Conenct button is clicked, the prompt grays out for between 1-5 minutes before it prompts for credentials. Everything seemingly works fine after that. No other
devices have this issue, and they're all in the same OU as the other Windows desktops and the same account works fine on other devices. It is not networked related, as the same issue occurs when connecting to devices that are on the same switch or remotely
over an L3VPN. To the best of my knowledge, no changes were made recently, so I am not quite sure what caused this. None of the other Windows box is having this issue and they mostly have the exact same software footprint with slight differences in hardware
(all are Dells). It's on Windows 10 Professional version 1809 and it's currently on the May build(.1217). I cannot confirm if this device specifically had the same problems on a previous version of Windows 10. While the connection is grayed out while waiting
for the credentials prompt to render, I am also still able to comfortably use the desktop without any issues.

Things I've tried:

• Connected via hostname, IP, and FQDN at credential prompt along with flushing DNS. All name resolutions are good.
• In the RDP options, I've tested disabling persistent bitmap caching, remote audio, printers, smart cards. I've lowered connection quality requirements and colors as well.
• Used multiple credentials, including testing the same credentials from other Windows 10 devices to the same destination
• Ensured any networking applications are closed/not running (primarily Cisco AnyConnect) and disabled all firewall and antivirus components
• Flushed DNS cache and confirmed name resolutions are correct
• Set the RDP process priority to "Realtime" and "High" in the task manager while confirming no bottlenecks in CPU/RAM usage before clicking "Connect"
• Added this registry key: HKLM\software\policies\microsoft\windows nt\Terminal Services\Client\fClientDisableUDP
• Confirmed I'm connected to the local domain controller (echo %LOGONSERVER%)

 

RDP Credentials Screen

As of this morning, after an automatic Windows update, the credentials page for RDP login has changed (to a flat grey background). It appears completely different and I want to make sure this is part of an official Windows update.