Windows 10: I have a windows laptop machine that used to be able to rdp to another windows machine. Not...

I made sure the machine being remoted into was pingable from the other computer, that it was allowing rdp access as well. Both machines run on windows 11. I also remoted in from a different machine successfully. The issue seems to be from the machine that is initiating the rdp session.

:)

 

Wasn't able to RDP into windows 10 machine. Even with firewall off.


Hi Guys,

I was able to RDP into windows 10 when i first install last Wednesday with other machine of the same domain. And today, I wasn't able to RDP in to my Window 10. I got a error of (the remote connection has timed out. Please try connecting to the remote computer again.) Under the remote setting, I choose (Don't allow remote connections to this computer). I have a different error, so clearly my computer was able to communicate to windows 10 but wasn't able to connect.

I was able to RDP out to other machine using window 10, it just don't accept RDP from other computer. Anyone of you having this problem ?

 

Slow RDP connection to host machine after updates

Hello,



Thank you for writing to Microsoft Community Forums.



I understand that the RDP connection to the host machine is slow after the updates.



As the issue is related to RDP connection on Virtual Machines, I suggest you to post your query on

TechNet forums, where we have experts who have more knowledge on Virtual Machines and RDP connections.



Hope it helps.



Regards,

Prakhar Khare

Microsoft Community – Moderator

 

RDP between two windows 10 21H2 machines fails

I have two Windows 10 Pro 21H2 machines (a laptop and a desktop). I have always been able to RDP from the laptop to the desktop without a problem until I installed the 21H2 update. After the update, I get the message: "The credentials that were used to connect to DESKTOP_NAME did not work. Please enter new credentials." Has anyone else had this problem with RDP between two 21H2 machines?

After every windows update is installed, I had always gotten a "warning" that the credentials for the machine I was connecting to had changed and I've always assumed this had to do with the OS update, but I was always able to select "OK" and accept the change in creds and continue to connect successfully. After the update to 21H2 I was never asked, and the connection just fails.

Both logins were local logins before I connected them to my Microsoft account (that was a long time ago). So, when I login to the local machine I use a PIN to login, but when I RDP into the machine, I always used the local password to the local account. I have wondered if being connected to my Microsoft account on both machines would cause problems, but until I installed 21H2, I haven't had a problem.

As a test, I created a local admin account that's not connected to a Microsoft account, and I can RDP into that account remotely from the laptop without a problem, so I think it's the Microsoft attached account that doesn't work. I've been thinking about either disconnecting them from the Microsoft account or creating new accounts that aren't connected to Microsoft.

Has anyone worked through this problem with success?