![]() It is my understanding that port 3389 is not necessary for rdp sessions through a remote desktop gateway. Since the transport should be HTTP (instead of RPC over HTTP), I don't think this should be a problem.Īny help in pointing me in the right direction would be appreciated. On the gateway or if the customer has blocked traffic in some way that does not allow RDP. I'm having trouble trying to determine if I have not configured something correctly The do not have trouble connecting to normal secured web sites through port 443. ![]() The users that cannot connect are behind a firewall at a customer facility. Remote Desktop Gateway - Windows Server 2012 R2 (SSL certificate has been installed and chain verified)Ĭlient computer that cannot connect - supports RDP 8.1. Remote Desktop Session Host - Windows Server 2008 R2 Most users, connections are not a problem. "Your computer can't connect to the remote computer because a security package error occurred in the transport layer." For A few of our users receive the following error when attempting to establish a remote desktop session.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |