Invalid Credentials when RDP'ing to PC , after DHCP and DNS were recently move to new server

Dan Potter 1 Reputation point

We have recently moved our DHCP and DNS services from Server 2008 R2 to Server 2019 (DHCP and DNS subsequently turned off , on the old server)

Whilst this appears to work okay (clients are connecting to the correct DHCP, and using correct DNS), it also worth noting that pinging hosts by name does return the correct IP#


Whenever I attempt to RDP via name ...(note: RDP via IP# continues to work), I get an "invalid credentials" message.....even though the credentials are correct. If I subsequently attempt to rpd via issues are encountered.

So far the only solution is to remove / add the host in question to the domain....which appears to resolve the issue.

Windows Server 2019
Windows Server 2019
A Microsoft server operating system that supports enterprise-level management updated to data storage.
3,150 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.
992 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Dave Patrick 415.2K Reputation points MVP

    You could try ipconfig /flushdns, ipconfig /registerdns, check the source and target both have valid DNS servers listed on connection properties, check for stale DNS records, check the time is correct on all involved.

    --please don't forget to upvote and Accept as answer if the reply is helpful--