Sep 17 2020 03:20 AM
I am trying to troubleshoot some disconnect issues with a customer in the Western Europe region. I used the following query to list all the connections (it's not the ARM release of WVD):
UKS | 23 |
GWC | 21 |
FRC | 17 |
WEU | 16 |
UKW | 14 |
NEU | 6 |
Oct 06 2020 09:59 AM
Oct 07 2020 02:51 AM
Thank you for the reply! That would explain the results.
So my understanding of how the gateway is chosen does seem to be a bit off (I based this on a blog post about this topic somewhere).
I assumed that running an nslookup of rdgateway.wvd.microsoft.com would correctly show the gateway that would be used if I was to start a WVD session. For example at the moment is shows me:
Name: waws-prod-am2-f32c0796.cloudapp.net
Address: 51.136.28.200
Aliases: rdgateway.wvd.microsoft.com
rdgateway-prod-geo.trafficmanager.net
mrs-weur1c100-rdgateway-prod.wvd-ase-weur1c100-prod.p.azurewebsites.net
waws-prod-am2-f32c0796.sip.p.azurewebsites.windows.net
But running a capture with Wireshark does indeed show DNS entries such as afd-rdgateway-r1.wvd.microsoft.com which does imply that a Frontdoor service is at work.
Thanks again for the explanation.
Apr 27 2021 09:14 AM