This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
Troubleshooting
To confirm that HDX Direct successfully established a direct connection, you can use the CtxSession.exe
utility on the VDA machine.
To use the CtxSession.exe
utility, launch a Command Prompt or PowerShell within the session and run ctxsession.exe -v
. If the HDX Direct connection is successfully established, HDX Direct Status is Connected
.
You can also look at the session host’s event logs for information on whether the HDX Direct connection was established successfully or failed. See the Event Logs section for details.
Note:
Depending on the environment and the number of IP addresses available to the session hosts, it can take up to 5 minutes for the HDX Direct connection to be established.
When HDX Direct fails to establish a direct connection
If HDX Direct is failing to establish a direct connection, review the following steps:
- Ensure that the VDA version and Workspace app version in use support the feature per the system requirements.
- Confirm that you have a policy applied to the VDA that enables HDX Direct and that there are no other policies with higher priority disabling the feature.
- Confirm that you have a policy applied to the VDA that sets the desired HDX Direct mode and that there are no other policies with higher priority overwriting the configuration.
- Ensure that the Citrix ClxMtp Service is running on the session host.
- Ensure that the Citrix Certificate Manager Service is running on the session host. If it’s not running, try to start it manually. The service automatically stops if HDX Direct is disabled.
- Check if the session host has its self-signed Root CA certificate:
- Issued to:
CA-<hostname>
(For example, CA-FTLW11-001) - Issued by:
CA-<hostname>
(For example, CA-FTLW11-001) - Issuer details: The organization is Citrix Systems, Inc.
- Issued to:
- Check if the session host has its self-signed server certificate:
- Issued to:
<host FQDN>
(For example, FTLW11-001.ctxlab.net) - Issued by:
CA-<hostname>
(For example, CA-FTLW11-001) - Issuer details: The organization is Citrix Systems, Inc.
- Issued to:
- If the certificates are missing, contact Citrix Tech Support.
- If the certificates are present:
- Stop the Citrix Certificate Manager Service on the session host.
- Delete both the self-signed Root CA certificate and the self-signed server certificate.
- Start the Citrix Certificate Manager Service on the session host. The service creates new certificates once it starts.
- For internal users:
- Ensure the session host’s firewall is not blocking inbound traffic on UDP 443 or TCP 443, for HDX over EDT and HDX over TCP, respectively.
- Ensure that your network firewall is not blocking traffic on UDP 443 and TCP 443 between your clients’ network and session hosts’ network.
- For external users:
- Check the NAT type for the client and the session host, and ensure that the combination is expected to work. See the NAT Compatibility section for details.
- If the NAT test fails on either the client or the session host:
- If there is a firewall running on the system, ensure it is not blocking outbound traffic on UDP 3478.
- Ensure that your network firewalls are not blocking outbound traffic on UDP 3478.
- Ensure the firewalls are not blocking the STUN server’s response.
- Ensure that your network firewalls have the appropriate rules configured to allow all necessary traffic. See the Network Requirements section for details.
- If you change the default port range using the HDX Direct port range policy setting, ensure that your firewall rules are set for the custom port range.
Event logs
The following events are logged in the VDA machine’s event log:
Log | ID | Source | Level | Description |
---|---|---|---|---|
Applications and Services Logs > Citrix-HostCore-HDX Direct/Operational | 1 | HDX Direct | Information | HDX Direct connection for internal user <username> established. |
Applications and Services Logs > Citrix-HostCore-HDX Direct/Operational | 2 | HDX Direct | Information | HDX Direct connection for external user <username> established. |
Applications and Services Logs > Citrix-HostCore-HDX Direct/Operational | 3 | HDX Direct | Information | HDX Direct connection for user <username> failed. |
Known issues
HDX Direct might stop working after performing an in-place upgrade of the VDA on a machine that already has HDX Direct enabled. To resolve the issue, complete the following steps:
- Stop the Citrix Certificate Manager Service on the session host.
- Delete the self-signed Root CA certificate and the self-signed server certificate.
- Open the registry.
- Delete the
HKLM\Software\Citrix\HDX-Direct
key. - Go to
HKLM\SYSTEM\CurrentControlSet\Control\TerminalServer\Wds\icawd
. - Set the SSLEnabled value to
0
. - Delete the contents of the SSLThumbprint value.
- Start the Citrix Certificate Manager Service.
Share
Share
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.