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