XDMCP Session Properties

The following are descriptions of connection-related items in the XDMCP Session Properties. The items are displayed in the [General] tab of the XDMCP Session Properties dialog box.

Method
The session connection methods are None (Passive), XDMCP Query, XDMCP Broadcast, XDMCP Indirect, and Secure XDMCP.
For descriptions of each connection method, see 'Static XDMCP Session'.

Host
Enter the remote host name or IP address for connection.
Check if a display manager is in operation in the remote host. Most UNIX/Linux distros use dtlogin, kdm, gdm, lightdm, or xdm as the display manager.

Port Number
Enter remote display manager port number. The default value is UDP 177.

Use Default
Set port number as the UDP 177 default value.

Connection Address
This option is necessary when users connect using port forwarding in a limited network environment such as a firewall or proxy server and when automatic connection address does not function properly due to XDM server settings even if Secure XDMCP connection is selected. When the user's Windows resides in a private network with a firewall, Xmanager cannot get a remote login window with an XDMCP connection since the firewall blocks incoming connections. Thus, the remote display manager will not be able to reach Xmanager on the user's Windows PC. To use this feature, users need to allocate a listening port in the firewall and forward incoming connections to your Windows.

Address Type
Select User Defined when using a proxy server or attempting XDMCP connection in an environment blocked by a firewall. When using Secure XDMCP, if Automatic of connection address fails, select IP address of SSH server or Loopback Address (127.0.0.1).

IP Address
If [Address Type] is selected as User Defined, enter proxy server or firewall server IP address. The remote display manager attempts the connection using this address and the proxy server forwards the connection to the user's system.

Port Number
If [Address Type] is selected as User Defined, designate a TCP port number allocated to a proxy server and standing by for port forwarding.
For example, let's assume that a user's computer uses 192.168.1.100, a private IP address, and the firewall server uses 192.168.1.1, a private IP address. Additionally, the firewall uses 210.100.xxx.10, a public IP address, for an external Internet connection, and the UNIX host IP address is 210.100.xxx.100.
In this case, you need to configure the firewall to forward incoming connections (210.100.xxx.10, port number 6010) to Xmanager (192.168.1.100, port number 6010) on your Windows. This is called port forwarding. For this setting, make an inquiry to the firewall system administrator.
Now, enter 210.100.xxx.100 in the [Host] box of [Connection] field, and select User Defined as [Address Type] in [Connection Address]. Then, enter 210.100.xxx.10 in [IP Address] and enter 6010 in [Port Number]. Click [X Server] tab, clear [Allocate display number automatically] option and enter 10 (TCP 6010) in [Display Number].
The [Connection Address] setting process when connecting with an external host through a router is described in 'Firewall-related Setting'.