Windows Virtual Desktop Client can't connect

%3CLINGO-SUB%20id%3D%22lingo-sub-1496485%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Virtual%20Desktop%20Client%20can't%20connect%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1496485%22%20slang%3D%22en-US%22%3Eare%20you%20using%20this%20Windows%20Desktop%20Client%3F%20Please%20update%20to%20the%20latest%20version%20and%20try%20again.%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fvirtual-desktop%2Fconnect-windows-7-and-10%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fvirtual-desktop%2Fconnect-windows-7-and-10%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3EAlso%20mstsc.exe%20is%20not%20supported%3A%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fwindows-virtual-desktop%2Fblocking-older-and-unsupported-remote-desktop-clients-starting-6%2Fm-p%2F1438153%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fwindows-virtual-desktop%2Fblocking-older-and-unsupported-remote-desktop-clients-starting-6%2Fm-p%2F1438153%3C%2FA%3E%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1497600%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Virtual%20Desktop%20Client%20can't%20connect%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1497600%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F181812%22%20target%3D%22_blank%22%3E%40Soo%20Kuan%20Teo%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYes%2C%20I'm%20using%20the%20Windows%20Desktop%20Client%20and%20it's%20the%20latest%20version.%3CBR%20%2F%3EIn%20fact%2C%20since%20I%20have%20the%20problem%20there%20have%20been%20two%20updates%20of%20the%20clients%2C%20which%20didn't%20solve%20the%20problem.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnd%20I%20know%2C%20I'm%20not%20using%20mstsc.exe%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1499543%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Virtual%20Desktop%20Client%20can't%20connect%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1499543%22%20slang%3D%22en-US%22%3ECan%20you%20please%3A%3CBR%20%2F%3E1.%20setup%20log%20analytics%20for%20your%20WVD%20workspace.%3CBR%20%2F%3E2.%20Reproduce%20your%20problem.%3CBR%20%2F%3E3.%20wait%20for%20a%20few%20minutes%2C%20then%20go%20to%20your%20log%20analytics.%3CBR%20%2F%3E3.%20Please%20share%20your%20corelationid%20for%20the%20connection%20that%20has%20the%20issue.%3CBR%20%2F%3EI%20will%20take%20a%20look%20at%20your%20connection%20issue%20with%20your%20corelationid.%3CBR%20%2F%3E%3CBR%20%2F%3EThanks%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1492087%22%20slang%3D%22en-US%22%3EWindows%20Virtual%20Desktop%20Client%20can't%20connect%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1492087%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe're%20in%20the%20process%20of%20rolling%20out%20WVD%20to%20some%20users%2C%20one%20of%20which%20is%20me.%3C%2FP%3E%3CP%3EI%20can%20connect%20via%20the%20Web%20Client%20without%20problems.%20I%20can%20connect%20to%20a%20full%20desktop%20and%20start%20apps%20only.%20So%20no%20issues%20there.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHowever%2C%20with%20the%20Remote%20Desktop%20Client%20I%20receive%20the%20following%20error%20(screenshot%20attached)%3A%3C%2FP%3E%3CP%3E%22Your%20computer%20can't%20connect%20to%20the%20remote%20computer%20because%20a%20security%20package%20error%20occurred%20in%20the%20transport%20layer.%20Retry%20the%20connection%20or%20contact%20your%20network%20administrator%20for%20assistance%22.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOther%20colleagues%20can%20also%20connect%20without%20problems%20with%20the%20RD%20Client.%3C%2FP%3E%3CP%3EI%20also%20can%20connect%20from%20other%20devices%20with%20my%20account.%20So%20it's%20clearly%20something%20on%20my%20own%20device.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EImportant%20to%20note%20is%20that%20I%20can%20see%20all%20the%20WVD's%20and%20apps%20in%20the%20client.%3CBR%20%2F%3EIt's%20when%20I%20try%20to%20connect%20to%20it%20that%20it%20throws%20the%20error.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20I've%20done%3A%3C%2FP%3EClear%20all%20entries%20from%20the%20Credential%20Manager%20No%20proxy%20Not%20blocked%20on%20firewall%20Created%20this%20registry%20entry%3A%3CBR%20%2F%3EHKEY_CURRENT_USER%5CSoftware%5CMicrosoft%5CTerminal%20Server%20Client%3CBR%20%2F%3EName%3A%20RDGClientTransport%3CBR%20%2F%3EType%3A%20Dword%3CBR%20%2F%3EData%3A%201%26nbsp%3B%20Created%20this%20registry%20key%3A%3CBR%20%2F%3EKey%3A%20HKLM%5CSYSTEM%5CCurrentControlSet%5CControl%5CLsa%3CBR%20%2F%3EName%3A%20LMCompatilityLevel%3CBR%20%2F%3EType%3A%20REG_DWORD%3CBR%20%2F%3EValue%3A%203%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHonestly%20no%20idea%20why%20it%20doesn't%20work.%3C%2FP%3E%3CP%3EI%20don't%20think%20that%20my%20device%20differs%20anything%20from%20those%20of%20my%20colleagues%20and%20from%20other%20domain%20joined%20devices.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBtw...%3CBR%20%2F%3ENormal%20RDP%20to%20on-prem%20servers%20is%20working%20just%20fine.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20thoughts%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

Hi,

 

We're in the process of rolling out WVD to some users, one of which is me.

I can connect via the Web Client without problems. I can connect to a full desktop and start apps only. So no issues there.

 

However, with the Remote Desktop Client I receive the following error (screenshot attached):

"Your computer can't connect to the remote computer because a security package error occurred in the transport layer. Retry the connection or contact your network administrator for assistance".

 

Other colleagues can also connect without problems with the RD Client.

I also can connect from other devices with my account. So it's clearly something on my own device.

 

Important to note is that I can see all the WVD's and apps in the client.
It's when I try to connect to it that it throws the error.

 

What I've done:

  • Clear all entries from the Credential Manager
  • No proxy
  • Not blocked on firewall
  • Created this registry entry:
    HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client
    Name: RDGClientTransport
    Type: Dword
    Data: 1 
  • Created this registry key:
    Key: HKLM\SYSTEM\CurrentControlSet\Control\Lsa
    Name: LMCompatilityLevel
    Type: REG_DWORD
    Value: 3

 

Honestly no idea why it doesn't work.

I don't think that my device differs anything from those of my colleagues and from other domain joined devices.

 

Btw...
Normal RDP to on-prem servers is working just fine.

 

Any thoughts?

3 Replies
Highlighted
Highlighted

@Soo Kuan Teo 

 

Yes, I'm using the Windows Desktop Client and it's the latest version.
In fact, since I have the problem there have been two updates of the clients, which didn't solve the problem.

 

And I know, I'm not using mstsc.exe

Highlighted
Can you please:
1. setup log analytics for your WVD workspace.
2. Reproduce your problem.
3. wait for a few minutes, then go to your log analytics.
3. Please share your corelationid for the connection that has the issue.
I will take a look at your connection issue with your corelationid.

Thanks