nxsetup Fatal error: Could not connect to NX Server.

[fogelfish]

I recently started – and with help, completed-- a thread about problems with “ssh localhost”. I can now do it. But I pursued that problem in the first place because I want to install freeNX. I still run up against the same problem in nxsetup, even though “ssh localhost” apparently is working.

Here is the complete output of

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

Removing special user “nx” …no crontab for nx
done
Removing session database …done
Removing logfile …done
Removing home directory of special user “nx” …done
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:
60:45:54:43:b9:8e:0b:8d:d6:fa:c3:d3:fc:20:71:d1 root@localhost
Setting up /var/lib/nxserver/db …done
Setting up /var/log/nxserver.log …done
Setting up special user “nx” …done
Adding user “nx” to group “utmp” …done
Setting up known_hosts and authorized_keys2 …done
Setting up permissions …done
Setting up cups nxipp backend …done

----> Testing your nxserver configuration …
Warning: Invalid value “COMMAND_FOOMATIC=/usr/lib64/cups/driver/foomatic-ppdfile”
Users will not be able to use foomatic.
Warning: Invalid value “COMMAND_START_GNOME=gnome-session”
Users will not be able to request a Gnome session.
Warning: Invalid value “COMMAND_START_CDE=cdwm”
Users will not be able to request a CDE session.
Warning: Invalid value “COMMAND_SMBMOUNT=smbmount”. You’ll not be able to use SAMBA.
Warning: Invalid value “COMMAND_SMBUMOUNT=smbumount”. You’ll not be able to use SAMBA.

Warnings occured during config check.
To enable these features please correct the configuration file.

<---- done

----> Testing your nxserver connection …
Permission denied (publickey,password,keyboard-interactive).
Fatal error: Could not connect to NX Server.

Please check your ssh setup:

The following are examples of what you might need to check.

    - Make sure "nx" is one of the AllowUsers in sshd_config.
(or that the line is outcommented/not there)
    - Make sure "nx" is one of the AllowGroups in sshd_config.
(or that the line is outcommented/not there)
    - Make sure your sshd allows public key authentication.
    - Make sure your sshd is really running on port 22.
    - Make sure your sshd_config AuthorizedKeysFile in sshd_config is set to authorized_keys2.
(this should be a filename not a pathname+filename)

• Make sure you allow ssh on localhost, this could come from some
  restriction of:
  -the tcp wrapper. Then add in /etc/hosts.allow: ALL:localhost
  -the iptables. add to it:
  $ iptables -A INPUT -i lo -j ACCEPT
  $ iptables -A OUTPUT -o lo -j ACCEPT

I am told to “Please check your ssh setup” and I have.

Here are UNCOMMENTED lines in sshd_config (and I show the OUTCOMMENTED AllowUsers and AllowGroups lines for good measure):

Port 22
ListenAddress 0.0.0.0
Protocol 2

HostKey /etc/ssh/ssh_host_key

HostKeys for protocol version 2

HostKey /etc/ssh/ssh_host_rsa_key
HostKey /etc/ssh/ssh_host_dsa_key

PubkeyAuthentication yes
AuthorizedKeysFile authorized_keys2

PasswordAuthentication yes
PermitEmptyPasswords no

RSAAuthentication yes
PubkeyAuthentication yes
AuthorizedKeysFile authorized_keys2

PasswordAuthentication yes
PermitEmptyPasswords no
ChallengeResponseAuthentication yes

UsePAM yes

Subsystem sftp /usr/lib64/ssh/sftp-server

AcceptEnv LANG LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE LC_MONETARY LC_MESSAGES
AcceptEnv LC_PAPER LC_NAME LC_ADDRESS LC_TELEPHONE LC_MEASUREMENT
AcceptEnv LC_IDENTIFICATION LC_ALL

#AllowUsers nx
#AllowGroups remotessh nx

GatewayPorts yes
X11DisplayOffset 50
AllowTcpForwarding yes
Compression yes
MaxAuthTries 6
PermitRootLogin yes
PrintMotd yes

Here is the bottom of /etc/hosts.allow:

ALL:localhost
ALL:127.0.0.1

added per Linux Help - Secure Shell SSH/SSH2 Setup Guide

sshd: ALL
sshdfwd-X11: 192.168.1.35

added this for nx

$ iptables -A INPUT -i lo -j ACCEPT
$ iptables -A OUTPUT -o lo -j ACCEPT

Is there a way I can debug the error occuring in nxsetup?

[user]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I’d start with /var/log/messages to see what happened when SSH tried to
bind.

Good luck.

fogelfish wrote:
| I recently started – and with help, completed-- a thread about problems
| with “ssh localhost”. I can now do it. But I pursued that problem in
| the first place because I want to install freeNX. I still run up
| against the same problem in nxsetup, even though “ssh localhost”
| apparently is working.
|
| Here is the complete output of> nxsetup --install

• –setup-nomachine-key --clean --purge
  |> Removing special user “nx” …no crontab for nx
  |> done
  |> Removing session database …done
  |> Removing logfile …done
  |> Removing home directory of special user “nx” …done
  |> 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:
  |> 60:45:54:43:b9:8e:0b:8d:d6:fa:c3:d3:fc:20:71:d1 root@localhost
  |> Setting up /var/lib/nxserver/db …done
  |> Setting up /var/log/nxserver.log …done
  |> Setting up special user “nx” …done
  |> Adding user “nx” to group “utmp” …done
  |> Setting up known_hosts and authorized_keys2 …done
  |> Setting up permissions …done
  |> Setting up cups nxipp backend …done
  |>
  |> ----> Testing your nxserver configuration …
  |> Warning: Invalid value
  |> “COMMAND_FOOMATIC=/usr/lib64/cups/driver/foomatic-ppdfile”
  |> Users will not be able to use foomatic.
  |> Warning: Invalid value “COMMAND_START_GNOME=gnome-session”
  |> Users will not be able to request a Gnome session.
  |> Warning: Invalid value “COMMAND_START_CDE=cdwm”
  |> Users will not be able to request a CDE session.
  |> Warning: Invalid value “COMMAND_SMBMOUNT=smbmount”. You’ll not be able
  |> to use SAMBA.
  |> Warning: Invalid value “COMMAND_SMBUMOUNT=smbumount”. You’ll not be
  |> able to use SAMBA.
  |>
  |> Warnings occured during config check.
  |> To enable these features please correct the configuration file.
  |>
  |> <---- done
  |>
  |> ----> Testing your nxserver connection …
  |> Permission denied (publickey,password,keyboard-interactive).
  |> Fatal error: Could not connect to NX Server.
  |>
  |> Please check your ssh setup:
  |>
  |> The following are examples of what you might need to check.
  |>
  |> - Make sure “nx” is one of the AllowUsers in sshd_config.
  |> (or that the line is outcommented/not there)
  |> - Make sure “nx” is one of the AllowGroups in sshd_config.
  |> (or that the line is outcommented/not there)
  |> - Make sure your sshd allows public key authentication.
  |> - Make sure your sshd is really running on port 22.
  |> - Make sure your sshd_config AuthorizedKeysFile in sshd_config
  |> is set to authorized_keys2.
  |> (this should be a filename not a pathname+filename)
  |> - Make sure you allow ssh on localhost, this could come from some
  |> restriction of:
  |> -the tcp wrapper. Then add in /etc/hosts.allow: ALL:localhost
  |> -the iptables. add to it:
  |> $ iptables -A INPUT -i lo -j ACCEPT
  |> $ iptables -A OUTPUT -o lo -j ACCEPT
  | I am told to “Please check your ssh setup” and I have.
  |
  | Here are UNCOMMENTED lines in sshd_config (and I show the OUTCOMMENTED
  | AllowUsers and AllowGroups lines for good measure):
  |
  |> Port 22
  |> ListenAddress 0.0.0.0
  |> Protocol 2
  |>
  |> HostKey /etc/ssh/ssh_host_key
  |> # HostKeys for protocol version 2
  |> HostKey /etc/ssh/ssh_host_rsa_key
  |> HostKey /etc/ssh/ssh_host_dsa_key
  |>
  |> PubkeyAuthentication yes
  |> AuthorizedKeysFile authorized_keys2
  |>
  |> PasswordAuthentication yes
  |> PermitEmptyPasswords no
  |>
  |> RSAAuthentication yes
  |> PubkeyAuthentication yes
  |> AuthorizedKeysFile authorized_keys2
  |>
  |> PasswordAuthentication yes
  |> PermitEmptyPasswords no
  |> ChallengeResponseAuthentication yes
  |>
  |> UsePAM yes
  |>
  |> Subsystem sftp /usr/lib64/ssh/sftp-server
  |>
  |> AcceptEnv LANG LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE LC_MONETARY
  |> LC_MESSAGES
  |> AcceptEnv LC_PAPER LC_NAME LC_ADDRESS LC_TELEPHONE LC_MEASUREMENT
  |> AcceptEnv LC_IDENTIFICATION LC_ALL
  |>
  |> #AllowUsers nx
  |> #AllowGroups remotessh nx
  |>
  |> GatewayPorts yes
  |> X11DisplayOffset 50
  |> AllowTcpForwarding yes
  |> Compression yes
  |> MaxAuthTries 6
  |> PermitRootLogin yes
  |> PrintMotd yes
  |>
  |
  | Here is the bottom of /etc/hosts.allow:
  |> ALL:localhost
  |> ALL:127.0.0.1
  |>
  |> # added per ‘Linux Help - Secure Shell SSH/SSH2 Setup Guide’
  |> (http://www.linuxhelp.net/guides/ssh/)
  |> sshd: ALL
  |> sshdfwd-X11: 192.168.1.35
  |>
  |> # added this for nx
  |> $ iptables -A INPUT -i lo -j ACCEPT
  |> $ iptables -A OUTPUT -o lo -j ACCEPT
  |>
  | Is there a way I can debug the error occuring in nxsetup?
  |
  |
  -----BEGIN PGP SIGNATURE-----
  Version: GnuPG v1.4.2 (GNU/Linux)
  Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIoNrf3s42bA80+9kRAsczAJ0bkeBQcZRIcsp31giCiJJsVrdBFgCfZi/4
8fFno8SAZxxHMmwNYZwJ6jA=
=U5Wx
-----END PGP SIGNATURE-----

[user]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Oh, also, if ‘nxsetup’ is a shell script of some sort that will be
executed by bash, try the following:

bash -x ./nxsetup

Get ready for a lot of data.

Good luck.

ab@novell.com wrote:
| I’d start with /var/log/messages to see what happened when SSH tried to
| bind.
|
| Good luck.
|
|
|
|
|
|
| fogelfish wrote:
| | I recently started – and with help, completed-- a thread about problems
| | with “ssh localhost”. I can now do it. But I pursued that problem in
| | the first place because I want to install freeNX. I still run up
| | against the same problem in nxsetup, even though “ssh localhost”
| | apparently is working.
| |
| | Here is the complete output of> nxsetup --install
| --setup-nomachine-key --clean --purge
| |> Removing special user “nx” …no crontab for nx
| |> done
| |> Removing session database …done
| |> Removing logfile …done
| |> Removing home directory of special user “nx” …done
| |> 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:
| |> 60:45:54:43:b9:8e:0b:8d:d6:fa:c3:d3:fc:20:71:d1 root@localhost
| |> Setting up /var/lib/nxserver/db …done
| |> Setting up /var/log/nxserver.log …done
| |> Setting up special user “nx” …done
| |> Adding user “nx” to group “utmp” …done
| |> Setting up known_hosts and authorized_keys2 …done
| |> Setting up permissions …done
| |> Setting up cups nxipp backend …done
| |>
| |> ----> Testing your nxserver configuration …
| |> Warning: Invalid value
| |> “COMMAND_FOOMATIC=/usr/lib64/cups/driver/foomatic-ppdfile”
| |> Users will not be able to use foomatic.
| |> Warning: Invalid value “COMMAND_START_GNOME=gnome-session”
| |> Users will not be able to request a Gnome session.
| |> Warning: Invalid value “COMMAND_START_CDE=cdwm”
| |> Users will not be able to request a CDE session.
| |> Warning: Invalid value “COMMAND_SMBMOUNT=smbmount”. You’ll not be able
| |> to use SAMBA.
| |> Warning: Invalid value “COMMAND_SMBUMOUNT=smbumount”. You’ll not be
| |> able to use SAMBA.
| |>
| |> Warnings occured during config check.
| |> To enable these features please correct the configuration file.
| |>
| |> <---- done
| |>
| |> ----> Testing your nxserver connection …
| |> Permission denied (publickey,password,keyboard-interactive).
| |> Fatal error: Could not connect to NX Server.
| |>
| |> Please check your ssh setup:
| |>
| |> The following are examples of what you might need to check.
| |>
| |> - Make sure “nx” is one of the AllowUsers in sshd_config.
| |> (or that the line is outcommented/not there)
| |> - Make sure “nx” is one of the AllowGroups in sshd_config.
| |> (or that the line is outcommented/not there)
| |> - Make sure your sshd allows public key authentication.
| |> - Make sure your sshd is really running on port 22.
| |> - Make sure your sshd_config AuthorizedKeysFile in sshd_config
| |> is set to authorized_keys2.
| |> (this should be a filename not a pathname+filename)
| |> - Make sure you allow ssh on localhost, this could come from some
| |> restriction of:
| |> -the tcp wrapper. Then add in /etc/hosts.allow: ALL:localhost
| |> -the iptables. add to it:
| |> $ iptables -A INPUT -i lo -j ACCEPT
| |> $ iptables -A OUTPUT -o lo -j ACCEPT
| | I am told to “Please check your ssh setup” and I have.
| |
| | Here are UNCOMMENTED lines in sshd_config (and I show the OUTCOMMENTED
| | AllowUsers and AllowGroups lines for good measure):
| |
| |> Port 22
| |> ListenAddress 0.0.0.0
| |> Protocol 2
| |>
| |> HostKey /etc/ssh/ssh_host_key
| |> # HostKeys for protocol version 2
| |> HostKey /etc/ssh/ssh_host_rsa_key
| |> HostKey /etc/ssh/ssh_host_dsa_key
| |>
| |> PubkeyAuthentication yes
| |> AuthorizedKeysFile authorized_keys2
| |>
| |> PasswordAuthentication yes
| |> PermitEmptyPasswords no
| |>
| |> RSAAuthentication yes
| |> PubkeyAuthentication yes
| |> AuthorizedKeysFile authorized_keys2
| |>
| |> PasswordAuthentication yes
| |> PermitEmptyPasswords no
| |> ChallengeResponseAuthentication yes
| |>
| |> UsePAM yes
| |>
| |> Subsystem sftp /usr/lib64/ssh/sftp-server
| |>
| |> AcceptEnv LANG LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE LC_MONETARY
| |> LC_MESSAGES
| |> AcceptEnv LC_PAPER LC_NAME LC_ADDRESS LC_TELEPHONE LC_MEASUREMENT
| |> AcceptEnv LC_IDENTIFICATION LC_ALL
| |>
| |> #AllowUsers nx
| |> #AllowGroups remotessh nx
| |>
| |> GatewayPorts yes
| |> X11DisplayOffset 50
| |> AllowTcpForwarding yes
| |> Compression yes
| |> MaxAuthTries 6
| |> PermitRootLogin yes
| |> PrintMotd yes
| |>
| |
| | Here is the bottom of /etc/hosts.allow:
| |> ALL:localhost
| |> ALL:127.0.0.1
| |>
| |> # added per ‘Linux Help - Secure Shell SSH/SSH2 Setup Guide’
| |> (http://www.linuxhelp.net/guides/ssh/)
| |> sshd: ALL
| |> sshdfwd-X11: 192.168.1.35
| |>
| |> # added this for nx
| |> $ iptables -A INPUT -i lo -j ACCEPT
| |> $ iptables -A OUTPUT -o lo -j ACCEPT
| |>
| | Is there a way I can debug the error occuring in nxsetup?
| |
| |
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIoNsG3s42bA80+9kRAk+jAJ0VdhoN/QiK+vXUOErmowDujc8zEACeKKYj
ZTTeu4DGxR54S9DP1FRlZZY=
=vwkb
-----END PGP SIGNATURE-----

[lornix]

fogelfish wrote:

>>
>> Setting up known_hosts and authorized_keys2 …done
>>
>> ----> Testing your nxserver connection …
>> Permission denied (publickey,password,keyboard-interactive).
>> Fatal error: Could not connect to NX Server.
>>
>> AuthorizedKeysFile authorized_keys2
>>

Hey! I know you! {Grin}

From my experiences with freenx, I found that the ‘unable to connect’ error
is caused by the fact that nxsetup creates a ‘authorized_keys2’ file, while
the sshd server USUALLY has an ‘authorized_keys’ file as default. I know
that you’ve adjusted the sshd_config file (shown above), but I found that
symlinking the nx user’s authorized_keys2 file to authorized_keys in the nx
user home directory (/var/lib/nxserver. I think, something like that
really), fixed the problem.

If you changed or edited the sshd_config file, you need to restart the sshd
server to reflect the new configuration options.

(as root)
rcsshd restart

MIGHT fix the authorized_keys2 issue since you show that the sshd_config
file has been changed to reflect the new name (_keys2 vs _keys)

To find the authorized_keys2 file that the nxsetup script created, look at
the users list (in yast-> users) to see what the ‘nx’ users home directory
is. Usually it’s /var/lib or /var/share something. I forget exactly.

As root, cd to that subdir, then to .ssh subdir. You should see the
authorized_keys2 file. Type this:

ln authorized_keys2 authorized_keys

which will create a HARD link between the two files. Essentially, they
become the exact same info, just two different names for it.

After doing this, I was able to start and use the freenx system.

Realize that this is all from memory from my last foray into freenx. Yes, I
tinker with everything, trying it all. I got it working, played with it,
thought it was cool, and then moved on to other things…

Hope this helps.

Loni

L R Nix
lornix@lornix.com

[fogelfish]

Yes, I’m back and so soon!

There was no ‘nx’ user displayed in Yast - User and Group Management, but I was able to locate the ‘nx’ user’s home from reading ‘/var/log/messages’. Here’s the relevant extract:

Aug 11 22:44:43 linuxos useradd[26859]: new account added - account=nx, uid=107, gid=1000, home=/var/lib/nxserver/home, shell=/usr/bin/nxserver, by=0
Aug 11 22:44:43 linuxos useradd[26859]: running USERADD_CMD command - script=/usr/sbin/useradd.local, account=nx, uid=107, gid=1000, home=/var/lib/nxserver/home, by=0
Aug 11 22:44:43 linuxos shadow[26862]: account added to group - account=nx, group=utmp, gid=22, by=0

There were three files in ‘/var/lib/nxserver/home/.ssh’:

-rw------- 2 nx root 669 Aug 11 22:44 authorized_keys2
-rw------- 1 nx root 668 Aug 11 22:44 client.id_dsa.key
-rw-r–r-- 1 nx root 235 Aug 11 22:44 known_hosts

I took your suggestion literally. As root I entered:

ln authorized_keys2 authorized_keys

But I’m not sure I understood your instructions correctly. Would you explain this in linux baby-ese?

Was the intent to create a link between root’s authorized_keys and the nx user’s authorized_keys? Or, why would I make a link to authorized_keys from authorized_keys2 in the nx home if ssh_config calls for authorized_keys2. Please enjoy a laugh if my questions are silly.

And in case this info is of use, root has these files in ‘/.ssh’:

-rw------- 1 root root 1743 2008-08-07 02:15 id_rsa
-rw-r–r-- 1 root root 396 2008-08-07 02:15 id_rsa.pub
-rw-r–r-- 1 root root 438 2008-08-07 01:46 known_hosts

I wanted to get down this response before I try ‘bash -x ./nxsetup’ per Ab’s suggestion.

One other thing: you say you moved on to other things. My aim is to have a functioning and decent remote desktop and I don’t care which one it is. Can you suggest another, even a commercial implementation, that is proven to work in SuSE 11?

[fogelfish]

I ran ‘bash -x nxsetup --test’.

Of interest are these lines:

++ NX_HOME_DIR=/var/lib/nxserver/home
…
++ SSH_AUTHORIZED_KEYS=authorized_keys2
…
++ NODE_PUBLICKEY=/var/lib/nxserver/home/.ssh/client.id_dsa.key
++ /usr/bin/nxnode-login test-nx nx 22 nxserver --check

• read -t 3 line
  ’ echo Permission denied '(publickey,password,keyboard-interactive).

And:

++ ENABLE_SERVER_FORWARD=0
++ SERVER_FORWARD_HOST=
++ SERVER_FORWARD_PORT=22
++ SERVER_FORWARD_KEY=/usr/NX/share/client.id_dsa.key

The first quote shows important variables and the locus of the failure.

I’m not sure if the second quote is important. I don’t know what the SERVER_FORWARD_HOST is, or if it matters that it is undefined, or whether it is important that SERVER_FORWARD_KEY points to a non-existent file (there is no such thing as ‘client.id_dsa.key’ in ‘/usr/NX/share/’), but I mention this in case it is important to those who know better.

linuxos:/usr/NX/share # ls -al

total 72
drwxr-xr-x 12 root root 4096 2008-06-12 03:17 .
drwxr-xr-x 9 root root 4096 2008-08-11 10:38 …
drwxr-xr-x 4 root root 4096 2008-06-12 03:17 branding
drwxr-xr-x 3 brian nx 4096 2008-08-11 22:41 config
drwxr-xr-x 2 root root 4096 2007-05-28 06:26 cups
drwxr-xr-x 5 root root 4096 2008-06-12 03:17 documents
drwxr-xr-x 2 brian nx 4096 2007-06-19 11:02 fonts
drwxr-xr-x 6 root root 4096 2007-06-02 05:14 icons
drwxr-xr-x 2 root root 4096 2008-06-12 03:17 images
-rw-r–r-- 1 root root 1861 2008-01-22 09:50 keyboards
drwxr-xr-x 2 brian nx 4096 2007-06-19 11:02 keymaps
drwxr-xr-x 2 root root 4096 2008-06-24 03:44 keymaps-windows
drwxr-xr-x 2 root root 4096 2007-05-28 06:26 keys
-rw-r–r-- 1 root root 18124 2007-05-28 06:26 rgb

And ‘linuxos:/usr/NX/share/keys # ls -al’

total 12
drwxr-xr-x 2 root root 4096 2007-05-28 06:26 .
drwxr-xr-x 12 root root 4096 2008-06-12 03:17 …
-rw-r–r-- 1 root root 668 2007-05-28 06:26 server.id_dsa.key

Do these two lines hint at the cause of the failure?

++ /usr/bin/nxnode-login test-nx nx 22 nxserver --check

• read -t 3 line

[lornix]

fogelfish wrote:

>
> I ran ‘bash -x nxsetup --test’.
>
> Of interest are these lines:
>> ++ NX_HOME_DIR=/var/lib/nxserver/home
>> …
>> ++ SSH_AUTHORIZED_KEYS=authorized_keys2
>> …
>> ++ NODE_PUBLICKEY=/var/lib/nxserver/home/.ssh/client.id_dsa.key
>> ++ /usr/bin/nxnode-login test-nx nx 22 nxserver --check
>> + read -t 3 line
>> ’ echo Permission denied '(publickey,password,keyboard-interactive).
> And:
>> ++ ENABLE_SERVER_FORWARD=0
>> ++ SERVER_FORWARD_HOST=
>> ++ SERVER_FORWARD_PORT=22
>> ++ SERVER_FORWARD_KEY=/usr/NX/share/client.id_dsa.key
>>
> The first quote shows important variables and the locus of the failure.
>
>
> I’m not sure if the second quote is important. I don’t know what the
> SERVER_FORWARD_HOST is, or if it matters that it is undefined, or
> whether it is important that SERVER_FORWARD_KEY points to a
> non-existent file (there is no such thing as ‘client.id_dsa.key’ in
> ‘/usr/NX/share/’), but I mention this in case it is important to those
> who know better.
>
> linuxos:/usr/NX/share # ls -al
>> total 72
>> drwxr-xr-x 12 root root 4096 2008-06-12 03:17 .
>> drwxr-xr-x 9 root root 4096 2008-08-11 10:38 …
>> drwxr-xr-x 4 root root 4096 2008-06-12 03:17 branding
>> drwxr-xr-x 3 brian nx 4096 2008-08-11 22:41 config
>> drwxr-xr-x 2 root root 4096 2007-05-28 06:26 cups
>> drwxr-xr-x 5 root root 4096 2008-06-12 03:17 documents
>> drwxr-xr-x 2 brian nx 4096 2007-06-19 11:02 fonts
>> drwxr-xr-x 6 root root 4096 2007-06-02 05:14 icons
>> drwxr-xr-x 2 root root 4096 2008-06-12 03:17 images
>> -rw-r–r-- 1 root root 1861 2008-01-22 09:50 keyboards
>> drwxr-xr-x 2 brian nx 4096 2007-06-19 11:02 keymaps
>> drwxr-xr-x 2 root root 4096 2008-06-24 03:44 keymaps-windows
>> drwxr-xr-x 2 root root 4096 2007-05-28 06:26 keys
>> -rw-r–r-- 1 root root 18124 2007-05-28 06:26 rgb
>
> And ‘linuxos:/usr/NX/share/keys # ls -al’
>> total 12
>> drwxr-xr-x 2 root root 4096 2007-05-28 06:26 .
>> drwxr-xr-x 12 root root 4096 2008-06-12 03:17 …
>> -rw-r–r-- 1 root root 668 2007-05-28 06:26 server.id_dsa.key
> Do these two lines hint at the cause of the failure?
>> ++ /usr/bin/nxnode-login test-nx nx 22 nxserver --check
>> + read -t 3 line
>>
>
>

To address your previous post, Are you connecting from one linux box to
another linux box? If so, you can log in to another machine remotely by
clicking on ‘system’ (bottom left), then ‘remote login’ (or whatever it’s
called), then either scan for, or provide the ipaddress/name of the desired
machine. click ok, then log in as if you were sitting in front of other
machine. Uses normal X11 forwarding.

FreeNX was nice, but a pain to install. I looked for quite a while
for “simple installation guide”, but everything seemed to say “omg! this is
a hard!”. I did get it working, but the overhead to get it to that point
was more than I wanted to spend to get it going on the various machines I
play with.

The installer creates and expects you to use ‘authorized_keys2’, which was
the typical name for ssh protocol 2 key storage long ago. Protocol 1 has
become non-standard due to some issues and protocol 2 has become the
new ‘norm’… so all of a sudden, everything puts authorized keys
into ‘authorized_keys’ instead of ‘_keys2’. At least on every distro I’ve
played with in the last few years.

The ‘ln authorized_keys2 authorized_keys’ command just makes it so that the
keys are accessible through either filename. I believe that a daemon’s
defaults are set for a reason, and see no need to change sshd’s defaults
for a third party program (freenx). which means that freenx should change
to reflect the current defaults of the time. grrr!

Dunno, I’m no slouch when it comes to making things work, but the
documentation is spotty and fractured, the installation script makes
assumptions that I cannot easily adjust, and it was just plain annoying how
it refused to work unless the stars and planets were perfectly aligned.

Now, once you get it configured… holy cow! FreeNX was great! Insane
speeds over slow links! wow! love it! But I used to administer more than
20 systems remotely… my desire to repeat the installation of freenx 20
times was very very low.

Nowadays, I just ssh into a system, making sure that X11Forwarding is
enabled in the sshd config, or use the -X option on ssh to temporarily
enable it as needed.

This works very well, is almost global in availability, as it already exists
by default, and works very well, although it can be slow at times.

I sometimes use VNC too, but usually only if I need to talk to windows or
mac machines since they don’t support the X11 forwarding themselves.

Don’t get me wrong, I’m not saying that FreeNX sucks… not at all!! I
think it’s a fantastic application and implementation of a concept. I
simply do not like the convoluted mess the install seems to involve.

It should be…

1. zypper install freenx
2. ./nxsetup -option1 -option2 -etc
3. add users to ‘valid nx users list/group’
4. enjoy amazing remote speed from other machine!

It’s just that somewhere between steps 2 and 3… it doesn’t work like that.

I might take some time and revisit the freenx application… and write down
what I did to install it and get it working… might help others… but for
now, I have no pressing need and the ssh X11Forwarding works very well for
me.

I tend to mostly run apps from other machines to display locally, rather
than do a complete log in to a remote machine. There’s a difference, and
making FreeNX work for the individual application, which I prefer, is not
trivial.

Guess I should install FreeNX now if I want to help you, right?

Loni

–
L R Nix
lornix@lornix.com

[greenmachine]

Guess I should install FreeNX now if I want to help you, right?

I would like that very much as well. The info found here:
FreeNX Server HOWTO - openSUSE

needs to be a little more in depth for the likes of me. If you or someone can be very specific with each step of the way in getting NX to work, I would be very appreciative.

Thanks,
g

[lornix]

greenmachine wrote:

>
>> Guess I should install FreeNX now if I want to help you, right?
>
> I would like that very much as well. The info found here:
> ‘FreeNX Server HOWTO - openSUSE’
> (http://en.opensuse.org/FreeNX_Server_HOWTO)
>
> needs to be a little more in depth for the likes of me. If you or
> someone can be very specific with each step of the way in getting NX to
> work, I would be very appreciative.
>
> Thanks,
> g
>
>

Hmmm, well ok… since you asked so nicely. I respectfully request a little
while to try things out and compile notes… maybe I can find my old notes
too… I tend to lose things, I once misplaced an 80GB hard drive image one
day… 2.2 TB of storage on my main machine… 80GB is a drop in the
bucket!! (and a few kilobyte text file… I’ll never find it!)

Off to play! {Grin}

Loni

–
L R Nix
lornix@lornix.com

[fogelfish]

Off to play! {Grin}

Thank you, man, from myself and on behalf of hundreds like me the world over!

[fogelfish]

I was planning to connect from Mac/Windows to Linux, but I may have to change that plan and connect Linux to Linux using X11 Forwarding.

I noticed the noMachine website has rpm’s for SuSE 10/10.1/10.2/10.3. Maybe they will develop rpm’s for 11.0. (Should I assume that installation would go better from one of their rpm’s?)

[malcolmlewis]

@fogelfish

> Off to play! {Grin}
Thank you, man, from myself and on behalf of hundreds like me the world
over!

Hi
Just to jump in here, if all else fails why not try the actual NX from
nomachine… it is free

–
Cheers Malcolm °¿° (Linux Counter #276890)
openSUSE 11.0 x86 Kernel 2.6.25.11-0.1-default
up 3:14, 1 user, load average: 0.12, 0.09, 0.09
GPU GeForce 6600 TE/6200 TE - Driver Version: 173.14.12

[malcolmlewis]

@fogelfish

I was planning to connect from Mac/Windows to Linux, but I may have to
change that plan and connect Linux to Linux using X11 Forwarding.

I noticed the noMachine website has rpm’s for SuSE 10/10.1/10.2/10.3.
Maybe they will develop rpm’s for 11.0. (Should I assume that
installation would go better from one of their rpm’s?)

Hi
The 10.3 rpms install fine, you could always install from the tarball
anyway

–
Cheers Malcolm °¿° (Linux Counter #276890)
openSUSE 11.0 x86 Kernel 2.6.25.11-0.1-default
up 3:21, 2 users, load average: 0.75, 0.33, 0.18
GPU GeForce 6600 TE/6200 TE - Driver Version: 173.14.12

[fogelfish]

The 10.3 rpms install fine, you could always install from the tarball anyway

I didn’t want to try NoMachine without knowing it worked on 11.0. So it would be worth a go.

First, would uninstalling the rpm’s (in Yast - Software Management) be sufficient, or do you recommend further steps to wipe all traces of freeNX from my system before trying NoMachine’s tarball?

[malcolmlewis]

@fogelfish

> The 10.3 rpms install fine, you could always install from the tarball
> anyway
I didn’t want to try NoMachine without knowing it worked on 11.0. So
it would be worth a go.

First, would uninstalling the rpm’s (in Yast - Software Management) be
sufficient, or do you recommend further steps to wipe all traces of
freeNX from my system before trying NoMachine’s tarball?

Hi
I use it from this machine to connect to Solaris and SLED systems
fine

I would remove the other rpms then install via rpm -Uhv
<name_of_rpm> Remember it’s client->node->server.

Any reason for the tarball?

–
Cheers Malcolm °¿° (Linux Counter #276890)
openSUSE 11.0 x86 Kernel 2.6.25.11-0.1-default
up 4:41, 1 user, load average: 0.74, 0.49, 0.25
GPU GeForce 6600 TE/6200 TE - Driver Version: 173.14.12

[lornix]

Malcolm wrote:

>

@fogelfish

>> Off to play! {Grin}
> Thank you, man, from myself and on behalf of hundreds like me the world
> over!
>

> Hi
> Just to jump in here, if all else fails why not try the actual NX from
> nomachine… it is free
>

I’ll pull that one and see how it installs / works too… it’s like Pokemon!
Gotta try them all!!

And it’s ma’am, actually.

Loni

–
L R Nix
lornix@lornix.com

[fogelfish]

My apologies. Thank you, ma’am!

[fogelfish]

Malcolm, I have installed NoMachine client-node-server using rpm’s. I installed the client on my Mac. The connection fails at the point of checking the key.

I don’t know if this is an appopriate place to continue this discussion, but I’ll start just to indicate my problem: there is no mention in documentation I have found of having to run nxsetup or anything like that (which I had to do with freeNX). I don’t know how to generate the default keys.

Also in the /usr/NX/etc directory there are only sample files, such as ‘server-suse.cfg.sample’. I can find no mention in the documentation of copying that to ‘server.cfg’. There are none of the following as well: ‘administrators.db’, ‘guests.db’, ‘nodes.db’, ‘passwords.db’, ‘profiles.db’ and ‘users.db’.

Since you got NoMachine to work on your system could you tell me steps I am missing?

[malcolmlewis]

@fogelfish

Malcolm, I have installed NoMachine client-node-server using rpm’s. I
installed the client on my Mac. The connection fails at the point of
checking the key.

I don’t know if this is an appopriate place to continue this
discussion, but I’ll start just to indicate my problem: there is no
mention in documentation I have found of having to run nxsetup or
anything like that (which I had to do with freeNX). I don’t know how
to generate the default keys.

Also in the /usr/NX/etc directory there are only sample files, such as
‘server-suse.cfg.sample’. I can find no mention in the documentation
of copying that to ‘server.cfg’. There are none of the following as
well: ‘administrators.db’, ‘guests.db’, ‘nodes.db’, ‘passwords.db’,
‘profiles.db’ and ‘users.db’.

Since you got NoMachine to work on your system could you tell me steps
I am missing?

Hi
It just works… On the client machine you need to delete any ssh keys
for the server you have cached from previous attempts/installs. Have no
idea where they are kept on a Mac…

Server, install client, node then server, ensure ssh port is
open in firewall…done

Client, install client, connect…done?

–
Cheers Malcolm °¿° (Linux Counter #276890)
openSUSE 11.0 x86 Kernel 2.6.25.11-0.1-default
up 11:07, 1 user, load average: 0.28, 0.17, 0.12
GPU GeForce 6600 TE/6200 TE - Driver Version: 173.14.12