Windows 10: Why will some windows 11 Computers will not respond to RDP requests coming from another subnet

We have recently run into some RDP issues that seem to only affect some windows 11 computers. Example. I have 2 computers on site. Both are Windows 11 Pro x64 240.519. When I am connected to an SSL VPN I can connect to one without issue and cannot connect to the other one. I can ping and browse to both. I ran wireshark on the destination computer The PC I am remoting into. When I RDP from the LAN I get the following 2 packets initiating the session and it works fineNow when I connect over the VPN I get the followingSo you can see the destination computer RECEIVES the RDP request but just choos

:)

 

Cannot RDP to specific host in specific subnet

This issue is ripping me a new one so I'd really appreciate any help...

Layout:

desk and test are on subnet 1

frank is on subnet 2

vpn is on its own subnet but is passed subnet 1 in the vpn config (handled by router)

all are windows 10

there is full routing between subnets (pass all traffic)

ping works to all hosts, telnet over 3389 works to all hosts, TightVNC works, just rdp is acting up

window firewall is completely off on frank, desk, and test

test is a completely fresh install of windows with all updates

there is no windows domain or anything and all computers are in "WORKGROUP"

rdp testing table:

_from_ -> _to_ _result_

desk -> test yes

desk -> frank no "the logon attempt failed"

frank -> test yes

frank -> desk yes

test -> desk yes

test -> frank no "connects and show lockscreen but says 'username or passowrd is incorrect try again'"

vpn -> desk yes

vpn -> frank yes

vpn -> test yes

keep in mind telnet 3389 works even when rdp doesn't

for some reason frank is the only one that others cannot connect TO (it can connect to others) and for some reason vpn clients are able to connect to frank.

Troubleshooting:

On frank when I attempt to connect from desk/test I sometimes get the following error in frank's event log:

A CredSSP authentication to TERMSRV/<desk/test ip> failed to negotiate a common protocol version. The remote host offered version 4 which is not permitted by Encryption Oracle Remediation.

Microsoft recommends this page:

CredSSP updates for CVE-2018-0886 - Microsoft Support

Based on the above, tried setting to "vulnerable" or whatever, no good.

So I update all windows machines to the latest build so now all rdp clients are version 10.0.17134 and it doesn't help at all except now when test fails to connect to frank it has the same message as desk, that is "the logon attempt failed" and no longers shows
the logon screen as it did previously.

I also tried creating a new account "test" on frank but that got the same error.

IF i connect frank to subnet 1 everything works fine so I think it is simply something to do with that host being on a differnet subnet. Is there anything I can set to allow rdp even though it is in another subnet. How can I rdp to frank and have it remain
in subnet 2? please help!

 

RDP sessions on mostly windows 11 computers stop responding

4 or 5 weeks ago we started having problems with windows 11 RDP sessions freezing. We are connecting to a Windows terminal Server 2019. The terminal server is running fine, but the built-in RDP app on our users computers just suddenly stops responding to mouse clicks etc. We can force quit the RDP, but it will sometimes happen again every few minutes. The Microsoft store RDP app works more consistently, but it will only use one screen (most users have two or three) and doesn’t redirect printers. Seems to be mostly Windows 11 computers with the problem, though I now have one Windows 10 user with the same issue but less frequently. I have a feeling that a recent MS Update may be the reason? Anyone else having this issue? It is causing a lot of headache in our office.

 

RDP to dual NIC Windows 10 server, only one responds

Hi all,

I have a Windows 10 Pro at home which I access remotelly using RDP. The server is using two interfaces, one Ethernet and one Wifi, both on the same subnet.

I can only RDP into the device using the Ethernet IP address. If I try to RDP to the Widi interface, it will not respond. Is there a way to make it also respond? Or, if we consider the 3389 port can only respond to one interface, can I choose which interface
will it respond to?

Regards,

Persio