RDS/RDP : Connection reset by client on some networks

alex a 61 Reputation points
2022-12-16T09:58:27.713+00:00

I have an issue with RDS access on ONE network only (assuming 10.10.0.0/24) It give me "crendetials didn't work" message just after log in.

RDS access is ok all other networks (10.10.3.0/24 and 10.40.0.0 for example). When i connect to server 10.10.0.16 from VMWare Console, i can RDS other servers in 10.10.0.0/24. NLA is activated for ALL networks.

My client is 10.0.4.101 but when i trie to connect from 10.40.0.11 to 10.10.0.16, same error "crendetials didn't work"

As local admin, i can connect.
I also can connect when i m on 10.10.4.0 network.

On wireshark :
271372-wireshark.png

on event viewer :
271362-rdsevent.png

id event 143, socket TCP error 64
id event 226 error code 0x80070040
id event 103 reason 4407
what i ve done :

sfc /scannow >> no errors
dism check/scan/restore health >> no errors
netsh interface ipv4 set subinterface "Ethernet0" mtu=1452 store=persistent >> no change
deleted rds selfsigned certificate
restarted rds services
Test-NetConnection -ComputerName 10.10.0.16 -CommonTCPPort "RDP" -InformationLevel "Detailed" >> all ok
GPOs to disable ModuleRemoteFX.
Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\ DWORD: MaxOutstandingConnections VALUE: 10000
And still no luck. Any advice?
unjoin and rejoin domain: OK >> but after another reboot KO.

Thanks.

Windows for business Windows Client for IT Pros User experience Remote desktop services and terminal services
{count} votes

1 answer

Sort by: Most helpful
  1. Jan Werner 0 Reputation points
    2024-04-05T11:41:23.0366667+00:00
    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.