Making nx work again

alaios · June 2, 2015, 4:23pm

Dear all,
I have installed the latest nx server version to opensuse. I would like to allow my windows client or linux client from home to connect to my linux work computer.

I think I would need some help at the beginniing to confirm that my server is correctly set. Can you help me on what I need to check configure on my service to make sure that I am doing it right?

At the same time I am trying to connect from my windows machine to my linux server, but I fail. I guess it would help me if I can check somehow fast on my linux nxserver that the requests make it to my work computer or not. I thought I could use a tcpdump but I can not filter enough the packets (nx runs on ssh port) to see if a connect request from my windows machine makes it.

Can you please help me sort out what is going wrong?

I would like to thank you for your reply
Regards
Alex

hcvv · June 2, 2015, 5:00pm

Please, which version of opeSUSE.

malcolmlewis · June 2, 2015, 5:21pm

Hi
If you go into YaST firewall and under allowed services on the right in the dropdown have you allowed the NX service. AFAIK it also uses ssh, so is the ssh service enabled and running as well as allowed through the firewall.

alaios · June 3, 2015, 9:52am

Welcome to openSUSE 13.1 “Bottle” - Kernel \r (\l).

nxserver --version
NoMachine - Version 4.6.3

In the firewall module noew I can see the following services in the drop down menu:

DHCPv4 Server
DHCPv6 Server
dnsmasq
HTTP server
…
Secure Shell server (I just allowed it)

but

I can not find the nx listed there

I would like both my ssh and nx running on port 5902 though

I would like to thank you for you reply

Regards
Alex

alaios · June 3, 2015, 4:47pm

Hi,ca
n you please help me find the right way to see if requests are coming at my 5902 port or not?
Regards
Alex

malcolmlewis · June 3, 2015, 4:55pm

Hi
Is this the NX Player? If so AFAIK, they use different ports…

Can you temporarily disable the firewall on the openSUSE machine and check it connects, then we can work out the port.

alaios · June 3, 2015, 5:37pm

Hey. Your avatar is back
I have used tcpdump on my port to see for incoming connections. I had one small mistake on my clients tunnel an thus I could not reach my server. I fixed it! Now I canconnec tto server and see the ssh packets coming in.
I am getting authentication error though. I am trying to remember what I have to do with nx users…

Alex

malcolmlewis · June 3, 2015, 9:09pm

Hi
You need to configure sshd on the server for .ssh/authorized_keys2 for NX. Restart the ssh service.

alaios · June 3, 2015, 10:01pm

Why 2?
I guess after that I would be able to log in with just my normal kde user name. Right?
Regards
Alex

malcolmlewis · June 3, 2015, 10:10pm

Yes, login in as your normal user, is this just NX server, not NX player?

alaios · June 5, 2015, 10:14am

From my sshd configuration file

#RSAAuthentication yes
#PubkeyAuthentication yes
AuthorizedKeysFile      .ssh/authorized_keys2

# For this to work you will also need host keys in /etc/ssh/ssh_known_hosts
#RhostsRSAAuthentication no

it looks enabled.

I guess I might also see what there is indeed inside my

~/.ssh> vi authorized_keys2

Any ideas how I can check that this files content is correct? (It has some line inside…)

malcolmlewis · June 5, 2015, 2:40pm

On Fri 05 Jun 2015 08:16:01 AM CDT, alaios wrote:

From my sshd configuration file

Code:

#RSAAuthentication yes
#PubkeyAuthentication yes
AuthorizedKeysFile .ssh/authorized_keys2

For this to work you will also need host keys

in /etc/ssh/ssh_known_hosts #RhostsRSAAuthentication no

it looks enabled.

I guess I might also see what there is indeed inside my

~/.ssh> vi authorized_keys2

Any ideas how I can check that this files content is correct? (It has
some line inside…)

Hi
On the client if you generate your public key (eg rsa) then on the
server’s ~/.ssh/authorized_keys2 file you would add the rsa key from the
client.

–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel 3.12.39-47-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

alaios · June 6, 2015, 8:31am

Hi,
I am not sure I understand that.

Can you give me a bit more details?
Regards
Alex

hendwolt · June 6, 2015, 8:50pm

Hi,

if you are using the free version of NX4, you can’t use ssh in the same way as with NX3.* , if I get this right:

https://www.nomachine.com/AR10K00728

Hendrik

alaios · June 7, 2015, 1:51pm

I guess that might be the problem that in the past I was using version before 4 and now I am using version 4, so I think files of different versions are used…
How I can clean stuff from my server?

Regards
Alex

hendwolt · June 7, 2015, 8:19pm

I guess, you used rpm to install the packages.
First, check the installed versions, for example with:

rpm -qa | grep nx

To uninstall (erase):

rpm -e <package name>

Hendrik

alaios · June 7, 2015, 9:17pm

if I remove the ~/.ssh/authorized_keys2
would that be recreated as needed?

Regards
Alex

alaios · June 7, 2015, 9:40pm

I removed the authorized key completely.
I tried connected and got the message

This server does not support connection over ssh. Switch to NX protocol? (unfortunately I can not make this error message happen again).

I have pressed yes and then I immediately got the following error

Error is 22: Invalid argument

So what I do next?
For me is clear that I can reach from my client my server… It looks like that there is misconfigured on my server. What that can be?

Regards
Alex

alaios · June 8, 2015, 7:29am

I have missed this post so I copied my ssh public key as you said. Problem persists.
I also used this guide, that explains about my problem but still problem persists

How I can see server log files, so I can understand why connection fails?

Regards
Alex

alaios · June 8, 2015, 7:48am

I also found these from my server log files…
Error: Can’t bind the socket for proto ‘TCP’.
Error: Error 98 ‘Address already in use’.
Info: Server with pid 29223 terminated on Mon Jun 8 07:25:49 2015.
Info: Server started with pid 29226 on Mon Jun 8 07:25:49 2015.
Info: Listening for connections on any interface on port 5902.
Info: Accepting connections from any host with encryption enabled.
29226 29226 07:25:49 165.440 Socket: WARNING! Can’t bind the IPv6 socket.
29226 29226 07:25:49 165.480 Socket: WARNING! Error is 99 ‘Cannot assign requested address’.
29226 29228 07:25:49 165.655 TcpListener/TcpListener: ERROR! Can’t bind the socket for proto ‘TCP’.
29226 29228 07:25:49 165.679 TcpListener/TcpListener: ERROR! In method ‘startTcp()’ context .
29226 29228 07:25:49 165.690 TcpListener/TcpListener: ERROR! Error is 98 ‘Address already in use’.
Error: Can’t bind the socket for proto ‘TCP’.
Error: Error 98 ‘Address already in use’.
Info: Server with pid 29226 terminated on Mon Jun 8 07:25:49 2015.
Info: Server started with pid 29229 on Mon Jun 8 07:25:49 2015.
Info: Listening for connections on any interface on port 5902.
Info: Accepting connections from any host with encryption enabled.
29229 29229 07:25:49 282.241 Socket: WARNING! Can’t bind the IPv6 socket.
29229 29229 07:25:49 282.279 Socket: WARNING! Error is 99 ‘Cannot assign requested address’.
29229 29231 07:25:49 282.519 TcpListener/TcpListener: ERROR! Can’t bind the socket for proto ‘TCP’.
29229 29231 07:25:49 282.567 TcpListener/TcpListener: ERROR! In method ‘startTcp()’ context .
29229 29231 07:25:49 282.584 TcpListener/TcpListener: ERROR! Error is 98 ‘Address already in use’.
Error: Can’t bind the socket for proto ‘TCP’.
Error: Error 98 ‘Address already in use’.