Can ping the Remote IP address but not with 3389.

Perrin Hawver 1 Reputation point
2021-01-18T19:20:22.73+00:00

I've been having an issue with RDP on Windows 10. I use a VPN called GlobalProtect to connect to my work computer. I can connect to the VPN fine and I can ping my remote computer using

 ping <remote computer address>

successfully. However, when I try to RDP I get the generic error message that I cannot connect.
Also I have tried this command

Test-NetConnection -ComputerName "remote computer address" -CommonTCPPort "RDP" -InformationLevel "Detailed"

and it fails. I have also tried

telnet "remote computer" 3389

and it fails.

I have tried turning my firewall on and off. I have made sure the remote desktop service is running. I've turned the firewall on and allowed the port 3389 in the advanced menu. I've checked the registry to make sure 3389 was the default RDP port. I have tried just about everything that I have read on every forum post. None of it has worked.

I'm open to any suggestions. Also it's worth noting that I have been able to connect on a laptop running Windows 10 home edition. Is it possible I could copy over some settings or files from the computer it works on over to the computer it doesn't work on? Thank you.

Remote Desktop
Remote Desktop
A Microsoft app that connects remotely to computers and to virtual apps and desktops.
4,283 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Dave Patrick 426.2K Reputation points MVP
    2021-01-18T19:26:05.193+00:00

    Something here might help.
    https://www.howtogeek.com/131961/how-to-access-windows-remote-desktop-over-the-internet/

    --please don't forget to Accept as answer if the reply is helpful--

    0 comments No comments

  2. Jenny Yan-MSFT 9,326 Reputation points
    2021-01-19T06:48:12.203+00:00

    Hi,
    1. However, when I try to RDP I get the generic error message that I cannot connect.
    What is the exact error message for the RDP failure? How did you start the remote session? Via mstsc or other tools?

    2.Regarding the telnet failure, please check the suggestion below and verify the problem:

    • If you can connect by replacing "tserv" with the Terminal Server's IP address but not the host name, you may have a DNS or WINS resolution problem.
    • If you can connect when "tserv" is the host name, but cannot connect when "tserv" is the computer name, then you may have a NetBIOS name resolution issue with WINS or an LMHOSTS file.
    • If you cannot connect when "tserv" is the IP address, the host name, or the computer name, then it is likely that port 3389 is blocked somewhere in your WAN.

    Reference link:
    https://learn.microsoft.com/en-us/troubleshoot/windows-client/networking/use-telnet-to-test-port-3389-functionality#why-does-telnet-reports-that-you-cannot-connect

    3.Also it's worth noting that I have been able to connect on a laptop running Windows 10 home edition.
    How did you manage to remote to windows 10 home? Any third party tools or you mean remoting from windows 10 home?
    According to following, it is not allowed to remote to computers running a Home edition (like Windows 10 Home).
    Remote Desktop - Allow access to your PC
    https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/clients/remote-desktop-allow-access

    For the working and non-working computer, kindly confirm if they are in the same network environment, the same account or the permission of account.


    Hope this helps and please help to accept as Answer if the response is useful.

    Thanks,
    Jenny

    0 comments No comments