Forum / NoMachine for Linux / How to setup server on Centos
- This topic has 16 replies, 7 voices, and was last updated 9 years, 7 months ago by titan.
October 22, 2013 at 09:05 #180
I just downloaded and installed NoMachine for Linux 64-bit. However, I was not able to start the server (nxserver) as out-of-box.
when I issued the following command:
I got the output as
NX> 161 Enabled service: nxserver.
When I issued the command:
I got the output as
NX> 161 Enabled service: nxserver.
NX> 162 Disabled service: nxd.
Basically, I couldn’t start nxd, even when issuing
/usr/NX/bin/nxserver –start nxd
How can I start nxd? Is it required for the server?
Any help is greatly appreciated.
October 22, 2013 at 19:16 #194jwcpcParticipant
- This topic was modified 9 years, 7 months ago by John Watts. Reason: spelling for process nxd
You are using the base NoMachine for Linux free product? What Linux distribution are you using to host the NoMachine install? e.g. Red Hat, etc.
Can you still make a connection to your NoMachine installation even with this error message?
/JohnOctober 22, 2013 at 19:42 #197jwcpcParticipant
Sorry I meant what specific version of Centos are you running?
/JohnOctober 29, 2013 at 20:54 #331
I’m going to piggy back on to this one because I have the same issue.
The machine that NX is installed on is CentOS 5.8 32-bit.
LewisOctober 30, 2013 at 05:34 #356fordboy0Participant
Edit /etc/selinux/config and change ‘SELINUX=enforcing’ to ‘SELINUX=disabled’ and reboot.October 30, 2013 at 11:29 #370
This was done previously. Any other suggestions?
LewisOctober 31, 2013 at 00:58 #387
I am still trying to get the latest non-enterprise version 4.0.360 for 64-bit to work for my centos as server and Windows 7 as client. No success so far.
What I’ve tried are as below:
Right out-of-box for both server and client with NX protocol, connection timed out. If I connect client and the server on the same centos machine, it works.
Somehow, I think that the NX protocol on port 4000 does not work for me if the client is on a Windows 7.
When switching to SSH protocol by adding SSH to ClientConnectionMethods in server.cfg, I can get the login, but then got “Error is: SSH connections are not supported on this server.”. By reading the doc, it appeared to me that SSH protocol is not supported in the non-enterprise version.
Any guidance on what to try the next…
JasonOctober 31, 2013 at 12:23 #389sil04Participant
If I connect client and the server on the same centos machine, it works.
can be that a firewall rule is blocking port 4000?October 31, 2013 at 20:41 #401
In my case, the firewall is disabled.
LewisNovember 2, 2013 at 03:39 #415
My firewall on centos where NX server is running is also disabled. Could be other network setting blocking me from access it?
On another machine in my office, ‘telnet x.x.x.x 22’ connects where x.x.x.x is the IP for the centos. But ‘telnet x.x.x.x 4000’ doesn’t connect.
Is there a way to enable SSH (port 22) protocol on the server with my non-enterprise version 4.0.360?
JasonNovember 2, 2013 at 09:10 #416titanParticipant
can you please tell me what you see in /usr/NX/var/log/nxd.log on the server?November 2, 2013 at 23:10 #418
I just stopped nxd, deleted nxd.log and then restarted nxd so that you can have a clean log file to take a look at. I also tried to connect to it from my Windows 7 client with no success. Below is all in the nxd.log.
Info: Server started with pid 17603 on Sat Nov 2 14:51:28 2013.
Info: Listening for connections on any interface on port 4000.
Info: Accepting connections from any host with encryption enabled.
It doesn’t look like it received any connection request. On my NX client window, it displayed:
Could not connect to the server.
Error is 138: Connection timed out
If we cannot resolve this due to network setting for port 4000, can we possibly enable SSH port 22 on the NX server? Again, I’m using the non-enterprise version 4.0.360 for 64-bit.
Thanks for your help!
JasonNovember 3, 2013 at 12:34 #424titanParticipant
open a console and run:
> ps auxwww| grep nxd
You should see nxd running with pid 17603. Can you see it?
AFAIR you said that you can connect to nxd when running the client on the same machine. It seems to me a trivial firewall problem, that is the connection on port 4000 is blocked before reaching nxd. It can be a security feature on your machine blocking connections to “unknown” services. The installation script adds all the required rules for SELinux and AppArmor. You disabled SELinux and this didn’t work either… I don’t think changing port will help, but…
Install netcat (nc) and run:
> nc -l 4012
Or some other port. Then on another machine:
> telnet server_machine 4012
Can you connect to this other port?
There is not much more that I can say. What I can suggest is:
– Tunnel the connection to that machine by ssh. See this post on how to do it:
– Install the Workstation evaluation. In the meanwhile we’ll investigate if there are similar reports from other usersNovember 5, 2013 at 02:49 #447
Thanks for the tip of tunneling. I installed openssh on my windows and used it to tunnel the way you described. My NX client can now connect to the NX server.
Great help! Thanks again.
JasonNovember 5, 2013 at 12:33 #463sil04Participant
can you please provide output of this command?
It’s for checking if iptables are still on for some reasons.
This topic was marked as solved, you can't post.