Forum Discussion
Windows Virtual Desktop is generally available!
- Oct 01, 2019
soloji Did you check with the new user experience estimator we have? Is it really giving you that high a latency? I'm getting 240ms for RT from WUS to Australia Central 2 (which is not the best but definitely better than 540).
https://azure.microsoft.com/en-us/services/virtual-desktop/assessment/
By end of 2019, we will have service instance in Japan and that should considerably reduce your RT to double digits.
soloji Did you check with the new user experience estimator we have? Is it really giving you that high a latency? I'm getting 240ms for RT from WUS to Australia Central 2 (which is not the best but definitely better than 540).
https://azure.microsoft.com/en-us/services/virtual-desktop/assessment/
By end of 2019, we will have service instance in Japan and that should considerably reduce your RT to double digits.
- Paul MaranzanoOct 02, 2019Copper Contributor
I'm a little confused. So my VM is in Australia East but my rdgateway is routing through the US.
tracert rdgateway-r1.wvd.microsoft.com
Tracing route to waws-prod-bn1-043.cloudapp.net [104.209.178.67]
What RDGateway should Australian's be routing through? Is there a list of gateways?
How accurate is the WVD Experience Estimator? It's telling me best experience is in East US 2 with 206ms but Australia East is 446ms
- solojiOct 02, 2019Copper Contributor
I am also interested in this answer but I think from above there are no rd gateway servers in Australia with Japan to be next (hopefully not final) region that will be closer than US
- Paul MaranzanoOct 02, 2019Copper Contributor
Hopefully, it's quite unusable. I might start deploying but get clients to use the traditional RDP client over secure connection.
- solojiOct 01, 2019Copper Contributor
Great news about Japan 🙂
I actually got my results from the experience calculator interestingly I have found that depending on DNS server that you use will change the response of returned location for rdgateway.wvd.microsoft.com.
I expect that this what is influencing my strange results.
So as pictured if you use google DNS 8.8.8.8 it returns an address in the Netherlands (using kloth.net)
DNS server handling your query: 8.8.8.8 DNS server's address: 8.8.8.8#53 Non-authoritative answer: rdgateway.wvd.microsoft.com canonical name = rdgateway-prod-geo.trafficmanager.net. rdgateway-prod-geo.trafficmanager.net canonical name = mrs-weur1c001-rdgateway-prod.azurewebsites.net. mrs-weur1c001-rdgateway-prod.azurewebsites.net canonical name = waws-prod-am2-135.sip.azurewebsites.windows.net. waws-prod-am2-135.sip.azurewebsites.windows.net canonical name = waws-prod-am2-135.cloudapp.net. Name: waws-prod-am2-135.cloudapp.net Address: 52.233.128.61
Geolocation data from https://www.iplocation.net/go/ip2location (Product: DB6, updated on 2019-9-1)
IP Address Country Region CityISP Organization Latitude Longitude
52.233.128.61 Netherlands Noord-Holland Amsterdam Microsoft Corporation Not Available 52.3740 4.8897 But if you use cloudflare DNS 1.1.1.1 it returns an address in the Eastern United States (using kloth.net)
DNS server handling your query: 1.1.1.1 DNS server's address: 1.1.1.1#53 Non-authoritative answer: rdgateway.wvd.microsoft.com canonical name = rdgateway-prod-geo.trafficmanager.net. rdgateway-prod-geo.trafficmanager.net canonical name = mrs-eus2r0c002-rdgateway-prod.azurewebsites.net. mrs-eus2r0c002-rdgateway-prod.azurewebsites.net canonical name = waws-prod-bn1-039.sip.azurewebsites.windows.net. waws-prod-bn1-039.sip.azurewebsites.windows.net canonical name = waws-prod-bn1-039.cloudapp.net. Name: waws-prod-bn1-039.cloudapp.net Address: 137.116.78.243
Geolocation data from https://www.iplocation.net/go/ip2location (Product: DB6, updated on 2019-9-1)
IP Address Country Region CityISP Organization Latitude Longitude
137.116.78.243 United States Virginia Boydton Microsoft Corporation Not Available 36.6676 -78.3875