Client: connection timed out, server: Can’t bind the IPv6 socket

[Romz]

Hi,

The Windows 10 client shows an error 138 “connection timed out”.

I checked the server logs and saw this:

$ sudo tail -f /usr/NX/var/log/nxerror.log

Info: Handler started with pid 27780 on Sun Jan  1 23:19:51 2017.

Info: Handling connection from 192.168.0.6 port 60691 on Sun Jan  1 23:19:51 2017.

27780 27780 23:20:26 283.326 Socket: WARNING! Can’t bind the IPv6 socket.

27780 27780 23:20:26 283.380 Socket: WARNING! Error is 99 ‘Cannot assign requested address’.

nxexecRestoreSavedResourceLimits: Info: Can not open resource limits file.

nxexecRestoreSavedResourceLimits: No such file or directory.

nxexecExecNode: Info: Cant not restore saved resource limits.

nxexecRestoreSavedResourceLimits: Info: Can not open resource limits file.

nxexecRestoreSavedResourceLimits: No such file or directory.

nxexecExecNode: Info: Cant not restore saved resource limits.

nxexecRestoreSavedResourceLimits: Info: Can not open resource limits file.

nxexecRestoreSavedResourceLimits: No such file or directory.

nxexecExecNode: Info: Cant not restore saved resource limits.

Usage: nxnode …

this command is intended to be used only by NX Server

or NX Workstation.

27890 27890 23:20:32 183.484 Socket: WARNING! Can’t bind the IPv6 socket.

27890 27890 23:20:32 183.744 Socket: WARNING! Error is 99 ‘Cannot assign requested address’.

Info: Connection from 192.168.0.6 port 60691 closed on Sun Jan  1 23:20:32 2017.

Info: Handler with pid 27780 terminated on Sun Jan  1 23:20:32 2017.

Server version: 5.1.62, Ubuntu 16.04 amd64. IPv6 disabled in Network Manager.

Client version: 5.1.62_1, Windows 10 amd64. IPv6 disabled in adapter properties.

I read in another post that there is no way to disable IPv6 on the NX server, but that “it should still work” with ipv4. It doesn’t look like it works when IPv6 is disabled on the system. Or is there another problem causing my client/server to close the connection (after authentication)? Any workaround?

Thanks!

[brotech]

Hello Romz,
instead of nxerror.log where there are often harmless errors, please take a look in: /usr/NX/var/log/nxserver.log file for any errors reported.

If nothing useful is there, please enable debug in /usr/NX/etc/server.cfg and /usr/NX/etc/node.cfg file, restart NoMachine server (sudo /etc/NX/nxserver –restart), then reproduce the problem (connect using nxplayer on windows and get error 138 connection timeout out and send to us /usr/NX/var/log/nxserver.log file to forum at nomachine.com.

Full instructions are here:
https://www.nomachine.com/DT07M00098

NoMachine server doesnt currently have problems when disabling IPv6.

[Author]

Posts