Forum Replies Created
-
Posts
-
After digging deeper, looks like I missed executing a CMD:
NoMachine administrator is a valid account on the Cloud Server (CS) host having special rights for NoMachine. Being a NoMachine administrator doesn’t affect system privileges of that user. To assign such NoMachine privileges to a system user, execute on the CS host:
nxserver --useredit USERNAME --administrator yesAfter executing this command, now adding a new server works.
Thanks for the reply.
The articles are really helpful, after reading these, NoMachine still doesn’t work as I expected.
Here’s my situation:
1. have 3 machine :172.16.234.151 (NoMachine Cloud Server install), 192.168.33.233 (Winserver 2019，NoMachine Enterprise Desktop evaluation version installed) and 192.168.33.169 (my client Win10),
PS: these 3 computers can ping each other successfully (firewall disabled all of them), so the connection is not a problem.
2. add server (Enterprise Desktop) to Cloud Server by GUI or CMD, but all fails, CMD runs on Cloud Server (172.16.234.151), and the error shows as bellow:
C:\Program Files (x86)\NoMachine\bin>nxserver –serveradd 192.168.33.233 –lable “ed1 serveice2”
NX> 830 Connected to NoMachine remote server.
NX> 763 Could not authenticate on the remote server using server’s public key.
NX> 763 Would you like to login on the remote server as a privileged user to add
NX> 763 this key and try again? [yes|no]: yes
NX> 830 Connected to NoMachine remote server.
NX> 765 Username: administrator
NX> 766 Password:
NX> 508 ERROR: Cannot add remote server ‘192.168.33.233:4000’. Cannot connect to the remote server.
The error msg “Cannot add remote server ‘192.168.33.233:4000’. Cannot connect to the remote server.” shows on GUI also when I login to Cloud Server (172.16.234.151) via web and click add server.
And as the article asked, the Cloud Server and Enterprise Desktop both have the same username administrator.
So what went wrong??