Forum Discussion

Sbarnet's avatar
Sbarnet
Copper Contributor
Dec 12, 2019
Solved

Consistent Thin Client Disconnection from WVD Pool

Hello we have been experiencing some random but consistent disconnects from our WVD Pool. We have roughly 10 users and have been getting different event viewer logs for when they disconnect. We have ...
  • evasse's avatar
    evasse
    Dec 20, 2019

    Sbarnet: Thank you for sharing the logs. Unfortunately there isn't enough information to debug the disconnects. I recommend to open a support case and provide activity IDs for the connections you see issues with. 

oiab_nl's avatar
oiab_nl
Copper Contributor
Mar 16, 2020

XxArkayxX 

 

I will try to open a ticket and link.

 

My biggest clients are logging in now from a site 2 site vpn, then its ok.

knowlite's avatar
knowlite
Iron Contributor
Mar 16, 2020

Just got complaints from our client aswel, working with 9 per VM and feedback is slow.
Thinking about migrating them back to our own datacenter environment where we can troubleshoot the whole infrastructure.

  • knowlite's avatar
    knowlite
    Iron Contributor
    Mar 16, 2020
    They are doing DNS LB so your rdweb endpoint isn't the same as mine,our results will differ.
    Your resolved IP address is different than mine, however the spikes are also there.

    Is there a way to resolve the RDGW that the user is using at the time of issues?
  • XxArkayxX's avatar
    XxArkayxX
    Brass Contributor
    Mar 16, 2020

    just got off the line with a MS Engineer. He did little more then run Psping:

    psping -t rdweb.wvd.microsoft.com:443

     

    You see a lot of spikes depending on which site you run it from it gets worse and worse but they all experience the spiking. Naturally you don't see such spikes to other internet infrastructure to exclude the possibility of a local issue.

     

    After seeing that he is escalating once more internally and will provide feedback.

     

    I suggest we all try running these continuously and keep comparing. This is a screenshot of the current "performance" although I do have to mention it's a whole lot better then this morning.