Forum Discussion
Consistent Thin Client Disconnection from WVD Pool
Seems fine here as well. Just some troubleshooting steps I would take.
1) Establish what end-point you are going to: Ping rdweb.wvd.microsoft.com and see which IP address it is resolving to. I use this website to find out where that IP is located: https://www.iplocation.net/. DNS issues may make you bounce to a further away end-point. If you want to check other end-points I use this website: https://dnschecker.org/
2) Download and install Psping: https://docs.microsoft.com/en-us/sysinternals/downloads/psping
3) Run the following command. You can pipe out to a file for logging purposes: psping -t rdweb.wvd.microsoft.com:443
4) Run the following command as a baseline to see if you don't have local/internet issues: psping -t 8.8.8.8
When we had major issues in the West EU region you always saw spikes on the psping to the Rdweb and not to your baseline. Are you experiencing the same? Or do you have consistent low pings without spikes and are still seeing performance issues?
roneps07 In any gateway environment (WVD or RDS) all traffic from the client is passed to the Gateway (via port 443) and them from the gateway to the host. There is no direct connection between the client and host.
You never establish a direct connection to the WVD machine(s). Your connection remains tunneled through rdweb.wvd.microsoft.com. Unless if you manually open specific ports and bypass the WVD Gateway there is no direct path to your WVD machine(s).
Disconnections from RDS or WVD are notoriously difficult to troubleshoot. There are plenty of reasons for disconnections. I suggest running the tools I said earlier on computers that are experiencing the issues. Then just wait till it happens so you can pinpoint who or what's to blame. I really wish someone would write a small WVD Health tool that provides this data in an easy to install format. Now it's pretty labourintensive to troubleshoot. Something like: https://bramwolfs.com/2020/03/11/connection-experience-indicator-for-rds-wvd/ but then a tool that runs on the client side instead of within the session.
XxArkayxX thank you for the detailed steps.
The issue is quite random. It happens for a few seconds. I have not been able to observe the pattern yet. Most of the users use remote apps so they might not notice the disconnection. However handful of the users who use virtual desktop have reported this couple of times.
There is one doubt I would like to get clarified. Once the connection is created between the RD Client and the session host(WVD) machine, does the rdweb really come into the picture? I may be missing something.
