Forum Replies Created
OK, latest update. When I first installed the Cloud Server, it worked fine. Then I had to reboot to apply some updates, now Cloud doesn’t work anymore. Only the SSH can be started, all other services are off. Trying to start the server doesn’t do anything, it will never start.
OK, I installed the Enterprise Desktop on a bunch of clients. I then added them to the Cloud Server interface. This now works well, except for one client. On that one, I can’t connect. It just won’t add to the Cloud Server no matter what, and I can’t tell what the issue is. It’s set up exactly the same as all the other clients. I can add the Cloud Server to it (or it does it automatically), but I can’t add it to the Cloud as a child like the others.
I get an error saying “remote host identification has changed” whenever I try.
I’m following those instructions, I installed the cloud product on the main pc, then I installed enterprise desktop to another client. But I am not able to add the client to the server from that web interface. Anything I try it doesn’t work, gets rejected.
I tried the Cloud server product. I installed it on one of my clients. Do I need to install it on all the clients? I don’t understand what is different. There is that web interface where I can connect to the computer where the cloud server is, but it’s just one client. The others are still the same on the regular NoMachine free installs. Anyway, I can’t tell what I am looking for, please advise. Thanks.
Ah thank you, I understand the port forwarding you mentioned and will try it.
And yes, I will also try the cloud product. Thanks.
The one that would work I believe is:
Use Case 2: Cloud Server behind a NAT
So are you saying you can’t do this without the cloud server product?
I checked the pricing, it is pretty expensive. I guess it sounds like without paying for the enterprise product, I can only access one machine on my home network. Is that correct?
OK this is now fixed. I’ll explain….
The problem was the nx user directory. On Windows server machines, the NoMachine installer needs to create an nx user directory in the profiles folder. When I first installed it, it couldn’t create it, and that was the reason why I couldn’t connect the machines to each other.
Then, I reinstalled using Admin elevation (even though the account already was admin) and this time I didn’t get an error regarding the installer couldn’t create nx directory. After that, everything works fine.