Forum Discussion
F5 Bigip as RDG Gateway, Windows 2016 Server
Hello,
i would like to youse my F5 Bigip 12.1.3 to act as a RDG Gateway. i used the iApp version for this scenario.
I have created successfully a NTML machine account in a Windows Server 2016 active Directory. When i connect via Remote Destopk i get invalid TS gateway credential.
I i use an NTML machine account in a Windows Active Dirextory 2012, the setop works as expected.
Is there any issue known between F5 acts as an RDP gatway and Windows Server/Active Directory 2016?
Best regards Heiko
It seems that Microsoft Server 2016 isn't supported yet. See section 'Remote Desktop Gateway Compatibility Matrix':
However, I found this post. Seems like a registry change under Microsoft Windows Server 2016 could solve the problem.
https://devcentral.f5.com/questions/windows-server-2016-rdp-from-apm-53075
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.
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com