Error The Nx User Db Is Disabled
Contents |
Reports Feature Requests Software Updates Searching in: Articles & FAQs Filter the search results Applies to:
Cannot Add User: Nx To The System.
Software Added on:2005-02-09 Last update:2016-04-12 Print this article How the NX login works with NX nxserver add user 3.5.0 The way NX works is by creating a 'nx' user on the server machine whose shell, /usr/NX/bin/nxserver, is executed any time a remote
Nxserver Commands
NX user connects by SSH using nxclient. To access the server, the client uses a public DSA key. Using this public key forces the SSH server to execute the nxserver shell and prevents any possibility for the special nx 500 error public key authentication failed user 'nx' to login on the machine outside NX. As the 'nx' user is required to properly function, the username for 'nx' cannot be changed. To login, the 'nx' user must go through the usual host authentication and SSL key negotiation mechanisms offered by the Transport Level Security built in SSH. This means that all the traffic between the client and the server is effectively encrypted just as the login would have happened if the 'nx' user had nomachine authentication failed gained access to the server by means of an interactive session. By comparison, this use of SSH is in practice the same that HTTPS servers do with the Secure Socket Layer specification to provide secure access to Web content. Once the user is logged in to SSH, that is they have reached the stage it has entered the nxserver shell, SSH must authenticate to the NX server using any of the available methods. No operation is allowed by the server until the user has authenticated. NX Server can offer arbitrary means for authenticating a user. At the present moment the following methods are supported: - A separate NX server password database. - The currently configured system by which SSH checks the user's password, most likely PAM. In the first case NX tries to match the user's password in its own database. In order to connect, users must be added to the system by a 'nxserver --useradd' command. This offers a separation between system users and NX users, as only users that have been added to the NX system will be able to connect by NX. The second method offers seamless integration with the PAM system configured on the machine. To verify the password, NX will submit the user's credentials to the SSH subsystem. If SSH guarantees the access, then NX will allow the user to enter the session. Besides the basic con
Search All KB Documents Articles &
Nx> 700 Error: Output: Useradd: Can't Get Unique System Gid (no More Available Gids)
FAQs Trouble Reports Feature Requests Software Updates Searching authentication to nx server failed in: Trouble Reports Filter the search results Last update: Any dateLast weekCurrent monthCurrent
Nx Client
year Affects:
Get Kubuntu Get Xubuntu Get Lubuntu Get UbuntuStudio Get Mythbuntu Get Edubuntu Get Ubuntu-GNOME Get UbuntuKylin Ubuntu Code of Conduct Ubuntu Wiki Community Wiki Other Support Launchpad Answers Ubuntu IRC Support AskUbuntu Official Documentation User Documentation https://ubuntuforums.org/showthread.php?t=1283875 Social Media Facebook Twitter Useful Links Distrowatch Bugs: Ubuntu PPAs: Ubuntu Web Upd8: Ubuntu http://vanilla.slitaz.org/index.php?p=/discussion/1881/setting-up-a-nomachine-nx-server/p1 OMG! Ubuntu Ubuntu Insights Planet Ubuntu Activity Page Please read before SSO login Advanced Search Forum The Ubuntu Forum Community Ubuntu Official Flavours Support General Help [ubuntu] NXServer/SSH Authentication issues Having an Issue With Posting ? Do you want to help us debug the posting issues ? < is the place to report it, thanks ! Results 1 add user to 3 of 3 Thread: NXServer/SSH Authentication issues Thread Tools Show Printable Version Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode October 6th, 2009 #1 promet View Profile View Forum Posts Private Message Gee! These Aren't Roasted! Join Date May 2005 Beans 143 NXServer/SSH Authentication issues Heya, I'm trying to fix my NoMachine nxserver install. This used to work really well, but I've started having authorization error the nx issues. using the: Code: sudo /usr/NX/bin/nxserver --usercheck username tool, it reports success, a la: Code: sudo ./nxserver --usercheck promet NX> 900 Verifying public key authentication for NX user: promet. NX> 900 Adding public key for user: promet to the authorized keys file. NX> 716 Public key added to: /home/promet/.ssh/authorized_keys2. NX> 900 Verifying public key authentication for NX user: promet. NX> 900 Public key authentication succeeded. NX> 999 Bye. But when trying to login to the server via nxclient, I get the following error consistently: Code: NX> 203 NXSSH running with pid: 28262 NX> 285 Enabling check on switch command NX> 285 Enabling skip of SSH config files NX> 285 Setting the preferred NX options NX> 200 Connected to address: 127.0.0.1 on port: 6784 NX> 202 Authenticating user: nx NX> 208 Using auth method: publickey NX> 204 Authentication failed. I suspect it may be due to some sshd configuration issues, but I can't pinpoint the issue. Here is my sshd_config: Code: # Package generated configuration file # See the sshd(8) manpage for details #Allow only users in the following group to access the server #AllowGroups sshusers #AllowUsers nx promet # What ports, IPs and protocols we listen for Port 6784 # Use these options to restrict which interfaces/protocols sshd will bind to #ListenAddress :: #ListenAddress 0.0.0.0
SSH and X forwarding. It works wonderfully with key-only auth, no passwords are accepted, and I often run graphical apps via my netbook. Fantastic, but a little slow on dodgy/slow connections elsewhere; I'd like to have some compressed or optimised remote desktop going, low colours & resolution etc.. I'd like NoMachine (NX) but am having some trouble connecting. This are the steps I have taken:1. Unzip 3x NX packages (client, node, server) on server into /usr to create /usr/NX directory.2. Unzip client package on client.Server:3. Created links /etc/rc.d/rc#.d/ to /etc/init.d/4. Modify scripts/setup/nxserver by: - fixing user add/del commands in lines 924, 963, 984, 1032. - comment out command in line 956 (will do manually later) - drop "2" from authorized_keys2 in line 25735. Run: sudo ./scripts/setup/nxserver --install fedora - doesn't really matter but it's the closest match6. Change server name & SSH port in /usr/NX/etc/server.cfg (line 31, 36 & 236)7. Allow admin logins in line 87 of /usr/NX/etc/server.cfg8. Drop "2" from authorized_keys2 in line 337 of /usr/NX/etc/server.cfg9. Modify scripts/setup/nxnode by: - specify SSH port in line 43 - change to local.sh on line 130510. Run sudo ./scripts/setup/nxnode --install fedora - ignoring warning about CUPS detection, I don't have a printer11. Change server name & SSH port in /usr/NX/etc/node.cfg (line 32, 342)12. Drop "2" from authorized_keys2 in line 186 of /usr/NX/etc/node.cfg13. Run: sudo bin/nxserver --restart (no errors)14. Enable the nx user account by using: sudo passwd -u nx15. Run twice: sudo bin/nxserver --usercheck seawolfseawolf@Felicity:/usr/NX $ sudo bin/nxserver --usercheck seawolfNX> 900 Verifying public key authentication for NX user: seawolf.NX> 900 Adding public key for user: seawolf to the authorized keys file.NX> 716 Public key added to: /home/seawolf/.ssh/authorized_keys.NX> 900 Verifying public key authentication for N