Forum Discussion

benjaminfrei's avatar
benjaminfrei
Copper Contributor
Jun 11, 2020

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 without issues. Installed Client version 1.2.1026.0 using URL https://rdweb.wvd.microsoft.com/api/arm/feeddiscovery.

Login is accepted and Workspace is visible. But when I try to connect to a published SessionDesktop the connection fails with a generic "Remote Desktop can't connect to the remote computer for one of these reasons..." (Error code 0x204).

I have and showcase tomorrow with the customer - any hints? Thanks!

  • virtualmanc's avatar
    virtualmanc
    Iron Contributor

    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

      virtualmanc Good morning! I tested the connection on three different devices and also disabled security modules like webfilter. all of them have managed bitdefender installer. I will do another test with disabled/uninstalled bitdefender and let you know. So my interpretation is correct that no pinholes on the azure side is required because all the traffic flows between the client - the azure frontdoor and then internally to the vm's via 443/tcp?

    • benjaminfrei's avatar
      benjaminfrei
      Copper Contributor

      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

        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

Resources