I have the identical problem, which I discovered today after installing Cox McAfee Security Suite. My Windows 7 Professional remote desktop does not work for incoming remote desktop connections even after opening port 3389 in the McAfee firewall. As described by "katt", when I turn the McAfee firewall off, I connect with no problem.

Your computer can’t connect to the remote computer because the Remote Desktop Gateway server’s certificate has expired or has been revoked. Contact your network administrator for assistance. In most cases this should be easy to fix, if you use self signed certificates make sure your CRL settings and/or OCSP settings are correct. Despite all of this I can't connect to this machine via Remote Desktop. All other network ports seem to work fine and traffic works two directions. If I run: netstat -a I also don't see anything listening on port 3389. As a result it seems Remote Desktop isn't running despite all of what I've done. Dec 30, 2016 · Can't connect w/ remote desktop from one PC but others work They're all running Win10 on a private home network connection and all allow remote desktop connections. I use the same local username/password on all. Remote Desktop uses the Remote Desktop Protocol (RDP) and enables you to connect to and use your instance in the same way you use a computer sitting in front of you. It is available on most editions of Windows and available for Mac OS. I have the identical problem, which I discovered today after installing Cox McAfee Security Suite. My Windows 7 Professional remote desktop does not work for incoming remote desktop connections even after opening port 3389 in the McAfee firewall. As described by "katt", when I turn the McAfee firewall off, I connect with no problem. And use another PC to connect this PC through remote desktop, I can't! After typing the PC name (or IP address) to connect to, it wait for a short time and prompt me the machine to connect again (just like I haven't press the connect button". But when I type "telnet pc_name 3389" in command prompt, it accepts the connection.

This computer can't connect to the remote computer. Additional resources. If none of these errors occurred and you still can't connect to the VM via Remote Desktop, read the detailed troubleshooting guide for Remote Desktop.

Mar 12, 2020 · But today, I can’t connect any machine from my server machine via Remote Desktop Client (RDP) tool. Note: – I can ping the Remote machine from my Local server. – I cannot connect Remote Desktop (RDP) only from my server machine that I am using for Administrative task but I can connect same machines from other Server machine.

Re: Can't connect to remote desktop! I use that address with the port number on any other network and it works on remote desktop. When I use chrome on my phone it just keeps trying to load a webpage but it literally just stays a white screen when I try the address with the port number. Oct 31, 2019 · You can't use Remote Desktop Connection to connect to a computer using Windows 7 Starter, Windows 7 Home Basic, or Windows 7 Home Premium. Members of the local Administrators group can connect even if they are not listed. Resolution 2: Port assignment conflict Remote Desktop can't connect to the remote computer for one of these reasons: 1) Remote access to the server is not enabled 2) The remote computer is turned off 3) The remote computer is not available on the network Make sure the remote computer is turned on and connected to the network, and that remote access is enabled. - Connect using Remote desktop - Don't forget to start the IPSec service and set its startup mode to Automatic. Regards, BalintN. 1 Votes Share Flag Collapse - Thanks for the info, glad that you