Forum Discussion
CirrusWindows server 2016 RDP from APM
Hi,
we have been using remote desktop with the application access from our F5 device for a while. We never had any issues until we tried to add connections to some windows server 2016.
The only error it gives us is "The connection cannot proceed because authentication is not enabled and the remote computer requires that authentication be enabled to connect." To be sure, I checked all the configuration and the different securities that might be related on the server to RDP. Strangely, we are able to do remote desktop to those servers from any other devices.
Finally, here's our version BIG-IP 11.6.0 Build 6.0.442 Hotfix HF6
Let me know if it rings a bell or if it's something that can easily be fixed.
Jonathan
No need to go further.
We found out that we need to change a registry key on any windows 10 or windows server 2016
- Navigate to this Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp
- Change “SecurityLayer” to a zero
It seem that the F5 Big-Ip act as a really old rdp client and it's blocked by Windows 10 or Windows Server 2016 even if on the GUI it's allowing connection from an older RDP client.
2 Replies
Jdemers_204143No need to go further.
We found out that we need to change a registry key on any windows 10 or windows server 2016
- Navigate to this Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp
- Change “SecurityLayer” to a zero
It seem that the F5 Big-Ip act as a really old rdp client and it's blocked by Windows 10 or Windows Server 2016 even if on the GUI it's allowing connection from an older RDP client.
Zuke_254875Altostratus
Jdemers, what health monitor do you use for your Windows Server 2016 pool? I'm currently using a standard TCP monitor, but I'd prefer something that was more robust and indicative of the service working. The deployment guides and iApp only list Server 2008/2012/2012R2.
