Forum Discussion

fdwl's avatar
fdwl
Former Employee
Apr 13, 2022

Announcing public preview of Azure Virtual Desktop RDP Shortpath for public networks

Today I have the pleasure of announcing the public preview of RDP Shortpath for public networks. This Remote Desktop Protocol (RDP) feature establishes a direct UDP data flow between the Remote Deskt...
pcluskey's avatar
pcluskey
Brass Contributor
Apr 19, 2022

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!

dextraa9791's avatar
dextraa9791
Copper Contributor
Apr 19, 2022

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 Shortpath

 

Anyone else running into this?

  • MawandaH's avatar
    MawandaH
    Brass Contributor
    Jul 27, 2022

    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.

    • Kyle_Wise's avatar
      Kyle_Wise
      Copper Contributor
      Jul 27, 2022
      MawandaH Im assuming you dont have a firewall in your environment. ShortPath Public Network doesn’t work with most.
  • Dennis_Schierenbeck's avatar
    Dennis_Schierenbeck
    Copper Contributor
    Jun 13, 2022

    dextraa9791 

    I'm seeing the same error message.

    Could anyone here find out the reason?

  • Nigel's avatar
    Nigel
    Iron Contributor
    Apr 25, 2022
    Yup 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
    • pcluskey's avatar
      pcluskey
      Brass Contributor
      Apr 26, 2022
      We 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.
  • Nigel's avatar
    Nigel
    Iron Contributor
    Apr 22, 2022
    This is exactly the error we are seeing and we have opened all firewall etc.
  • fmartel's avatar
    fmartel
    Brass Contributor
    Apr 19, 2022
    I also have the same error. This script seems to verify if your VM have a public IP or a NAT that is used for UDP binding. Seems like that the NAT preservation is a pre-requesite or one of the multiple ways that the agent try to connect in UDP. It would be nice if we would have a verbose log to know where the problem came from. As far as I understand without NAT translation or port preservation or UPnP it will not work. (Didn't manage to get it work)

Resources