This message was deleted.

Unless the network is shite, EDT has been pretty awesome

This was a bit of challenge for me in the past. I ended up Following this. I had to understand packet fragmentation. https://support.citrix.com/article/CTX231821/how-to-configure-mss-when-using-edt-on-networks-with-nonstandard-mtu

yeah, i've had some major challenges with it as well. Had some success with the above, and setting the MTU in the default ICA file.. However, with all the CVEs and shit that's happened with EDT over the past 2 years, i just turned it off across the board. 1. Edit "C:\inetpub\wwwroot\Citrix\<STORENAME>\App_Data\default.ica" in notepad and add the following entries under [Application] a. OutBufLength=1350 b. udtMSS=1350

@Ryan Gallier is this still applicable if your netscalers are on Azure?

"This is common when using VPN solutions like Cisco AnyConnect, when using Citrix Gateway hosted on Azure" Doc says this is that helps?

This used to be a requirement for azure specifically. I bet it's still true.

In germany, I have to disable it. Unusable. Only TCP works reliable (or I’m doing something wrong).

Thanks @Ryan Gallier. the more i think about it, it seems that @James Kindon may have mentioned this is no longer needed. do you have a link for that info?

it's in the link above

If we don't define mtu/mss, do we know what it defaults to using?

I would assume 1500

Isn’t the discovery all dynamic now @Oz Zy - I havent been setting those mtu values in azure for a while now

ping mygateway.onazure.com -f -l 1500 Pinging mygateway.onazure.com [10.22.X.X] with 1500 bytes of data: Packet needs to be fragmented but DF set. Packet needs to be fragmented but DF set. Packet needs to be fragmented but DF set. Packet needs to be fragmented but DF set. ping mygateway.onazure.com -f -l 1450 Pinging mygateway.onazure.com [10.22.X.X] with 1450 bytes of data: Reply from 10.22.0.8: bytes=1450 time=34ms TTL=250 Reply from 10.22.0.8: bytes=1450 time=34ms TTL=250 Reply from 10.22.0.8: bytes=1450 time=35ms TTL=250 Reply from 10.22.0.8: bytes=1450 time=35ms TTL=250

discovery all dynamic ASSUMING endpoints support that as well. So VDA has supported dynamic MTU now for a bit with Windows first then others coming after. The hard coded MTU would only be needed if needing to set it for CWAs that ignored the MTU discovery.

I can't speak on the Azure part, But on the other stuff, I would do this in the past. Which is what @Matt Nation Just did. Example of not have the key and using default MTU setting which is 1500.

• Citrix Workspace app ◦ Windows: version 1912 or later (2105 or later recommended) ◦ Mac: version 2108 or later ◦ Linux: version 2109 or later ◦ Android: version 21.5 or later

The article that @Ray Davis posted it a great guide. Overtime and with a lot of user feedback, I've had to go as low as 1338 to have reliability from any ISP/4G network connected device from anywhere within Australia. I found the further away the 4G tower was from a City, the lower the value had to be to make it reliable.

@Jeremy Saunders when did they start building cities over your side of this country? 😬

It seems i am not alone on this topic 🙂