![]() ![]() The default is that MTU of 1500 bytes are sent, if the MTU on the path is somewhere smaller the package gets fragmented, what is not a big issue but in real life we see that it can be a problem. Standard, MTU set to 1500 Default configuration, MTU to 1500 You can read more about MTU discovery here: MTU discovery is not a invention by Citrix, just new on EDT. This feature gives the possibility to have the best MTU for each session. The benefit of this solution that it works on every platform with the exception of Android.Īn even smarter option Citrix introduces on the background with CVAD 19.12, this is MTU Discovery for EDT. The disadvantage of this solution is that the MTU is lowered for all connections, also it’s needed to figure out which MTU fits best. In this article, you can see how to configure EDT for non-standard MTUs e.g. ![]() In the recent blog article, I called Citrix “please fix that” but they already started on this at this point. Solution 1: How to configure MSS when using EDT on networks with non-standard MTU It looks like EDT is much more sensible on that than the classic ICA protocol on TCP. So there will be a fragmentation of the packages, in some cases the fragmentation causes problems because the payload is no more enough that a session launch will work. I found out that our branch offices has a smaller MTU than 1500 what is the default, the reason is a crypto-tunnel which is configured to all our branches. (see the recent blog article)įurther analysis of this issue showed that the root cause of this issue is on the MTU, which means the Maximum Transmission Unit or simplified said Package size. But this is not really our intended solution because all the benefits of EDT get lost, so we just did it on client-side with a reg hack, but so we have to identify all the clients with issues. Our first workaround for this issue was to disable the UDP based EDT protocol which is now the default for Citrix Virtual Apps and Desktops. I wrote a blog article some weeks ago: Issues by accessing Citrix Virtual Apps and Desktops on a pure IPv6 Internet Provider with enabled EDT Desktops were connected from private devices over a Citrix ADC (aka Netscaler) but virtual apps were connected from our internal network from different branch offices. Recently I saw an increased number of issues by connecting to Citrix virtual desktops and apps. Only update the default.ica how it’s described below, referencing to if you also are using Citrix Workspace App for Mac in Version 2201 or later! If you set this flag the issue should be solved: The solution was to switch off EDT on the client side or to change the MTU discovery to a static MTU (edtMSS=13xx). Fact is, on certain cable connections with DS-Lite (IPv6 only) the MTU discovery with EDT did not work properly, because the cable modem did not process the “DF flag”, which caused the MTU discovery to detect a too high MTU, the datagrams had to be fragmented and the performance was bad. Martin Latteier wrote me that Citrix introduces a new feature which addresses the issue.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |