Aug 15 2019 06:02 AM - edited Aug 15 2019 06:17 AM
We have had WVD set up and working for a good bit now with no required interaction on our part. Yesterday, we started seeing with the thick client: "We couldn't connect because there are no available resources. Try again later or contact tech support for help if this keeps happening". The web browser shows: "Oops, We couldn't connect to the "hostpool. we couldn't connect to the gateway because of an error. If this keeps happening, ask you admin or tech support for help". This only happens if we try to connect from outside our corporate network. From inside our corporate network it works fine. I assume that from inside it is connecting through our vpn tunnel to azure. Hostpool and users accounts seem fine. Any ideas where to start?
Aug 15 2019 07:42 AM
Aug 15 2019 07:55 AM
I have had the same issue since yesterday at 4pm. But one distinction. I can reboot the WVD Virtual machine and the first person who signs in is fine but only from the original location. After that they cannot take over the session from any other device. I saw two updates and rolled them back but saw on another post from tuesday that there was a specific patch that caused the issue and even uninstalling it did not help. They had to re-register the host pool.
Aug 15 2019 08:16 AM
SolutionThere is a really good thread that explains it. Looks like the issue is with the Rd Infrastructure client update. The workaround from one gentleman was a start stop task every minute for the service. Go to the root of wvd and find the topic.
Aug 15 2019 09:22 AM
Thanks for the tips.. I didn't do anything but at least for the past 20-30 minutes everything has been working and I have been able to logon and off and on again over and over without any errors from the location I was having trouble with.
Aug 15 2019 09:24 AM
Aug 16 2019 06:49 AM
@richiewrt: It looks rather like a networking configuration issue. When where the outgoing traffic is blocked. Verify settings network configuration, firewall.... .
Aug 16 2019 06:56 AM
@Eva Seydl Wasn't a network issues. The workaround that @iconicmlee of restarting the RDAgentBootloader resolved it.
Aug 15 2019 08:16 AM
SolutionThere is a really good thread that explains it. Looks like the issue is with the Rd Infrastructure client update. The workaround from one gentleman was a start stop task every minute for the service. Go to the root of wvd and find the topic.