Windows 10: RDP connection Problem. Only Domain computers don't connect.

Windows 10 Pro, 22H2. This is a RDP problem.I can connect to another computer in a different state using RDP. However, once this same computer joins the company Domain it will not connect.I get the message that the credentials don't work. It didn't help removing the computer from the Domain. I tested this on 3 different computers. Brand new installation. Also, trying to change Policy rules, ie Lan Manager Auth level. It is greyed out. I couldn't change it, even though I am the admin of the computer.I can RDP to any computer within my physical network, and the computers that are connected to us

:)

 

Slow initial RDP connection

Hello.

I have a strange problem: since we recently moved from a 2003 domain (I know, way too long used) to a 2016 domain (no domain upgrade but a fresh install), RDP to a PC is taking a long time to login. A connection is made, but the
RDP window shows a spinning circle at “Welcome” for around 90 seconds. After this, for the most PCs the desktop is shown and the RDP connection is as fast as it should be. Some PCs however never login, the welcome keeps spinning.
Even worse: if you disconnect/connect the RDP connection a couple of times and you try to reconnect again, the target PC will never login and even physically you are unable to login… a hard reset only will solve the problem…

This behavior is only when RDP to Windows 7 or Server 2012. Logging in remote to Windows 10 or Server 2016 works without any delay. I tried different combinations:

PC A taken out domain and PC B taken out domain: RDP from A to B no problem

PC A taken out domain and PC B taken out domain: RDP from B to A no problem

PC A taken out domain en PC B member of domain: RDP from A to B 90 sec delay at logging in

PC A taken out domain en PC B member of domain: RDP from B to A no problem

PC A member of domain en PC B member of domain: RDP from A or B to B or A 90 sec delay at logging in

PC A member of domain but no GPO policies applied and PC B member of domain but no GPO policies applied: RDP 90 sec delay at logging in

PC A and PC B are Windows 7 Pro, fully updated or vanilla.

I tried all the GPO fixes found on the net about RDP tweaking, changing ports, or adding
enablecredsspsupport:i:0 to default.rdp file.

The eventlog (of RDP or terminal services) of the target PC is not showing any errors.

Somehow the new domain is causing this behavior…

Thanks in advance,

 

RDP and Network Connection Drops While on Ethernet

Sam,

1. Even without issuing the ping -t command I will experience a RDP drop and network bottleneck
2. RDP clients are the same version
3. No firewall setup
4. All connecting with the same cables from similar ports

winbox1 has full duplexTrue
winbox2 does not have duplex True

Pretty sure it's something with the network setup, I might reinstall the OS

 

Application is hanging over RDP connection only if connection is started from domain member computer.

Customer has really weird problem - they are using ERP system over RDP connetion, both desktop sessions and RemoteApp sessions, depends of user work profile.

Now, about month ago we got some calls, that ERP system is staying in "Not responding" status for 15-30 minutes, if some reports have been started. Started troubleshooting and now I have isolated the way how to reproduce the issue. It occurs only when the RDP connection is started from domain member computer and it does not occur, if the computer that does start the session, does not belong the AD. Affected is only the ERP system client that is installed on the RDS session host, if that does not respond, all other apps are working fine.

Tried already every single thing that I can imagine - disabled redirected devices and services one by one, tried to force only TCP or UDP connections, changed authentication methods, all remains the same. When I try to connect from computer that is not the member of the same AD that session host is belonging, everything works fine.

I isolated RDP connection as the problem cause, because if I connect to the user session using our RMM tool and disconnect the RDP session, the report that was in not responding state, opens immediately. When I don't disconnect that RDP session, ERP remains in not responding state.

Any ideas, what could cause that behavior?