Share via

Remote Desktop still not working outside local subnet

Chris A 6 Reputation points
2025-04-14T14:21:28.56+00:00

This previous question (which wasn't answered) covers the issue that still occurs with Windows 11 and RDP:

https://learn.microsoft.com/en-us/answers/questions/2187781/why-is-it-that-some-windows-11-computers-will-not?page=2&source=docs#answers

And not every Windows 11 computer, but some of them. I believe ones upgraded from 10, it works properly.

Issue is, as was described there, RDP works from within the same subnet. If you connect to that network via a VPN (so you end up on the VPN subnet) you cannot connect to the Windows 11 host, but you can connect to Windows Server 2012/2016/2019/2022 and Windows 10 hosts on the same subnet just fine.

Is this ever going to be fixed? It was indicated in the other thread that it should have been fixed in December, but we are into April of the following year now and it's still ongoing.

Remote Desktop
Remote Desktop
A Microsoft app that connects remotely to computers and to virtual apps and desktops.
4,777 questions

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Geoff McKenzie 860 Reputation points
    2025-05-01T01:29:11.1966667+00:00

    Hi Chris and Tom,

    I haven't seen this scenario personally, however here are a few thoughts that I hope you haven't tried/considered. Maybe one of them will lead you to something actually helpful ????

    These are mostly based on various search results I am sure you have already found (e.g. https://windowsforum.com/threads/fixing-windows-11-remote-desktop-issues-after-24h2-update.352977/) but...

    I assume you have also reviewed the reported KBs.

    RDP Firewall Rules - Edge Traversal.

    This is a random thought based on some of your senario statement.

    Run this in powershel (as admin)
    Get-NetFirewallPortFilter | Where-Object {$_.localport -eq 3389} | Get-NetFirewallRule
    on both an affected and unafected machine and see if they are different - especially re
    EdgeTraversalPolicy : Block
    I doubt it will have an impact as you stated you have disabled Windows Firewall but ....

    Change RDP to use TCP only

    Again, your trace shows the TCP traffic so the fact that UDP may be enabled shouldn't be contributing but may be worth a try. There is a Local/GPO policy setting for "Select RDP transport Protocol" you can set to TCP only.

    User's image

    Change the RDP port

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp\PortNumber

    Just as a test - Reported in other searches as a potential work around ????

    Play with/disable the "Select network detection on the server" options

    User's image

    I am not sure about this one as it reads more like it might help with maintiaing connection rather than establishing connection but again .... may be worth considering.

    I am not sure if any of that will help but I will be interested if you find a solution.

    Good luck

    1 person found this answer helpful.

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.