[prev in list] [next in list] [prev in thread] [next in thread]
List: freenx-knx
Subject: [FreeNX-kNX] The NX client does nothing
From: "Nowhereman Absent" <nowhereman.sme () gmail ! com>
Date: 2006-05-29 10:40:22
Message-ID: 866ca8e20605290340s578003f8vd927b740f464291c () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
[Attachment #4 (text/plain)]
Hi,
(Please respond also to nowhereman.sme@gmail.com as I'm not on the list..)
I have tried freenx server on coLinux (running inside W2k) with Debian
Sarge. I have configured everything ok (I think), also run the nxsetup:
colinux:~# nxsetup
------> You did select no action.
FreeNX guesses that you want to _install_ the server.
Type "y" to abort the installation at this point in time.
"N" is the default and continues installation.
Use "/usr/sbin/nxsetup --help" to get more detailed help hints.
Do you want to abort now? [y/N]
------> It is recommended that you use the NoMachine key for
easier setup. If you answer "y", FreeNX creates a custom
KeyPair and expects you to setup your clients manually.
"N" is default and uses the NoMachine key for installation.
Do you want to use your own custom KeyPair? [y/N]
Setting up /etc/nxserver ...done
Setting up /var/lib/nxserver/db ...done
Setting up /var/log/nxserver.log ...done
Setting up known_hosts and authorized_keys2 ...done
Setting up permissions ...done
----> Testing your nxserver configuration ...
Warning: Could not find nxdesktop in /usr/lib/nx. RDP sessions won't work.
Warning: Could not find nxviewer in /usr/lib/nx. VNC sessions won't work.
Warning: Invalid value "CUPS_ETC=/etc/cups/"
Users will not be able to enable printing.
Warning: Invalid value "DEFAULT_X_SESSION=/etc/X11/xdm/Xsession"
Users might not be able to request a default X session.
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.
Warning: Invalid value "COMMAND_CUPSD=/usr/sbin/cupsd"
Users will not be able to enable printing.
Warnings occured during config check.
To enable these features please correct the configuration file.
<---- done
----> Testing your nxserver connection ...
HELLO NXSERVER - Version 1.4.0-45-SVN OS (GPL)
NX> 105 quit
Quit
<--- done
Ok, nxserver is ready.
PAM authentication enabled:
All users will be able to login with their normal passwords.
PAM authentication will be done through SSH.
Please ensure that SSHD on localhost accepts password authentication.
You can change this behaviour in the /etc/nxserver/node.conf file.
Have Fun!
colinux:~# grep nx /etc/passwd
nx:x:103:106::/var/lib/nxserver/home:/usr/lib/nx/nxserver
colinux:~# nxserver --status
NX> 100 NXSERVER - Version 1.4.0-45-SVN OS (GPL)
NX> 110 NX Server is running
NX> 999 Bye
But when I'm trying to connect to the server (192.168.0.40), the windows
NoMachine NX client (192.168.0.1 - virtual interface) shows message "Setting
up the X environment" and nothing else happens. I can connect to the linux
installation via ssh no problem.. Neither tcpdump (on Linux side) nor
ethereal (on Windows) show _any_ ssh packets (on any interface) being sent
from the NX client??!
$ ssh 192.168.0.40
Password:
The sshd is listening on all the interfaces on standard port 22
colinux:~# netstat -tupan | grep ssh
tcp6 0 0 :::22 :::*
LISTEN 1800/sshd
colinux:~# iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
>ipconfig
Configuration IP de Windows 2000
Ethernet carte Connexion au réseau local 2 :
Suffixe DNS spéc. à la connexion. :
Adresse IP. . . . . . . . . . . . : 192.168.0.1
Masque de sous-réseau . . . . . . : 255.255.255.0
Passerelle par défaut . . . . . . : 155.208.108.101
Ethernet carte Connexion au réseau local :
Suffixe DNS spéc. à la connexion. :
Adresse IP. . . . . . . . . . . . : 155.208.108.101
Masque de sous-réseau . . . . . . : 255.255.255.0
Passerelle par défaut . . . . . . : 155.208.105.1
coLinux is reachable...
>ping 192.168.0.40
Envoi d'une requête 'ping' sur 192.168.0.40 avec 32 octets de données :
Réponse de 192.168.0.40 : octets=32 temps<10 ms TTL=64
Réponse de 192.168.0.40 : octets=32 temps<10 ms TTL=64
Réponse de 192.168.0.40 : octets=32 temps<10 ms TTL=64
Réponse de 192.168.0.40 : octets=32 temps<10 ms TTL=64
Statistiques Ping pour 192.168.0.40:
Paquets : envoyés = 4, reçus = 4, perdus = 0 (perte 0%),
Durée approximative des boucles en millisecondes :
minimum = 0ms, maximum = 0ms, moyenne = 0ms
Thanks
Marek
[Attachment #5 (text/html)]
Hi,<br><br>(Please respond also to <a \
href="mailto:nowhereman.sme@gmail.com">nowhereman.sme@gmail.com</a> as I'm not on the \
list..)<br>I have tried freenx server on coLinux (running inside W2k) with Debian \
Sarge. I have configured everything ok (I think), also run the nxsetup: \
<br><br>colinux:~# nxsetup <br>------> You did select no \
action.<br> FreeNX guesses that you want to \
_install_ the server.<br> Type \
"y" to abort the installation at this point in \
time.<br> "N" is the default and \
continues installation. <br> Use \
"/usr/sbin/nxsetup --help" to get more detailed help hints.<br><br> Do \
you want to abort now? [y/N] <br><br>------> It is recommended that you use the \
NoMachine key for<br> easier setup. If you \
answer "y", FreeNX creates a custom \
<br> KeyPair and expects you to setup your \
clients manually. <br> "N" is \
default and uses the NoMachine key for installation.<br><br> Do you want to use \
your own custom KeyPair? [y/N] <br>Setting up /etc/nxserver ...done <br>Setting up \
/var/lib/nxserver/db ...done<br>Setting up /var/log/nxserver.log ...done<br>Setting \
up known_hosts and authorized_keys2 ...done<br>Setting up permissions \
...done<br><br>----> Testing your nxserver configuration ... <br>Warning: Could \
not find nxdesktop in /usr/lib/nx. RDP sessions won't work.<br>Warning: Could not \
find nxviewer in /usr/lib/nx. VNC sessions won't work.<br>Warning: Invalid value \
"CUPS_ETC=/etc/cups/"<br> \
Users will not be able to enable printing. <br>Warning: Invalid value \
"DEFAULT_X_SESSION=/etc/X11/xdm/Xsession"<br> \
Users might not be able to request a default X session.<br>Warning: Invalid value \
"COMMAND_START_GNOME=gnome-session"<br> \
Users will not be able to request a \
Gnome session.<br>Warning: Invalid value \
"COMMAND_START_CDE=cdwm"<br> \
Users will not be able to request a CDE session.<br>Warning: Invalid value \
"COMMAND_SMBMOUNT=smbmount". You'll not be able to use SAMBA. <br>Warning: \
Invalid value "COMMAND_SMBUMOUNT=smbumount". You'll not be able to use \
SAMBA.<br>Warning: Invalid value \
"COMMAND_CUPSD=/usr/sbin/cupsd"<br> \
Users will not be able to enable printing. <br><br> Warnings occured during \
config check.<br> To enable these features please correct the configuration \
file.<br><br><---- done<br><br>----> Testing your nxserver connection \
...<br>HELLO NXSERVER - Version 1.4.0-45-SVN OS (GPL)<br>NX> 105 \
quit<br>Quit<br><--- done<br><br>Ok, nxserver is ready.<br><br>PAM authentication \
enabled:<br> All users will be able to login with their normal \
passwords.<br><br> PAM authentication will be done through SSH. <br> \
Please ensure that SSHD on localhost accepts password authentication.<br><br> \
You can change this behaviour in the /etc/nxserver/node.conf file.<br>Have \
Fun!<br><br>colinux:~# grep nx /etc/passwd<br><span style="background-color: rgb(255, \
153, 0);"> nx:x:103:106::/var/lib/nxserver/home:/usr/lib/nx/nxserver</span><br><br>colinux:~# \
nxserver --status<br>NX> 100 NXSERVER - Version 1.4.0-45-SVN OS (GPL)<br><span \
style="background-color: rgb(255, 153, 0);">NX> 110 NX Server is running \
</span><br>NX> 999 Bye<br><br><br>But when I'm trying to connect to the server (<a \
href="http://192.168.0.40">192.168.0.40</a>), the windows NoMachine NX client (<a \
href="http://192.168.0.1">192.168.0.1</a> - virtual interface) shows message \
"Setting up the X environment" and nothing else happens. I can connect to \
the linux installation via ssh no problem.. Neither tcpdump (on Linux side) nor \
ethereal (on Windows) show _any_ ssh packets (on any interface) being sent from the \
NX client??! <br><br><span style="background-color: rgb(255, 153, 0);">$ ssh <a \
href="http://192.168.0.40">192.168.0.40</a></span><br>Password: <br><br><br>The sshd \
is listening on all the interfaces on standard port 22<br><br>colinux:~# netstat \
-tupan | grep ssh <br>tcp6 \
0 0 \
:::22 \
:::* \
LISTEN 1800/sshd<br><br><span style="background-color: \
rgb(255, 153, 0);">colinux:~# iptables -L</span><br>Chain INPUT (policy \
ACCEPT)<br>target prot opt \
source \
destination <br><br>Chain FORWARD \
(policy ACCEPT)<br>target prot opt \
source \
destination <br><br>Chain OUTPUT \
(policy ACCEPT)<br>target prot opt \
source \
destination <br><br><br><span style="background-color: \
rgb(255, 153, 0);"> >ipconfig</span><br><br>Configuration IP de Windows \
2000<br><br>Ethernet carte Connexion au réseau local \
2 :<br><br> Suffixe DNS spéc. à la \
connexion. :<br> Adresse IP. . . . . . . . \
. . . . : <span style="background-color: rgb(255, 153, 0);"> <a \
href="http://192.168.0.1">192.168.0.1</a></span><br> \
Masque de sous-réseau . . . . . . : <a \
href="http://255.255.255.0">255.255.255.0</a><br> \
Passerelle par défaut . . . . . . : <a href="http://155.208.108.101"> \
155.208.108.101</a><br><br>Ethernet carte Connexion au réseau \
local :<br><br> Suffixe DNS spéc. à \
la connexion. :<br> Adresse IP. . . . . . . \
. . . . . : <a href="http://155.208.108.101">155.208.108.101</a><br> \
Masque de sous-réseau . . . . . . : <a \
href="http://255.255.255.0">255.255.255.0</a><br> \
Passerelle par défaut . . . . . . : <a \
href="http://155.208.105.1">155.208.105.1</a><br><br>coLinux is reachable...<br>
<span style="background-color: rgb(255, 153, 0);">>ping <a \
href="http://192.168.0.40">192.168.0.40</a></span><br> <br>
Envoi d'une requête 'ping' sur <a href="http://192.168.0.40">192.168.0.40</a> avec \
32 octets de données :<br> <br>
Réponse de <a href="http://192.168.0.40">192.168.0.40</a> : octets=32 \
temps<10 ms TTL=64<br> Réponse de <a \
href="http://192.168.0.40">192.168.0.40</a> : octets=32 temps<10 ms \
TTL=64<br> Réponse de <a href="http://192.168.0.40">192.168.0.40</a> : \
octets=32 temps<10 ms TTL=64<br> Réponse de <a \
href="http://192.168.0.40">192.168.0.40</a> : octets=32 temps<10 ms \
TTL=64<br> <br>
Statistiques Ping pour <a href="http://192.168.0.40">192.168.0.40</a>:<br>
Paquets : envoyés = 4, reçus = 4, perdus = 0 (perte \
0%),<br> Durée approximative des boucles en millisecondes :<br>
minimum = 0ms, maximum = 0ms, moyenne = \
0ms<br><br><br>Thanks<br>Marek<br>
________________________________________________________________
Were you helped on this list with your FreeNX problem?
Then please write up the solution in the FreeNX Wiki/FAQ:
http://openfacts.berlios.de/index-en.phtml?title=FreeNX_FAQ
Don't forget to check the NX Knowledge Base:
http://www.nomachine.com/kb/
________________________________________________________________
FreeNX-kNX mailing list --- FreeNX-kNX@kde.org
https://mail.kde.org/mailman/listinfo/freenx-knx
________________________________________________________________
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic