In the General tab, you can set XDMCP and connection address settings of a session.

Xbrowser Properties Dialog Box, General Tab

Connection Method

Select one of the connection methods: Passive (No XDMCP), XDMCP Query, XDMCP Broadcast, XDMCP Indirect, and Secure XDMCP.

Passive method just executes Xmanager in background mode. By default, Xmanager enters into the system tray and waits for X applications to connect. It is useful when you want to run Xmanager ahead of time and open X applications using Xstart or a telnet client.

XDMCP Query is a default method for dynamic sessions. It connects to the specified host directly and brings a graphic login window to your Windows.

XDMCP Broadcast is a method that Xmanager opens a Broadcast Chooser dialog box which looks like a simple Xbrowser.

XDMCP Indirect is a similar method to XDMCP Broadcast except that the chooser dialog box is displayed by the remote host, not by Xmanager.

Secure XDMCP is useful when Xmanager cannot establish XDMCP connection because of private network with firewall. If SSH server is running on the remote server, you can make XDMCP connection to the remote host using SSH tunneling.


Enter the IP address or hostname of the remote host you want to connect to. Make sure that a display manager is running on the remote host. Most Unix machines are using one of dtlogin, kdm, gdm, and xdm as the display manager.

Port Number

Enter the port number of the remote display manager. The default value is UDP port 177.

Use Default

Sets the port number to UDP port 177.

Local Address

Select one of the IP addresses of your Windows. This option is used only your Windows has multiple IP addresses.

If you select Auto Select in the list, Xmanager tries to find an appropriate IP address for the connection. When Xmanager fails to find an appropriate one, it displays an IP Selector dialog box in which you can select a correct one.

The display manager on the remote host will connect to the IP address you have selected. If you choose an inappropriate IP address, the display manager cannot get access to Xmanager and fails to open a login window.

Connection address

This option is required when you connect using port forwarding in a limited network environment such as firewall or proxy server, and when Secure XDMCP is selected and automatic connection address feature malfunctions due to XDM server settings, etc.

When your Windows resides in a private network with a firewall, Xmanager cannot get a remote login window with an XDMCP connection. It is because that the firewall blocks incoming connections and the remote display manager cannot reach at Xmanager on your Windows.

To use this feature, you need to allocate a listening port in the firewall and forward incoming connections to your Windows.

As an example, let us assume that your Windows has a private IP address, and the firewall has a private IP address, The firewall server has also a public IP address, for Internet connections and the IP address of a remote Unix host is

In this case, you need to configure the firewall to forward incoming connections (, 6010) to Xmanager (, 6010) on your Windows. This is called port forwarding and you should contact your administrator to configure it.

Now, enter in the Host box of the Connection area, select User Defined as Address Type in Connection Address area, enter in the Host box of the IP Address area, and then enter 6010 in the Port Number box. Click the X Server tab, turn off the Allocate display number automatically option, and then enter 10 (It means the TCP port 6010) in the Display Number box.