windows server 2012 remote desktop not working

Verified can telnet to server by name AND IP on port 3389 Checked Regedits for SecurityLayer and Ports Here's a quick summary of some of the troubleshooting, not in this order: RDP will not work on the public IP nor will it work on the local LAN.įrom Public you get the error: An internal error has occurredįrom LAN you get: Computer can't connect to the remote computer You should deploy certificates from your internal certificate authority.I have an RDP Gateway Server that has a public IP for RDP. Sure, you can deploy self signed certificates, but that’s not a good idea. asking for credentials (no Single Sign On)Īs part of the RDS reployment, the assistant kindly asks for certificates.Or if you are already using RDSH, and you want to try VMware Horizon View.īut three things can really spoil the usage of RemoteApps:

This can be handy, if you migrate from RDSH/ Citrix published desktops to VMware Horizon View. Application can then delivered using RemoteAPps. You can deploy virtual desktops without any installed applications. or they can click on a file that is associated with a RemoteAppĮven in times of VDI (LOL…), RemoteApps can be quite handy.

Users can simply start a link on the desktop or from the start menu (RemoteApps and Desktop connections deployed by an MSI or a GPO).

Users can start RemoteApps using a special RDP file.

Users can start RemoteApps through the Remote Desktop Web Access.

RemoteApps can be used and deployed in various ways: Software and data are kept inside the datacenter. Another benefit is, that data is not leaving the datacenter.

Because the application is running on a RDSH, you can easily deliver applications to end users. This information might be outdated.Ī RemoteApp is an application, that is running on a Remote Desktop Session Host (RDSH), and only the display output is sent to the client.

Windows server 2012 remote desktop not working