kroy

[kroy]

Can you verify that the firewall is not blocking NX ports on that windows 10? NoMachine use 4000 and 4022.

[kroy]

Hi.
This same output can show if you install 64-bit version on 32-bit architecture. Can you verify it? You can check it for example by using command uname -m on that Ubuntu.

If your architecture is 32-bit you need to uninstall 64-bit version and remove /usr/NX directory (sudo /usr/NX/scripts/setup/nxserver --uninstall && sudo rm -rf /usr/NX) and install correct version.

[kroy]

Hi Nick,

Could you enable and gather debug logs from both server and client sides, and then send them to us at forum[at]nomachine[dot]com. Instructions are available here: https://www.nomachine.com/DT04M00076.

[kroy]

Could you run debug mode and send logs from the server to forum[at]nomachine[dot]com? Instructions how to collect logs: https://www.nomachine.com/DT04M00076#1.

[kroy]

Could you send logs from server and client side to forum[at]nomachine[dot]com? There are instructions on how to collect them: https://www.nomachine.com/DT04M00076.

[kroy]

Hi.
Username and password required by the NoMachine is your usual account credentials from your remote machine. For example you can check which user is logged to that machine using command whoami.

If you don’t want to use your account credentials, you can also use NoMachine database. To enable it change values in server configuration file (it’s placed in /usr/NX/etc/server.cfg on remote machine) and uncomment two lines:

EnableUserDB 1
EnablePassDB 1

Then you can add your nomachine users by using command
sudo /usr/NX/bin/nxserver –useradd <enter_here_new_username>

Details you can find there: https://www.nomachine.com/DT12I00014

[kroy]

Hi.
Have you some issues with connection to that server? The log shows that connections works well. Can you describe in more details the problem?

Logs also will be helpful. There is instruction how to collect it: https://www.nomachine.com/DT04M00076#1
Send logs to forum[at]nomachine[dot]com or attach them here.

[kroy]

We weren’t able to reproduce this problem on mentioned platforms. Does it always happen?

Logs would be useful, can you send us logs from client side once you’ve
reproduced the problem? Instructions are here: https://www.nomachine.com/DT04M00076#4

[kroy]

We aren’t aware of this issue. We will investigate the problem.

[kroy]

Thank you for reporting this issue. We reproduced the problem and opened the following trouble report:

https://www.nomachine.com/TR03M05150

This issue should be solved in the next update, you may check the ‘Notify me when the TR is closed’ option in the trouble report page to be informed when the fix is released.

[kroy]

We couldn’t reproduce problem on basic configured CentOS 7. Anyway the description can indicate that it may be problem similar to https://www.nomachine.com/TR02M05028

Is there possibility that your user belongs to a group with a name containing spaces?

If not – please run debug mode and send logs from server side if you were able to reproduce problem. There is instruction how to collect logs: https://www.nomachine.com/AR07K00677

Please send everything to forum[at]nomachine[dot]com.

[kroy]

We configured OpenConnect VPN and we were able reproduce a similar problem, but that issue does not appear each time we try to connect.

We need more information. Please run debug mode and send to us logs from server side if you reproduce problem. Here you can find instruction how to collect logs: https://www.nomachine.com/AR07K00677

[kroy]

More details about computers network are needed. This kind of error could be caused by entering the wrong IP or connection port number.

Routers supporting UPnP or NAT-PMP are configured automatically to pass connections to NoMachine.  All required information is displayed at initial screen (Welcome to NoMachine) when you launch the NoMachine GUI on the remote machine you want connect to.

Please be sure to use the correct hostname/public IP and port when you connect.

Please note also that routers not supporting UPnP or NAT-PMP and Firewalls have to be configured manually to pass traffic to port 4000 (NX protocol), 22 (SSH protocol on Linux/MacOSX) or (4022) (SSH protocol on Windows).

Article: https://www.nomachine.com/AR11L00827 can be helpful.

[kroy]

Thanks for the post. We will answer as soon as we reconfigure our environment to reproduce the problem.

[Author]

Posts