Menu
Attempts to sign in to Citrix Workspace App for Mac 2006 might fail, displaying an unrelated UI with 'SET AT RUNTIME DO NOT LOCALIZE'. We are planning to include a fix in an upcoming release of Workspace App for Mac. As a workaround, click 'Refresh Apps' on the menu on the top right of the application to load the store.
Applicable Products
Symptoms or ErrorWhen using a third party VPN solution like Cisco AnyConnect, or when using Citrix Gateway hosted on Azure, the EDT connection might fail, falling back to TCP or even failing to establish a session.Environment: Citrix Workspace Mac App StoreXenApp / XenDesktop 7.13 - 7.18 or Citrix Virtual Apps and Desktops 1808+ EDT-capable Citrix Receiver / Workspace app:
Note: If the VPN uses TCP to encapsulate EDT, then EDT's congestion control will be affected by TCP's congestion control. While some performance improvements are still expected, Citrix has not quantified them. SolutionIf there is a modification to the MTU on the VPN, then EDT connections might fail and fall back to TCP. This is a limitation of the VPN which is not handling IP fragmentation properly.The workaround involves lowering the ICA/EDT MSS to a known value that will not cause fragmentation. This MTU value needs to be determined by the customer, for example by using a tool like mturoute.exe. Citrix Workspace App 1808 For Mac PcIn the case of Azure-hosted NetScaler VPX, Azure limits MTU to 1400 on the Azure Gateway. Therefore the EDT MSS and Output Buffers Length must be set to 1350.Steps 1. Define the EDT MSS and Output Buffers Length in the ICA file template in the Storefront server:
Open the default.ica file for editing (by default it is located in C:inetpubwwwrootCitrix<StoreName>App_Datadefault.ica) Add the following options under the [Application] section: OutBufLength=1480 udtMSS=1480 (add this line if using Receiver for Windows 4.7 - 4.12, Receiver for Mac 12.5 - 12.9, Receiver for Linux 13.6 - 13.10, Receiver for iOS 7.2 - 7.5.x, Receiver for Android 3.12.3 - 3.13.x, or Workspace app 1808 for Mac, Linux, iOS, or Android) edtMSS=1480 (add this line if using Workspace app for Windows 1808+) Note: 1480 was used as an example. Replace the value with the appropriate value determined by the customer, or with 1350 if using an Azure-hosted Citrix Gateway or if your VDAs are hosted in Azure and need to traverse Azure Gateway (e.g. VPN connection). The client and server will agree on sizes during the connection negotiation. 2. Enable Receiver/Workspace app to read the custom EDT MSS and Output Buffers Length values. NOTE ![]()
Create UDPStackParameters registry key, which is missing by default:
HKCUSOFTWARECitrixICA ClientEngineConfigurationAdvancedModulesUDPUDPStackParameters If using Receiver for Windows 4.7 / 4.8 / 4.9 / 4.9 CU1 / 4.9 CU2 / 4.9 CU3: There is a legacy issue in these Receivers for Windows where OutbufLength, when passed in an ICA file, is ignored. Even if the registry value is modified to '*', meaning accept everything from the ICA file, the ICA file setting is still ignored. For this to work, in addition to creating the 'UDPStackParameters' key as mentioned above, it is also necessary to modify the OutbufLength value in the registry and set it to the desired value determined above (1480 in the example):
HKLMSOFTWAREWow6432NodeCitrixICA ClientEngineConfigurationAdvancedModulesTCP/IPOutbufLength
HKLMSOFTWARE CitrixICA ClientEngineConfigurationAdvancedModulesTCP/IPOutbufLength
Modify the appropriate App Property to allow Receiver to read the customer parameters in the ICA file. This property is set to NO by default.
To do this, open Terminal and run: defaults write com.citrix.receiver.nomas UDPStackParameters -bool YES
Toggle the the 'Read EDT stack parameter' option, which is disabled by default:
Settings > Advanced > Adaptive Transport Settings > Read EDT stack parameter
Enable the the 'EDT stack parameter' option, which is disabled by default:
Once you have selected a Store in Receiver/Workspace app, open the hamburger menu and select Settings > Advanced > EDT stack parameters Problem Cause
MTU alteration not accounted dynamically by EDT, and IP Fragmentation not handled properly by the VPN solution.
Additional ResourcesComments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
November 2020
Categories |