This article describes troubleshooting performance issues with RDP file transfer through NetScaler Gateway.

Changes in performance and latency can be introduced by numerous causes. Each of the following points should be examined while troubleshooting this type of issue.

• The number of hops that has changed as a result of the traffic passing through the NetScaler Gateway. It is important to identify what each of these devices are and whether they can have an impact on performance.

• The license and model of NetScaler should be verified. The output of show license from the command line interface of NetScaler can be used to identify the license and the output of sysctl can be used to identify the hardware.

• The version of Receiver in use should be verified. Changes to Receiver can have a big impact on performance, particularly with the older versions.

• The encryption defined for use by NetScaler Gateway certificate/key pair should be verified. Higher encryption rates can dramatically reduce the performance.

• Within the NetScaler configuration, appropriate TCP Profile should be configured for use with XenApp and XenDesktop traffic. This can be defined globally or within the gateway service configuration, if multiple gateways are configured. An existing gateway service can be modified using:
  set add vpn vserver aaa.bbb.ccc SSL 192.168.0.10 443 -tcpProfileName nstcp_default_XA_XD

  Note: The aaa.bbb.ccc and IP address should be modified to match the name and IP address of the defined NetScaler Gateway service respectively.

• If the preceding troubleshooting steps does not improve performance, then trace data should be collected simultaneously from the client, NetScaler Gateway and server, when completing the transfers. This trace data must be reviewed together, to identify issues with the traffic at the TCP level.