Forum Discussion

benjaminfrei's avatar
benjaminfrei
Copper Contributor
Jun 11, 2020
Solved

not able to connect to WVD from win64 client (latest)

Hi everyone Just finished my first WVD test-deployment based on ADDS. Everything is running fine except connections from windows x64 based devices. HTML5 web client and IOS Remote Desktop App work w...
  • benjaminfrei's avatar
    benjaminfrei
    Jun 14, 2020

    Found a solution to the problem, great work done by Micha Wets! https://www.cloud-architect.be/2020/04/19/solution-for-the-0x204-error-when-connecting-to-windows-virtual-desktop-wvd/

virtualmanc's avatar
virtualmanc
Iron Contributor
Jun 12, 2020

benjaminfrei Hi, it maybe a firewall/antivirus issue??? Try temporarily disabling your windows firewall or any antivirus/malware software you have on the windows device.

 

Also do you have another windows device you can test from??

benjaminfrei's avatar
benjaminfrei
Copper Contributor
Jun 12, 2020

virtualmanc question: my ADDS setup (cloud only tennant, no on-prem AD) was build with the same top-leveld-domain as the public tenant has (split brain dns). In my understanding this should not be a problem, also when using azure connected enddevices. do you agree or could that be an issue? (nameresolution fails)

  • virtualmanc's avatar
    virtualmanc
    Iron Contributor
    Jun 12, 2020

    benjaminfrei If it was a name resolution problem the web client and the IOS would fail also. Has to be something local on the windows device which is blocking the connection

    • benjaminfrei's avatar
      benjaminfrei
      Copper Contributor
      Jun 12, 2020

      virtualmanc It seems that the issue occurs on azure-joined machines only.  AD or WORKGROUP machines are not affected. I setup another tenant using AzureAD domain equal ADDS Domain. Same issues also when trying to connect on a machine connected to tenant A but using a Remote Desktop connection to tenant B! Can someone clarify this?

    • benjaminfrei's avatar
      benjaminfrei
      Copper Contributor
      Jun 12, 2020

      virtualmanc Strange thing! Tested on two other clients joined to a (separate) On-Premise AD (previous tests were all conducted on Azure-joined Clients). Same security features in place (Webfilter and Bitdefender AV) and it works! So must be kind of name resolution issue but I^m a little bit confused because according the flow diagrams name resolution also for the target VM (session host) is done azure internally?

Resources