Forum Discussion

djshaunvt's avatar
djshaunvt
Copper Contributor
Nov 01, 2022

Windows Desktop Is Suddenly Broken Connecting With Hostname

Hi all.

 

I would be so greatfull if someone can share their knowledge with me because I have tried just about everything to solve this issue we are having for about 2 weeks now.

 

When connecting from site A lets call it, where out IT guys are located to a few computers / servers in other AD sites we are presented with a Remote Desktop Box stating the following: "Your Credentials did not work. The credentials you used to connect to (Insert Host Machine Name Here) did not work. Please enter new credentials. I tested Remote Desktop from a couple other machines in site A and the same message. I have uninstalled the most recent updates on the remote PC in lets call it AD site B. The one in this example is a Windows 10 machine. Latest update involved being  KB 501 8410 with no joy. i installed the later windows update to fix some issues regarding KB 501 8410 with no luck. The thing is I can remote to some other machines with KB 501 8410 installed so kind of ruled that out.

 

Windows firewall is off just to test as well as AV removed.

 

I have installed a brand new machine with Windows 10 (no updates installed and not joined to the domain to test Remote Desktop from it to the problematic machine in site B. It also brings up the same error message. I then joined it to the domain and updated fully - No luck. Still presented with the message when connecting to the machine in site B.

 

If the problematic remote PC in site B is rebooted on the off chance remote desktop then works again and once rebooted again, I am presented with the same message connecting from my work PC or any other PC in Site A. If I connect over VPN from my house PC to the problematic PC in Site B RDP works fine.  I CAN connect to the problematic PC in site B from our IT department machines in site A by using the IP Address. - DNS is fine as far as I can see as it does resolve to the correct IP Address. I can also use VNC to connect to the problematic machine in site B and logon just fine.  the credentials in question is the domain admin account.

 

The other thing is its domain controller in site B also sometimes brings up the same message (Server 2008r2) and when rebooted like 3 times we are able to login once again.  Same goes for other computers / Servers in lets call it AD site C D E.

 

Any ideas would be appreciated

 

 

  • Broken Connecting With Hostname

     


    I'll assume by this you meant by ip address succeeds? If so I'd check that the time sync across domain is functional.

     

     

    • djshaunvt's avatar
      djshaunvt
      Copper Contributor

      Dave Patrick thank you for the feedback and suggestion.

       

      I forgot to mention this was one of the things i checked and checked again this morning.

       

      The time sync between all sites is spot on correct 

      • Dave Patrick's avatar
        Dave Patrick
        MVP

        Might check that all members are using the static address of domain controller listed for DNS on connection properties and no others such as router or public DNS. Also check domain health is 100% (dcdiag, repadmin), check the system and dfs replication event logs for clues.

         

         

Resources