6/26/2023 0 Comments Nomachine 4In case of multinode environments, the UDP port must be open on each of the remote nodes. This port must be open between client and the remote host where the session will be run. Previous versions were using a range of ports between 40. Since v8 UDP communication for multimedia uses by default port 4000. This means that the other data traffic is still sent via TCP. Only multimedia communication however can be routed through UDP, when enabled. When UDP is enabled, data can travel on TCP and UDP streams at the same time. This port must be open between client and server: this is mandatory to allow connections by NX protocol.Ĭonnections by NX protocol can use UDP communication for multimedia data. The Network Server (nxd) listens by default on port 4000. Ii) or the server configuration file (the NoMachine_installation_dir/etc/server.cfg file). I) via the User Interface (Server preferences -> Network services -> Edit) NoMachine services ( the NoMachine Network Service nxd to accept connections by NX protocol, the SSH server nxsshd on Windows and the HTTP Server nxhtd) are configured to listen on default ports. On the client side, for each session NoMachine uses a port defined by 12000 + display for activities (locally) and a port defined by 10000 + display for the font channel. This is a service that operates only on a LAN.īroadcasting of the server information can be disabled from the NoMachine User Interface in 'Server preferences' ( 'Don't advertise the computer on the network'). The MDNS service (available since version 4.1 and used to publish the computer presence over the LAN) uses the UDP port 5353. This will apply to all new virtual desktops without the need to restart the NoMachine server. To do that, edit the /usr/NX/etc/node.cfg file and set:ĭisplayServerExtraOptions "-nolisten tcp" It's possible to disable listening on all TCP ports and force the display service to listen only on unix sockets. The NoMachine display service for virtual desktops listens instead on all interfaces. The NoMachine display service for connecting users to the physical display listens on the loopback interface. This port (7001 for example) is used to receive connections from X clients (according to X.org implementation). This applies to both the display service started to allow connections to the physical desktop (when an X server is available) and to the display service started for each new virtual desktop. If this port is already in use, NoMachine will look for a free port by incrementing DisplayBase up to the value set in the DisplayLimit server configuration key. This means that NoMachine will try to start the display service on port 1001 + 6000 = 7001 firstly. The NoMachine display service (embedded in the nxnode program) uses a TCP port which number is defined by the value set in the DisplayBase server configuration key + 6000. If the virtual desktop/custom session is reconnected or the user connects to that session is shadow mode, the new nxnode process uses this port to communicate with the nxnode process of the original session.Į) NoMachine also runs a session monitor listening on a port defined by 24000 + display. When a session is started, the nxnode process listens on it. This port is used locally.ĭ) NoMachine uses a local port defined by 25000 + display. NOTE: This setting will be applied only to new sessions.Ĭ) The server daemon process (nxserver -daemon ) uses a random port selected in the range between value set for ServerSlaveBase Just add the ServerSlaveBase key at the end of the server.cfg file, e.g.: Number of this port starts from 20000 and it's incremented by one when a new session is created.Ī hidden key in the server configuration file allows to define a different base value for this port. This port is used locally.ī) A port, used locally, to let the nxserver process started for the session communicate with the principal nxserver service. So the port used by the first connection will be 11000 + 1001 = 12001. Display is the value set in the DisplayBase server configuration key, by default 1001. PAM).įor each new session (regardless of whether it's a connection to the physical desktop or a new virtual desktop or custom session on Linux), NoMachine needs:Ī) A port defined by 11000 + display. All communications through ports listening on external interfaces are encrypted and require the user to be authenticated against the authentication sub-system of that host (e.g. Ports must be open on the firewall or router when they are necessary for data communication between client and server or client and node in case of multi-node environments. Ports used locally must be free to let the session start but don't need any change in the router or firewall configuration to allow access from outside. For each session, NoMachine uses a number of i) ports that are used only locally on server or client side and ii) TCP ports.
0 Comments
Leave a Reply. |