Forum Discussion
Announcing public preview of Azure Virtual Desktop RDP Shortpath for public networks
Also would using the AzureVirtualDesktop service tag on a custom UDR (to send that straight out of the session host and bypass NVA inspection) help? I've tried and it doesnt appear to.
Any additional logs other than the Log Analytics ones.?
thanks
update: it seems like this has now just started to work - even though I've made no additional host or network changes, so maybe a backend change. Either way its looking good!
- pcluskeyApr 20, 2022Brass Contributorwell I spoke too soon. no changes on our side, client on the same network as yesterday now using TCP again. I can't get it to work on my home broadband (Virgin) unless I disable UDR to our NVA (so can't do that in production). I'm wondering if my home mesh TPlink Deco is causing problems.
- dextraa9791Apr 19, 2022Copper Contributor
pcluskey
We started testing this feature today and also getting the same error.Failed to communicate [2a01:111:202f::155]:3478 with error: Unable to send data, check if InterNetworkV6 is configured
Local NAT does not use port preservation, custom port range may not work with ShortpathAnyone else running into this?
- MawandaHJul 27, 2022Brass Contributor
dextraa9791I just enabled shortpath using the guide "https://3tallah.com/improve-your-end-user-experience-with-rdp-shortpath-for-avd/?unapproved=101&moderation-hash=4c1fa124dd396ca4c6c9ff4904c54e87#comment-101" before following these steps I struggled to get this working.
- Dennis_SchierenbeckJun 13, 2022Copper Contributor
- NigelApr 25, 2022Iron ContributorYup same error - unsure what to do next - our network team has confirmed we are allowing UDP, and can see it making outbounds to STUN. Still no UDP sessions
- pcluskeyApr 26, 2022Brass ContributorWe have the same, and whilst outbound to the STUN servers is visible, I believe there also needs to be an outbound connection to the clients public IP. If I remove my UDRs then I see that communication, but with the UDR to our NVAs it's not happening. I suspect partly its because our NVA doesn't support STUN, and also down to lack of NAT for UDP traffic outbound. I've raised a support ticket (even though its in preview) - hopefully MS can have a look at my matching wireshark traces and advise.