Connection Problems
If you are having difficulty connecting to an X client or an XDMCP desktop, review the following tips:
-
If you are trying to connect to an X client and see "Client failed to connect to the X server" in the Status bar, the specified Command may not be valid on your host. Try changing the Host type and use the command drop-down list to test with a different sample command. For additional information, click the Information icon
to open the Start Client log. Review the log for terminal and X Manager activity messages. -
You may need to configure your firewall for the ports being used by Reflection X. See Ports used by Reflection X for a summary of these ports.
-
If you are connecting through a VPN and are having problems using XDMCP to connect to a session, you may be able to resolve the problem by using a distributed session. With this configuration, the client connector that originates the XDMCP request runs on the X application host and the request does not have to travel through the VPN router. (VPN routers typically block XDMCP connection requests.) If you're using X Manager, see How to Configure a Distributed Session in Standalone Mode. If you're using X Manager for Domains, see Domain Setup to Improve Performance Over a Slow Network.
-
If your host name resolves to an IPv6 address, try specifying an IPv4 address for the host instead of using the host name.
-
If you are having trouble establishing an XDMCP connection, try starting a desktop session without using XDMCP.
-
If you have configured X Manager to use remote session services, the connection to the remote Linux host uses PAM authentication. On some Linux systems, the pam_securetty module is configured by default to allow root logins only if the user is logging in on a secure tty. On these systems you cannot log on using root credentials.
More information