NoMachine NX - Support: Trouble Report

Added on:

2007-05-04

Last Modified:

2007-05-07

Product:

NX Core

Affecting:

3.1.0

Platform:

All Platforms

Severity:

Minor

Status:

Open

Target:

3.5.0

Opened by:

Raffaele Toriaco

Technical Responsible:

Gian Filippo Pinzari

Concurrent NX sessions on a client machine may fail to start under particular conditions

When the NX session starts, the proxy may open one or more TCP ports to listen or forward NX services connections. The port numbers are calculated adding to a fixed offset the X display number, as explained in the following document:

http://www.nomachine.com/documentation/admin-guide.php

If, for example either NX Server A and NX Server B are a fresh installation, and provided with the default configuration, they will both assign the same display number to the first session running there.

In this case, if the user runs contemporary a session on server A and on server B from the same NX Client machine, it can happen that the same X display is
assigned to both sessions and the second session fails to start with an error like:

Error: Call to bind failed for font TCP port 11000. Error is 112 'Address already in use'.

Since NX Server increments the display number on each new connection, a new attempt should solve the issue. Furthermore, a way to prevent the issue, could be ensuring that multiple servers have a different offset for the X display number by properly setting the server configuration.

Notes

	Concurrent NX sessions on a client machine may fail to start under particular conditions
Nothing available.

Provided Solution

Concurrent NX sessions on a client machine may fail to start under particular conditions

Under evaluation.