Forum Discussion
not able to connect to WVD from win64 client (latest)
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/
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??
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)
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
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?
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?