Share via

All in a sudden, cannot RDP to remote site servers via hostname but can RDP via ipaddr, how to fix?

eyeteelo 11 Reputation points
2022-11-09T07:13:59.043+00:00

Hi there,

In short, since last Wed or so, all in a sudden, my win10 computer cannot RDP to remote subnet server via hostname but no problem if RDP via ipaddr, the symptom is keep saying wrong password but I'm 200% sure I typed the correct password, it's not related to "fat finger", any idea what's wrong & how to fix?

Long story here:
Let's say we got 3 sites, A,B,C with 3 different subnets, I'm physically located in site A & I'll do routine check on all serves in site A,B,C. Since last Wed or so, sudden found out that my win10 computer cannot RDP to remote servers in site B&C via hostname, in which the symptom is keep looping at wrong password; but no problem if RDP via ipaddr. However for all servers in local site A, I can RDP via hostname without issue.

Initially I thought it might related to firewall bugs or what, so I contacted firewall vendor support, captured traffic packets for them to study, & they concluded that nothing wrong with firewall & suggest me to check with M$, that's why I'm writing the post here.

Tried winsock reset on my computer, didn't help.
Tried to change from DHCP to fix ipaddr on my computer, didn't help.
Tried hard code remote site servers in host file, didn't help.

Tried wireshark to capture packets on my computer, found that when problem happened, will have TCP src port :49868 dst port:3389 [RST, ACK] in which to my best understanding is TCP RESET. In fact, from firewall log also found related entry with description "TCP reset from client", but I've no idea why such TCP reset happened on my computer during the RDP connection.

My own computer is Win10pro 21h2 joined domain; also tested with another Win11pro 22h2 workgroup computer, also same problem.

Also observed that if remote site server is Win2003, then no such strange problem, can RDP via hostname. Seems the RDP via hostname problem only happening on Win2008/2012/2016 servers.

I've seen other post with similar problem but that was specific to win11 22h2 client computer only https://learn.microsoft.com/en-us/answers/questions/1075182/windows-credentials-don39t-work-after-22h2-update.html

Anyway as I'm not the only one so maybe something wrong with RDP just recently?
At this moment I'm ok to RDP via ipaddr so I can do my works, but of coz I want to fix it permanently, many thx!

Windows for business | Windows Client for IT Pros | User experience | Remote desktop services and terminal services

6 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Niyas 10 Reputation points
    2023-01-31T10:31:12.4333333+00:00

    Mine has been resolved after restarting netlogon service in server.

    2 people found this answer helpful.
  2. Emmanuel Riggs 1 Reputation point
    2022-11-16T14:54:11.757+00:00

    Hi, have you been able to find a solution for this? im having the same issue

  3. Emmanuel Riggs 1 Reputation point
    2022-11-17T18:06:28.703+00:00

    Hi, I actually found the fix, remove the update KB5019966 from all your Domain controllers at least until this issue gets patched. it Looks like the update broke the Kerberos authentication causing the RDP connection to fail authentication when using the host name.

    0 comments
  4. Mohammed Imran Mohammed Saeed Chivelkar 1 Reputation point
    2022-11-21T04:52:07.743+00:00

    Its due to November patch, it impact the Kerberos authentication.
    Workaround to be added on patched domain controller.
    reg add HKLM\System\currentcontrolset\services\kdc /t REG_DWORD /v ApplyDefaultDomainPolicy /d 0 /f

  5. Mohammed Imran Mohammed Saeed Chivelkar 1 Reputation point
    2022-11-27T05:40:12.233+00:00

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.