reza

[reza]

Hi,

Did you looked at https://www.nomachine.com/AR02L00785 already?

Regards

[reza]

If you want to take control over FW settings please disable automatic FW configuration by changing that key in server.cfg:

# Enable the server to automatically configure the firewall for all

# the configured services. On platforms that don’t support adding

# the specific executables to a white list, the needed ports are

# added at server startup and removed at server shutdown, or when,

# at run-time, a new port is needed. The default value is 1.

#

# 1: Enabled. NoMachine opens the required ports in the firewall.

#

# 0: Disabled. Firewall must be configured manually. By default

#    the required ports are TCP ports 4000 for NX, 4080 and 4443

#    for HTTP and UDP ports in the range 4011-4999 range.

#

#EnableFirewallConfiguration 1

[reza]

Hi, please check if firewall or anti-virus software doesn’t block external connections on your Mac client machine.

[reza]

Your physical display may be not resizable becouse it’s headless.

If you turn off lightdm / X server a NoMachine will start one on it’s own, fully resizable.

[reza]

Run the following command to update NoMachine audio support:
/usr/NX/bin/nxnode –audiosetup [<path>]
where <path> is an optional argument to specify the absolute path to PulseAudio configuration files (e.g. client.conf, daemon.conf, …) in a non standard location. For more information about this command please run /usr/NX/bin/nxnode –help.

[reza]

Please check if you have Artsd daemon installed and running.

[reza]

We found some unusual behaviour in logs you sent.

Can you tell us more about your Windows 10 edition and language variant?

We will try to reproduce a problem in our lab.

[reza]

We found that you are trying to connect to local port 7025 with help of SSH protocol and that connection fail.

Port 7025 is not a default SSH port so please assure that you have a SSH daemon listening there on your local host (directly or via port forwarding or tunnelling).

[reza]

Reconnection should take around 2 seconds but multiple factors can affect it.

Please send to us a logs from client and server and we will try to find a bottleneck.

[reza]

Connection time depends on multiple factors, quality of WiFi, server and client hardware etc.

4/5 seconds is fine on weaker WiFI networks.

[reza]

Ten seconds delay can be provoked by SSH server reverse DNS lookup procedure.

It can be disabled by setting ‚UseDNS’ key to ‚no’ in sshd_config on your server.

[reza]

Please assure that ports used by NoMachine are not blocked by firewall.

By default these ports are:

4000 in case of NX protocol

22 in case of SSH protocol and NoMachine server installed on Linux or Mac

4022 in case of SSH protocol and NoMachine server installed on Windows

[reza]

Looks like you have installed 32 bit NoMachine package on 64 bit system.

Please remove 32 bit version and install correct, 64 bit package or install 32 bit compatibility library.

 

[reza]

We found that key you are trying to do contains obsolete options, no longer used in NX 4 and 5.

Please don’t add ‚no-port-forwarding,no-agent-forwarding,command=”/usr/NX/bin/nxnode”’ to key you are trying to use for SSH System authorisation.

Additionally SSHD fails to decode your key.

Please generate new one, add it to your .ssh/authorized_keys2 and use in player as explained in following article:

https://www.nomachine.com/AR12I00615

[reza]

In System login case it looks like the key you are trying to use is not added into .ssh/authorized_keys2 file in your home directory on server.

NoMachine login case is more complicated and we need nxserver.log and nxerror.log files from your server to analyse the problem.

[Author]

Posts