Suse10 w/FreeNX 1.4.0-44 & WinXP w/NX Client 1.5.0-138

knu2xs · 01-02-2006, 05:35 PM

1. Using YaST, installed FreeNX 1.4.0-44 on Suse 10 box, and opened SSH port in firewall. Started NX Server using...

Code:

# nxsetup --install --setup-nomachine-key --clean --purge

2. Set static IP address and opened port 22 to Suse box through router(DLink wireless).
3. Installed NX Client 1.5.0-138 on WinXP machine. Entered IP address. Enabled SSL. When connecting recieved following message...

Code:

NX> 203 NXSSH running with pid: 3724
NX> 285 Enabling check on switch command
NX> 285 Enabling skip of SSH config files
NX> 200 Connected to address: xxx.xxx.xxx.xxx on port: 22
NX> 202 Authenticating user: nx
NX> 208 Using auth method: publickey
NX> 204 Authentication failed.

Checked compatibility issues of with FreeNX 1.4 & NX Client 1.5. However, this appears to theoretically be mitigated with a line in the node.conf file...

Code:

ENABLE_1_5_0_BACKEND="1"

Have checked all over web for possible solution. Appears most people get further. Apparently there is something very obvious I am overlooking or not seeing. Since this project is my first foray "under the hood" of Linux, what may be obvious to most is still quite obscure.

Can access machine using SSH through command line, thus router is not blocking. Re-checked nxserver, and is indeed running. Just to make sure, restarted nxserver. Still recieve same error.

Thank you in advance for any help, advice, and insight you might have to offer regarding this.

jst1 · 01-03-2006, 08:16 AM

Sorry if some of my terminology is incorrect; I am experienced with this, but unsure if I am using the right names...

When you connect via command line ssh (using putty or whatever on Windows), do you get a prompt to accept a key from the remote (linux) host, or do you need to install the key connection (copy and paste the string) manually before establishing an ssh session?

You might want to check if the key is registered within the NX client; 'General' tab, click 'Key'.

Do a search for FAQs on the subject. There are a lot of pieces that need to be configured...then it works beautifully! Take a look at this detailed one: http://madpenguin.org/cms/html/17/5755.html

knu2xs · 01-03-2006, 11:30 AM

The article you mention is the guide used for installation.

I opted for the "Basic Setup" method on page 2, which theoretically does not requre entering a key on the client machine. As part of troubleshooting, I did also attempt to connecet using this method, with no success. Just to make sure, I completely uninstalled both sides and started over including purging all files.

I am completely at a loss. Truthfully I don't even know what to do next or even where to look. Usually I at least get an idea from reading threads and help files. This one has me completely in the dark.

dasbooter · 01-06-2006, 04:00 PM

I had problems connecting with a computer that had Cygwin installed on it.Another system had no problem.
Also after uninstalling in the console and following the directive to remove the scripts and then reinstalling using yast I got a similiar error. I noticed that the nxagent script was not reinstalled.I did not actually delete the scripts only removed them so I replaced that one and was able to connect. Sorry if that doesnt help but these were my trials and tribulations.Sometimes it might be wise to completely shut down all firewalls server/client just to troubleshoot but you probably know that.

I would also like to add if anybody who is using the windows client also has problems resizing the window? I cant resize the window the session is drawn in and I get some really odd behaviour when resuming a session.