Welcome to LinuxQuestions.org, a friendly and active Linux Community. You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free.
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in. Are you new to LinuxQuestions.org? Visit the following links: If you have any problems with the registration process or your account login, please. If you need to reset your password,. Having a problem logging in? Please visit to clear all LQ-related cookies. Introduction to Linux - A Hands on Guide This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
To receive this Complete Guide absolutely free. I was able to connect the first time following the instructions here: 1. First time i was able to connect i used the nx client for Mac OS X. I logged off. Then i decided to test this using Windows nx client and i got: NX 203 NXSSH running with pid: 604 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: 208.85.242.181 on port: 22 NX 202 Authenticating user: nx NX 208 Using auth method: publickey NX 280 Exiting on signal: 15 and a NOMACHINE popup window saying: 'connection timeout' 3. Came back to my mac os x machine i tried connecting again. I got the same error as indicated in #2.
Went to my linux machine i tried connecting. I got the same error as indicated in #2. Now i'm not able to connect from anywhere! Help is appreciated! See if you have a /var/log/nxserver.log file available. Locations may be different on different distros, but /var/log is usually where this stuff goes. Also check /var/log/messages, /var/log/syslog, /var/log/auth and other logfiles that appear relavent for something that might contain a clue.
Can you ssh into the target box OK? (not NX, just plain old ssh) Are these three computers all on your LAN? Any possible router or firewall changes you might have made that may be interfering? Try using the ssh key you have for your NX client to go directly to your target via ssh (not NX).
E.g., ssh -vv -i thekeyfilename in editThe option above is 'dash vee vee', not 'dash double-you' (sometimes that is hard to tell depending on your font in use)/edit If this fails, and the -vv (verbose) output from ssh on your client side doesn't tell you what's going on, look for details of the session on the target in /var/log/auth.log (or syslog, or messages, or whatever other file your distro may be putting these in). Note: ssh will mysteriously fail on you, and not tell you why, if you have too loose permissions on the target server. Your (actually the nx login's) $HOME directory on the target should be mode 755, under that.ssh should be 755, (better yet, 700), and your authorizedkeys and/or authorizedkeys2 file should be 600. Usually permissions problems give you a blatant failure, not a timeout, though. Hi, I'm using centos 5: 1. File /var/log/nxserver.log is empty 2.
File /var/log/messages displays logs about pure-ftp 3. File /var/log/syslog does NOT exist 4. File /var/log/auth does NOT exist 5. I CAN SSH to the target box 6. 2 computers are in the same LAN (Mac OS X & Linux) 1 (Windows vista) at another location. NO firewall/router changes 7. Ssh -vv -i thekeyfilename in.
I'm not sure how to do this,but i copy/paste the NX client key into a file in my local computer and then tried your command and i was able to login into the remote server. I also did: /sbin/service freenx-server restart it went OK and still not able to connect. Thanks for the help. They are different. NoMachine came up with the NX server and made their source code available.
FreeNX then made a GPL free version of the server. The function of the two servers is the same (although the NoMachine has a few extra features). Then later, NoMachine decided to make their server free for Linux (where before you have to pay for this). The NoMachine server uses libraries that come with their client (which has always been free) so that's why they tell you to also install the client. FreeNX does not have their own client, they've always just said 'download the free NoMachine one'. The FreeNX server is mostly written in shell.
I imagine the NoMachine one is a binary executable. Since I am using FreeNX, I did not install any client software, because you don't need to with FreeNX. You only have to do that with NoMachine NX. And the NoMachine NX server setup may be different than the FreeNX setup. Never having used the NoMachine variety, I wouldn't know. Thanks haertig. I did those steps in order and no luck.
I get error message from client: 'DSA key is corrupted or has been protected with a passphrase' this i not sure how to do, because when i created the user cocotuc i got: sudo /usr/NX/bin/nxserver -useradd cocotuc NX 900 Setting password for user: cocotuc. NX 102 Password: NX 102 Confirm password: NX 110 Password for user: cocotuc added to the NX password DB. NX 900 Adding public key for user: cocotuc to the authorized keys file. NX 900 Verifying public key authentication for NX user: cocotuc. NX 900 Public key authentication succeeded.
NX 301 User: cocotuc enabled in the NX user DB. Does this means i have to copy/paste the public key in /home/cocotuc/.ssh/? I did that and got the above error msg. Output of tail -f /var/log/messages: Dec 8 16:31:48 c693d85 NXSERVER-3.3.0-826046: Cannot read from stdin: NX client disconnected before the 'bye' message: exiting cleanly 'NXShell::handleExitRequests' Dec 8 16:47:22 c693d85 NXSERVER-3.3.0-828955: Added password for user: cocotuc to the NX password DB. NXShell::handlerusersetpassword NXShell 373 Dec 8 16:47:22 c693d85 NXSERVER-3.3.0-828955: User 'cocotuc' logged in from '127.0.0.1'. 'NXLogin::set' Dec 8 16:47:24 c693d85 NXSERVER-3.3.0-828955: User 'cocotuc' from '127.0.0.1' logged out.
'NXLogin::reset' thanks.
Im running CentOS 4.4 with FreeNX. However, when i run custom 'startxfce4' on my Windows client it see the desktop for a second then it errors out and disconnects. Am I setting something wrong? I can Gnome/KDE fine just XFCE doesnt work. Exactally blkcamarozr28, thats the same problem I'm having I tried it in both CentOS 4.4 and Fedora Core 6, still same problem on both platforms. I just assumed there was some kind of trick to getting nomachine FreeNX to work with XFCE, because I too can with Gnome and KDE just fine, just not XFCE, so I assumed it was XFCE specific.
Yes, I had the same experience on my Ubunto desktop. Even if I enable the New Virtual Desktop option, the windows are scattered and not contained within the main desktop. Its confusing and not very pleasing to use. There are windows that would not close even if you clicked it to close. My interest in using XFCE is to have a lightweight desktop for remote administration using Nx or VNC. I've had little success with the latter so I shifted to Nx/FreeNx on a CentOS 5 server. Sad to say, no documentation is available on making this work, so I have to use Gnome which runs perfectly inside the Nx window.
I hope someone could offer or make a fix. To the developers, I still believe in your product though, and would continue to patronize it in situations that its use would be advantageous. Remote Desktop (RD) is one such area, so may I suggest that a team should be tasked to handle its performance over RD protocols?