Oracle Secure Global Desktop: NLA Enabled Windows Sessions Fail to Launch Connecting To Desktops Using VRDP Protocol (Doc ID 1990145.1)

Last updated on MARCH 24, 2015

Applies to:

Oracle Virtual Desktop Infrastructure - Version 3.5 to 3.5.1 [Release 3.0]
Oracle Secure Global Desktop - Version 4.7 to 5.1 [Release 4.0 to 5.0]
Information in this document applies to any platform.

Symptoms

When trying to launch Oracle Virtual Desktop Infrastructure (VDI) managed Windows desktops from a Oracle Secure Global Desktop (SGD) session, the Windows Desktop connection is created but fails to complete. The SGD client shows a window with white content for a few seconds and then disappears.

At the same time as the launch failure,  the VDI RDP Broker log in /opt/SUNWvda-rdpb/var/log/  shows an error similar to the following:

2015/03/07 10:18:26.917 ERROR: VDA query failed: Incorrect username or password.[DirectoryResponseCode=49]

The SGD server and SGD client, does not provide any indication within its logs as to the cause of the failure.

Upon closer examination, the SGD Windows application configuration indicates that Windows Network Layer Authentication (NLA) enhanced security is enabled, while the VDI network configuration for the  VDI Desktop pool in use shows that the VRDP protocol is being used to connect to the target assigned desktop, rather than MS-RDP.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms