Suddenly, cannot RDP to server using DNS names- only IPs

JDMils 51 Reputation points
2022-12-15T04:25:40.57+00:00

We have a mix of Windows servers, one server is a Windows 2012 Datacenter server which has been working well until a few days ago. I try to logon to the server from a jump box (running Windows server 2019 Datacenter) using the server's DNS name (both short & FQDN) and it asks for my credentials but then shows the error "Your credentials did not work". I know my credentials are OK because I can log into the same server using the IP and strangely if I add a "." dot to the end of the server's FQDN, I can logon OK.

I cannot see any issues in any of the Windows Event Logs.
PING -a <DNS_Name> shows the correct FQDN name.
NSLOOKUP <IP> shows the correct FQDN name.

Does anyone know what could be the issue?
Why does adding a dot after the FQDN work?

Remote Desktop
Remote Desktop
A Microsoft app that connects remotely to computers and to virtual apps and desktops.
4,251 questions

9 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Corey Speed 0 Reputation points
    2023-02-20T11:43:54.16+00:00

    Also having this issue, was there any update/fix for the issues ?

    Same error here

    RDP:

    FQDN: not work

    IP: works

    FQDN with a final dot: works

    0 comments
  2. Tony Guzzardo 0 Reputation points
    2023-03-01T14:40:46.6433333+00:00

    Just want to get on board saying we are recently experiencing similar issues with a couple 2019 STD servers. So frustrating but at least the IP works.

    0 comments
  3. Gantry G 0 Reputation points
    2023-03-03T21:13:37.97+00:00

    We are having the same issue... I assume an MS patch some time ago caused this...

    0 comments
  4. Marco Brondsema 0 Reputation points
    2023-03-20T19:14:28.5933333+00:00

    Had the same problem.

    flushed the dns on my system solved it for me

    ipconfig /flushdns

    0 comments