I made sure the RDP port is opened from my side to the server by using Telnet server_ip 3389 The remote desktop window always stuck at "Configuring remote session." before giving the error messages This computer can't connect to the remote computer.
SERVER 2016 REMOTE DESKTOP PORT WINDOWS 10
When I try to connect to the server from my home, it wouldn't connect at all, I have tried several machines (physical and virtual)with several windows 10 versions(pro~enterprise) and I always get one of two massages
SERVER 2016 REMOTE DESKTOP PORT SOFTWARE
Client computers can now connect successfully.We have an online Windows server 2016 that we connect to from several locations(from outside and inside the office)remotely using the native remote desktop software in our machines, we are using windows 10 with latest updates and every thing is just working fine. Then, on a reboot, RDG can gather the right certificates and present them to connecting client computers. You’ll only see things if you enable SCHANNEL logging.īy browsing to the certification authority’s web site, Windows add the right certificates to the local computer certificate store the right certificates go in the right location. So, nothing is ever logged on the server. This TLS negotiation happens very early, before Windows does anything else. So, when the RDP client was negotiating TLS, it was being aborted because the server wasn’t presenting it’s certification authority certificates. I’ve seen this before while I had the certificate, the RDG server didn’t have all the certificate authority certificates in the hierarchy. Once I browsed to the certification authority’s web site on the RDG server, then rebooted the RDG server, it started working.
I had installed a certificate on the RDG server. On the Gateway server > Start > Administrative Tools > Internet Information Services (IIS) Manager > Tasks > Edit Deployment Properties.Ĭertificates > RD Gateway > View Details > Is it in date?Įverything is OK? But I’m Still Getting This Error? Are you publishing the Gateway with something else like Web Application Gateway? Threat Management Gateway? Load Balancer? Look in that direction.Īlso See Remote Desktop Web Access – Connection Error Related Articles, References, Credits, or External Links In some cases you need to set the public name of the the Remote Desktop Gateway server, in the servers IIS Settings. The important thing is when I ping this name, it resolves to the correct IP address, (mine responds to pings, yours probably wont if you’re connecting though a firewall.) And this may not be the hostname of the server! As you can see in the image above the Gateway server name is set to. The machine trying to connect needs to be able to resolve the ‘public name’ of the Remote Desktop Gateway server. Try reconnecting later or contact your network administrator for assistance. Your computer can’t connect to the remote computer because the Remote Desktop Gateway server is temporarily unavailable. Type a valid Remote Desktop Gateway server address. Your computer can’t connect to the remote computer because the Remote Desktop Gateway server address is unreachable or incorrect. Server Manager > Remote Desktop Services > Collection > Task > Select your collection > Task > Edit Deployment Settings > Certificates > Check and reinstall each one as required.
You normally see this error if one (or more), of your Remote Desktop Role servers does not have the correct certificate installed on it, (or the certificate it does has has expired). Your computer can’t connect to the remote computer because your computer or device did not pass the Network Access Protection requirements set by your network administrator.Contact your network administrator for assistance. HKCU > SOFTWARE >Microsoft > Terminal Services ClientĪlso See Remote Desktop Web Access – Connection Error
0 kommentar(er)
