When I try to connect form my Windows 7 box using th NX Client I get an error:-
Authentication failed for user xxxxxxxx
I guessed it was permissions so on the Ubuntu box I tried:-
sudo nxserver --useradd xxxxxxxx
I got the response:-
NX> 100 NXSERVER - Version 3.2.0-74-SVN OS (GPL, using backend: 3.5.0)NX> 500 Error: The passdb function is not activated in node.conf.Most probably your FreeNX setup will work out of the box without thisfunctionality and you've been misleaded by an old tutorial or olddocumentation to do this step.If however you really need this functionality, just setENABLE_PASSDB_AUTHENTICATION="1" in node.conf.
if you mean the ubuntu box, yes there is only the one user account.
You will have to more specific I'm afraid, show details?
This only on my private LAN and it's a trial so I'm not worried about security at this point in time.
If you connect the details of why a connection failed are "hidden" and only shown when you push a "details" button.
I meant that because I didn;t go for defaults i have no experience with out of the box work, just with a generated keypair.
Anyway the keypair is available on the server, you can lift the private key from there and paste it in your connection profile.
(and see if they are equal too BTW).
It is behind the Key button in the 3rd screenshot. [ General Tab ].
There you need the private key part of the keypair on the server.
(if you use ssh-keygen you get a privatekey.. privatekey.pub )
On the server you have an ~nx/.ssh/authorize_keys2
Containing all public keys, the private key needs to be pasted into the nx config...
~nx is short for the home directory from the nx user.
On your workstation in then ~/.nx folder [ /home/user/.nx ] the connection profiles are stored. [ if you hit the save button on the nxclient software ]/
To verify nx setup on the system where the nxserver runs do:
ssh into your server
sudo -s # if not logged on as root ]
cd ~nx/.ssh
ls -la
Alternatively use:
ssh into your server
sudo -u nx -s
ls -la # should show a .ssh directory
cd .ssh
ls -la # should show the same as the last command in the previous set.
It should not be empty as at least the default public key should be stored there.
no..
The key consists of an assymmetric key pair: the public part is different from the private part, but they can only be used together.
The public key part of the key is in the authorized_keys2 file, the private part should be in the nxclient profile.
If the private part of the default key is in the client.id_dsa.key file on your server.
After the session state is final the Details button should become "un-greyed".
IF it just dissappears you may need to examine the logs on the server:
grep -i nx /var/log/*
And see if something about some obvious mistakes are mentioned.
If no sufficient info can be found, you can turn on "debug" logging by updating the
/usr/nx/etc/server.cfg
$ /usr/NX/bin/nxserver --version
NXSERVER - Version 3.5.0-5
Appearantly different.
The bottom line is you need to find where the config file is for NXserver and you have to enable debug mode to get better logging. [ i think ]
--update show the location of the config file on my ssytem.
3.2.0 might be a bit old esp. if parts of 3.5.0 are used. On my system all parts are of 3.5.0.x
where the x varies.
So it might be a version problem internaly, some debug logging most probably will tell this.
After running Ubuntu some time, you will be asked to download updates for fixing bugs and security updates.
All the packages you download replace the previous ones, except for the kernel, also called "linux-image". This is due to the fact that w…
If you use Debian 6 Squeeze and you are tired of looking at the childish graphical GDM login screen that is used by default, here's an easy way to change it.
If you've already tried to change it you've probably discovered that none of the old met…
Watch the video to know the process of migration of Exchange or Office 365 mailboxes in absence of MS Outlook. It is an eminent tool which can easily migrate Public, Archive user mailboxes from one another Exchange server and Office 365. Kernel Migr…