Forum / NoMachine Cloud Server Products / Running into trouble connecting to clients through Cloud Server
- This topic has 3 replies, 2 voices, and was last updated 4 years, 3 months ago by Colin.
-
AuthorPosts
-
July 17, 2020 at 08:47 #28540ColinParticipant
Hi folks! I’m an IT technician for a school system and we’ve been messing around a bit with NoMachine as an option for our students to use personal devices to access shared lab computers during the pandemic. We installed Cloud Server on a Windows server (2012) and installed the desktop client on a few of our computers (some Mac and some Windows). When we try to connect to the Cloud Server, we get to the web page itself just fine, but once we try to connect to a client, we have issues. Connecting to the local host (the server itself) works fine, but any other client gives us errors. At the moment, when trying to connect to one of our Macs, we run into this error in the log:
1464 14:04:39 631.851 Process: WARNING! Assuming temporary directory in ‘C:\Windows\system32\config\systemprofile’.
3624 1700 14:04:39 819.344 Encryptor/Encryptor: ERROR! Failed to authorize the server certificate.
Error: Failed to authorize the server certificate.
3624 1700 14:04:39 819.344 Channel/Channel: WARNING! Runnable DaemonReader failed for FD#508.
3624 1700 14:04:39 819.344 Channel/Channel: WARNING! Error is 13, ‘Permission denied’.
3624 1464 14:04:39 819.344 DaemonClientApplication/DaemonClientApplication: WARNING! Session terminated abnormally.
3624 1464 14:04:39 819.344 DaemonClientApplication/DaemonClientApplication: WARNING! Error is 13, ‘Permission denied’.
3624 4040 14:04:39 913.099 DaemonClientApplication/DaemonClientApplication: WARNING! No client running in 0x015bc060.
In the server cfg file, that client’s section is set up like so (the Host is its IP address):
Name “COMPUTER NAME”
Host xxx.xxx.x.xxx
Protocol system
Port 22
Authentication password
On the Mac itself, it’s set to allow SSH remote connection. When I try to connect to the Mac via the NoMachine desktop client, I set the request to go over SSH and port 22, and it works just fine. When we try to connect to the Mac directly through a browser (https://COMPUTER-NAME:4443) it also works just fine. The hang up seems to be in the cloud server. While it’s good that the direct browser connection works, we’d prefer not to have to hand out a list of the computer names and ip’s for students to connect to.
Any advice is greatly appreciated! Thank you!
-Colin M.
July 17, 2020 at 12:43 #28546brotechParticipantHello,
if I understood correctly, you are trying connect to ‘clients’, when client means only nxplayer.
What have you installed on the Mac hosts that you want to connect?
You should have Enterprise Desktop installed in order to share the desktop. You can add them to the Cloud Server using the command:
/etc/NX/nxserver --serveradd hostname
executed on Cloud Server as administrator or through sudo.
After that students should see a list of available desktops in Cloud Server. If you would like assign a student to a particular ED host, without the need for them to select the host itself, You can use:
/etc/NX/nxserver --useredit student_username --forward-connection ed_host:4000
Regards
July 20, 2020 at 07:48 #28570ColinParticipantHi! Thanks for the info! Enterprise Desktop is indeed installed on the Mac. On our windows based Cloud Server, the Mac is already added and shows up when students go to the Cloud Server. The issue we run into is connecting to it through the Cloud Server. I’ve attached some images to go along with the error log I posted above. This is the display that students currently see when going to the cloud server via a web browser. https://drive.google.com/file/d/1dVz9TF15gbcp3UncBOjPnfBAsrxJb0ct/view?usp=sharing
If I click on GDP-05, I’m given this log in screen, like expected. https://drive.google.com/file/d/1tjLY0yxrV-j-7TiDJYNZrJ8A0t2ROq35/view?usp=sharing
Then once I enter the information, I end up here. https://drive.google.com/file/d/1NDmuUqllu9MnpzrV1ekyhuWCeO9xOUvr/view?usp=sharing
Then this is what the log tells me for that entry:
3248 13:57:50 380.335 Process: WARNING! Assuming temporary directory in ‘C:\Windows\system32\config\systemprofile’.
3872 1440 13:57:50 536.616 Encryptor/Encryptor: ERROR! Failed to authorize the server certificate.
Error: Failed to authorize the server certificate.
3872 1440 13:57:50 536.616 Channel/Channel: WARNING! Runnable DaemonReader failed for FD#508.
3872 1440 13:57:50 536.616 Channel/Channel: WARNING! Error is 13, ‘Permission denied’.
3872 3248 13:57:50 536.616 DaemonClientApplication/DaemonClientApplication: WARNING! Session terminated abnormally.
3872 3248 13:57:50 536.616 DaemonClientApplication/DaemonClientApplication: WARNING! Error is 13, ‘Permission denied’.
3872 3584 13:57:50 630.400 DaemonClientApplication/DaemonClientApplication: WARNING! No client running in 0x0170b328.
So it seems like the Mac is added to the Cloud Server correctly, the connection is just failing somewhere along the line and I’m unsure why, because connecting directly to the Mac via another instance of Enterprise Desktop (circumventing Cloud Server) works just fine.
Thanks again for all the info and I hope the pictures may help show the problem a bit better. Let me know if there are any theories or other things I could try.
-Colin M.
July 20, 2020 at 07:49 #28571ColinParticipantTurns out we were using terminology a bit incorrectly! We figured out that the sections area in the server.cfg was for adding other cloud servers, not child servers (aka the enterprise desktops). Using your serveradd command, we’re all set! Thank you so much for all the help!
-Colin M
-
AuthorPosts
This topic was marked as solved, you can't post.