Re: NX client not connecting
- From: Vahis <waxborg@xxxxxxxxxxxxxxxx>
- Date: Mon, 04 Sep 2006 15:59:59 +0300
Darrell Stec wrote:
I have NX System (from Suse) installed and running (I think it is still
running). I downloaded NoMachine's Windows client and installed it on
a friend's WinXP computer. I get a connection timeout error.
[I put in the IP that the public sees in the host field and a user name
with appropriate password. I use the ADSL setting which is the
default]
I enabled SSH (port 22) in the Firewall on my machine. I also have a
D-Link 604 router. Could this be stopping the connection? How do I
check to see if the NX server is actually started on my machine (I
thought it ran correctly using the Demo NX client -- kNX)?
I am using Suse 10.0 if that makes a difference.
Have you pasted the key into the client's key window?
After installing FreeNX:n and running the Setup script
# nxsetup --install --clean --purge
The script returns like this:
Removing configuration files ...done
Setting up /etc/nxserver ...done
Generating public/private dsa key pair.
Your identification has been saved in
/etc/nxserver/users.id_dsa.
Your public key has been saved in
/etc/nxserver/users.id_dsa.pub.
The key fingerprint is:
18:91:df:2a:9a:a1:7a:a9:5c:68:5c:d5:17:19:07:74
root@machinename
Setting up /var/lib/nxserver/db ...done
Setting up /var/log/nxserver.log ...done
Setting up user nx ...done
Setting up known_hosts and authorized_keys2 ...Unique key
generated;
your users must install
/var/lib/nxserver/home/.ssh/client.id_dsa.key
on their computers.
done
Setting up permissions ...done
Ok, nxserver is ready.
PAM authentication enabled:
All users will be able to login with their normal passwords.
PAM authentication will be done through SSH.
Please ensure that SSHD on localhost accepts password
authentication.
You can change this behaviour in the
/etc/nxserver/node.conf file.
Warning: Clients will not be able to login to this server
with the standard key.
Please replace /usr/NX/share/client.id_dsa.key on all
clients you want
to use with /var/lib/nxserver/home/.ssh/client.id_dsa.key
and protect it accordingly. mainitun polun päässä avain:
/var/lib/nxserver/home/.ssh/client.id_dsa.key
Now, in the section Warning! you'll see where they is created.
This key needs to be given to the client when you open the
connection.
Configure >advanced setup > copy/paste the key into the window "Key".
Later you can, if you like create new pair of keys like:
# nxkeygen
after which you do the same as above again.
Vahis
--
Sometimes I reply to top posters. Seldom. And usually just once.
http://waxborg.servepics.com/English/Linux/SUSE.10.1/suse10.1.html
SUSE Linux 10.1 Suomi:
http://waxborg.servepics.com/Linux/10.1/suse-10.1.html
.
- Follow-Ups:
- Re: NX client not connecting
- From: Darrell Stec
- Re: NX client not connecting
- References:
- NX client not connecting
- From: Darrell Stec
- NX client not connecting
- Prev by Date: Re: SuSE 10.0 Patch breaks RaLink RT2561/RT61 wireless
- Next by Date: Re: 10.1 update error - packages not found
- Previous by thread: Re: NX client not connecting
- Next by thread: Re: NX client not connecting
- Index(es):
Relevant Pages
|
