I will see if I can check the user's event viewer for potential issues. I don't know how their firewall could be configured to allow traffic to other HTTPS web sites, but not our remote desktop gateway I thought the problem may be related to tunneling RPC through HTTP, but 2012 uses "pure" HTTP through port 443. "Ĭan you inform me as to why you think it needs to be open? Of this network design to provide remote access connectivity across multiple firewalls. Because most corporations open port 443 to enable Internet connectivity, RD Gateway takes advantage RD Gateway transmits RDP traffic to port 443 instead, by using an HTTP Secure Sockets Layer/Transport Layer Security (SSL/TLS) tunnel. Use the following commands: nslookup rdpservername1 ping rdpservername1 If the DNS name is not resolved properly, check your DNS settings or try connecting to a remote host using its IP address. This is because port 3389, the port used for RDP connections, is typically blocked for network Make sure the DNS address of the remote RDP host is correctly resolved from your computer.
#Rdp security package error windows
"Prior to this release of Windows Server, security measures prevented remote users from connecting to internal network resources across firewalls and NATs. From Overview of Remote Desktop Gateway on TechNet: Your computer cant connect to the remote computer because a security package error occurred in the transport layer. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under 'Windows 8.1/Windows Server 2012 R2' on. It is my understanding that port 3389 is not necessary for rdp sessions through a remote desktop gateway. This article describes an issue that occurs if you try to access the Remote Desktop Services (RDS) server through Remote Desktop Gateway (RD Gateway) service in Windows Server 2012 R2. 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. I can RDP just fine with XP etc and not everyone has this issue when using Windows 7.
The requested security package does not exist'. I get the following message after I enter my login details: 'An authentication error has ocurred.
#Rdp security package error windows 7
The users that cannot connect are behind a firewall at a customer facility. I have a strange problem when trying to RDP to another Windows 7 workstation or Windows 2008 server. 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 kommentar(er)
