| Autor |
Nachricht |
|
|
Titel: NX-Server
 Verfasst am: 25.09.2006, 15:19 Uhr
|
|
Anmeldung: 07. Jun 2005
Beiträge: 252
|
|
Hi, ich brauche ein wenig Hilfe.
Ich habe nach der Anleitung aus dem Wiki einen ssh-Zugang auf einen Rechner realisiert - super geklappt.
Jetzt will ich ebenfalls den NX-Server konfigurieren nach der gleichen Anleitung. Allerdings sagt er nur Authentifikation failed!
Hier meine /etc/nxserver/node.conf:
# node.conf
#
# This file is provided by FreeNX. It should be placed either into
# /etc/nxserver/node.conf (FreeNX style) or /usr/NX/etc/node.conf
# (NoMachine NX style).
#
# It is mostly compatible with NoMachine node.conf. The most important
# difference is that no spaces are allowed when assigning values (eg
# "A=value" is allowed, "A = value" is NOT).
#
# This file is sourced by bash, so you can do some fancy stuff here if you
# want to, but be aware that it is sourced 3 times per connection. If you
# want autostart stuff, set NODE_AUTOSTART instead!
#
#
# You surely are aware that FreeNX is based on the fantastic results that
# the hard work by NoMachine.com has achieved. NoMachine.com released the
# core NX libraries under the GPL. The installation of these libs are the
# precondition for all FreeNX scripts to work. If you are installing this
# software with the help of one of the package management tools of your
# Linux distribution, you can assume that this dependency is taken care of
# by the tool.
#
# You have questions about the inner workings of the NX technology?
#
# Then you are recommended to first check out the rich and very detailed
# NoMachine documentation and their online Knowledge Base at
#
# http://www.nomachine.com/kb/
#
# Other sources of information are the NoMachine mailing lists
# (nxusers@nomachine.com and nxdevelopers@nomachine.com):
#
# http://www.nomachine.com/mailinglists.php
#
# The FreeNX (freenx-knx@kde.org) list is here:
#
# https://mail.kde.org/mailman/listinfo/freenx-knx
#
# CVS: $Id: node.conf.sample,v 1.35 2005/08/02 15:39:32 fabianx Exp $
#########################################################################
# General FreeNX directives
#########################################################################
# The host name which is used by NX server. It's should be used if it's
# different than the default hostname (as returned by `hostname`)
#SERVER_NAME="$(hostname)"
# The port number where local 'sshd' is listening.
SSHD_PORT=22
#########################################################################
# Authentication / Security directives
#########################################################################
# Authentication directives
# This adds the usermode to the possible authentication methods
# Usermode means that a user can start the nxserver as his shell
# and connect directly to the right server via a custom client.
#ENABLE_USERMODE_AUTHENTICATION="0"
# This adds the passdb to the possible authentication methods
ENABLE_PASSDB_AUTHENTICATION="1"
# This adds SSH to the possible authentication methods. For it to work sshd
# must be set up at localhost accepting password authentication.
ENABLE_SSH_AUTHENTICATION="1"
# This adds SU to the possible authentication methods. For it to work the
# "nx" user must be in the wheel (RedHat, Fedora) or the users group (SUSE)
# and the user logging in must have a valid shell that accepts the -c
# parameter.
ENABLE_SU_AUTHENTICATION="1"
# Require all users to be in the passdb, regardless of authentication method
ENABLE_USER_DB="1"
# If enabled forces the user to use encryption. This will bail out
# if the user does not have encryption enabled.
#ENABLE_FORCE_ENCRYPTION="0"
# Refuse the NX client connection if SSHD does not export the
# SSH_CONNECTION and SSH_CLIENT variables in the environment
# passed to the NX server.
# 1: Will check the remote IP and will not accept the
# connection if it can't be determined.
# 0: Will accept the connection even if the remote IP
# is not provided.
#SSHD_CHECK_IP="0"
# If set to greater zero, nxserver will timeout after that many seconds
# before authentication succeeds.
#
#NX_SERVER_TIMEOUT="10"
#########################################################################
# Restriction directives
#########################################################################
# The base display number from which sessions are started.
#DISPLAY_BASE=1000
# The maximum number of contemporary sessions that can be run on FreeNX
#SESSION_LIMIT=200
# The maximum number of contemporary sessions that a single user can run
# on FreeNX. Defaults to the value of SESSION_LIMIT.
#SESSION_USER_LIMIT=200
# The number of displays reserved for sessions, it has to be greater or equal
# to the maximum number of contemporary sessions that a server can run.
#DISPLAY_LIMIT=200
# User for which sessions should be persistent. Either the keyword "all" or a
# comma-separated list of usernames or groups in the @groupname syntax.
#ENABLE_PERSISTENT_SESSION="all"
# Users and groups for whom persistent sessions should be disabled.
# Especially useful if ENABLE_PERSISTENT_SESSION="all"
#DISABLE_PERSISTENT_SESSION=""
#########################################################################
# Logging directives
#########################################################################
# This directives controls the verbosity of the server-wide log.
# 0: No Logging
# 1: Errors
# 2: Warnings
# 3: Important information
# 4: Server - Client communication
# 5: Information
# 6: Debugging information
# 7: stderror of some applications
NX_LOG_LEVEL=6
# By setting this to 0 the nxserver might be a bit faster, but passwords can be found in the log files.
NX_LOG_SECURE=0
# Before turning logging on, please make sure that NX_LOGFILE is
# writeable for the "nx" user
NX_LOGFILE=/var/log/nxserver.log
# This directive controls if the temporary session directory
# ($HOME/.nx/C-<hostname>-<display>-<session_id>) should be kept after a
# session has ended. A successfully terminated session will be saved as
# T-C-<hostname>-<display>-<session_id> while a failed session will be saved
# as F-C-<hostname>-<display>-<session_id>.
# The default is to cleanup the directories.
#SESSION_LOG_CLEAN=1
# Amount of seconds nxserver is to keep session history. The default of 2592000
# is equivalent to 30 days. If this is 0 no session history will be kept
# and a negative value denotes infinity.
#SESSION_HISTORY=2592000
#########################################################################
# Forwarding directives
#########################################################################
# FreeNX with ENABLE_SERVER_FORWARD="1" will automatically forward all
# connections to the host specified in SERVER_FORWARD_HOST with the
# secret key SERVER_FORWARD_KEY.
#
# This allows to have a "chain" of NX Servers. Note that you will need to
# use "SSL encryption" for all connections.
#ENABLE_SERVER_FORWARD="0"
#SERVER_FORWARD_HOST=""
#SERVER_FORWARD_PORT=22
#SERVER_FORWARD_KEY="/usr/NX/share/client.id_dsa.key"
# FreeNX with ENABLE_NOMACHINE_FORWARD_USER="1" will automatically forward all
# connections to the commercial NoMachine nxserver installed on the same
# machine. This feature is introduced to enable the usage of FreeNX and
# NoMachine NX side by side on the same machine without conflicts.
#
# To make a connection to the FreeNX server, just use 'freenx.<user>' as
# username (where <username> is the existing Unix username. (You do not
# need to create a user named 'freenx.<user>'!)
#
# To make a connection to the NoMachine nxserver, use the unmodified
# '<user>' username.
#ENABLE_NOMACHINE_FORWARD_USER="0"
#NOMACHINE_SERVER="/usr/NX/bin/nxserver"
#NOMACHINE_NX_HOME_DIR="/usr/NX/home/nx"
# To just forward connections to the NoMachine server, which connect to a
# certain port enable the following two directives.
#
# Note: You need to let SSHD listen to several ports to make use of this
# directive.
#ENABLE_NOMACHINE_FORWARD_PORT="0"
#NOMACHINE_FORWARD_PORT="22"
#########################################################################
# Services directives
#########################################################################
# FreeNX with ENABLE_ESD_PRELOAD="1" will automatically try to setup
# the sound with the help of the esd media helper.
#
# Currently ESD will be used just by the Windows NX Client.
#
# Be sure that $ESD_BIN_PRELOAD is in your path, does exist and work
# before enabling this directive.
#ENABLE_ESD_PRELOAD="0"
#ESD_BIN_PRELOAD="esddsp"
# FreeNX with ENABLE_ARTSD_PRELOAD="1" will automatically try to setup
# the sound with the help of the artsd media helper.
#
# Currently ARTSD will be used just by the Linux NX Client.
#
# Be sure that $ARTSD_BIN_PRELOAD is in your path, does exist and work
# before enabling this directive.
#ENABLE_ARTSD_PRELOAD="0"
#ARTSD_BIN_PRELOAD="artsdsp"
# FreeNX with ENABLE_KDE_CUPS="1" will automatically write
# $KDE_PRINTRC and put the current used port into it.
# $KDE_PRINTRC is automatically calculated if its not set.
#ENABLE_KDE_CUPS="0"
#KDE_PRINTRC="$KDEHOME/share/config/kdeprintrc"
#CUPS_ETC="/etc/cups"
#########################################################################
# Path directives
#########################################################################
# USER_FAKE_HOME is the base directory for the .nx directory. Use this
# parameter instead of the users home directory if $HOME is on a NFS share.
# Note that this directory must be unique for every user! To accomplish this
# it is recommended to include $USER in the path.
#USER_FAKE_HOME=$HOME
# Add the nx libraries to LD_LIBRARY_PATH before starting nx agents.
# WARNING: This will NOT (and should not) affect applications. ONLY Disable
# this if the nx libraries are in a standard system path (such as /usr/lib)!
#SET_LD_LIBRARY_PATH="1"
# The command binary for the default window manager. If set it is run when a
# 'unix-custom' session is requested by the NX Client and an application
# to run is specified. It defaults to empty (ie no WM is run).
# If KILL_DEFAULT_X_WM is set the WM is terminated after the started
# application finishes. Else FreeNX will wait for the WM to complete.
#DEFAULT_X_WM=""
#KILL_DEFAULT_X_WM="1"
# When a 'unix-default' session is requested by the client the user's X startup
# script will be run if pressent and executable, otherwise the default X
# session will be run.
# Depending on distribution USER_X_STARTUP_SCRIPT might be .Xclients, .xinitrc
# and .Xsession
# Depending on distribution DEFAULT_X_SESSION might be /etc/X11/xdm/Xsession,
# /etc/X11/Sessions/Xsession or /etc/X11/xinit/xinitrc
#USER_X_STARTUP_SCRIPT=.Xclients
#DEFAULT_X_SESSION=/etc/X11/xdm/Xsession
# The key that contains the name of the script that starts a KDE session.
# It's run when a 'unix-kde' session is requested by the client.
#COMMAND_START_KDE=startkde
# The key that contains the name of the script that starts a gnome session.
# It's run when a 'unix-gnome' session is requested by the client.
#COMMAND_START_GNOME=gnome-session
# The key that contains the name of the script that starts a CDE session.
# It's run when a 'unix-cde' session is requested by the client.
#COMMAND_START_CDE=cdwm
# The key that contains the name of the complete path of command name
# 'xterm'. It is run when a unix "xterm" session is requested by the
# client.
#COMMAND_XTERM=xterm
# The key that contains the name of the complete path of command name
# 'xauth'.
#COMMAND_XAUTH=/usr/X11R6/bin/xauth
# The key that contains the name of the complete path of command name
# 'smbmount'.
#COMMAND_SMBMOUNT=smbmount
# The key that contains the name of the complete path of command name
# 'smbumount'.
#COMMAND_SMBUMOUNT=smbumount
# The key that contains the name of the complete path of the 'netcat' command.
#COMMAND_NETCAT=netcat
# The key that contains the name of the complete path of the 'ssh' and
# 'ssh-keygen' command.
#COMMAND_SSH=ssh
#COMMAND_SSH_KEYGEN=ssh-keygen
# The key that contains the name of the complete path of the 'cupsd' command.
#COMMAND_CUPSD=/usr/sbin/cupsd
# The tool to generate md5sums with
#COMMAND_MD5SUM=md5sum
#########################################################################
# Misc directives
#########################################################################
# When set to 1 this will automatically resume started sessions
#ENABLE_AUTORECONNECT="0"
# When set to 1 this will automatically resume started sessions
# but only if an older client version is used
#ENABLE_AUTORECONNECT_BEFORE_140="1"
# When set to 1 exports NXUSERIP / NXSESSIONID in nxnode
#EXPORT_USERIP="0"
#EXPORT_SESSIONID="0"
# This can be set to any executable, which is started after session startup
# like: $NODE_AUTOSTART {start|restore}
#NODE_AUTOSTART=""
# When set to 1 will start nxagent in rootless mode.
#ENABLE_ROOTLESS_MODE="1"
# If enabled writes entries via the COMMAND_SESSREG program
# into utmp/wtmp/lastlog database.
# Note: You have to make sure that you add the nx user to the
# utmp or tty group or how its called on your system
# before this directive works.
#ENABLE_USESSION="0"
#COMMAND_SESSREG="sessreg"
# Extra options sent to the different nx agents. See !M documentation
# for examples of useful parameters.
#AGENT_EXTRA_OPTIONS_RFB=""
#AGENT_EXTRA_OPTIONS_RDP=""
#AGENT_EXTRA_OPTIONS_X=""
# The number of seconds we wait for the nxagent to start before
# deciding startup has failed
#AGENT_STARTUP_TIMEOUT="60"
# The font server the agent will use. If set to "" no font server is used.
# For this to do any good, the client has to have the same font server set
# in /etc/X11/XF86Config
#AGENT_FONT_SERVER=""
# Disable or enable use of 'tcp nodelay' on proxy. Old versions of Linux
# kernels have problems using this option on sockets that will cause a loss
# of TCP connections. This option is not set by default to allow clients to
# specify whether to enable or disable TCP nodelay. Setting this option to
# the value of "0" NX proxy avoids using 'tcp nodelay' but it will cause a
# loss of interaction in sessions.
#PROXY_TCP_NODELAY="0"
# Extra options to nxproxy. See !M documentation for useful parameters.
#PROXY_EXTRA_OPTIONS=""
mit
nxserver --adduser username und
nxserver --passwd username
hab ich die user erstellt.
Dann noch passwd -u nx
und den server restartet. Nix geht.
Hat jemand eine Idee?
Danke und Gruss Guido |
|
|
| |
|
|
|
 |
|
|
|
Titel: RE: NX-Server
Verfasst am: 25.09.2006, 15:26 Uhr
|
|
Anmeldung: 25. Mar 2005
Beiträge: 2133
|
|
Guido, drei allgemeine Bemerkungen zu freenx:
1. Die Einrichtung ist denkbar einfach mit dpkg-reconfigure freenx
2. Um sshd beim Booten starten zu können, musst du freeze/unfreeze-rc.d durchführen.
3. Mit dem Windowsclient 2.0 klappt es nicht; du musst 1.4 oder 1.5 verwenden. |
_________________
And I ain't got no worries 'cause I ain't in no hurry at all (Doobie Brothers, "Black Water").
|
| |
|
|
|
|
|
|
|
Titel:
Verfasst am: 25.09.2006, 15:41 Uhr
|
|
Anmeldung: 07. Jun 2005
Beiträge: 252
|
|
Hi,
danke für die fixe Antwort:
sshd ist klar - hab ich gemacht - ssh klappt ja auch schon.
Win-client - was ist win  ? Ich hab nur debian-Rechner .
Den tipp mit dpkg-reconfigure freenx werd ich versuchen....
Gruss Guido
Nachtrag: hat leider nix gebracht  |
|
|
| |
|
|
|
|
|
|
|
Titel:
Verfasst am: 25.09.2006, 16:13 Uhr
|
|
Anmeldung: 25. Mar 2005
Beiträge: 2133
|
|
| Da hast du irgend etwas verbockt. Der freenx server, eingerichtet mit dpkg-reconfigure freenx, läuft unter RC3 tadellos. |
_________________
And I ain't got no worries 'cause I ain't in no hurry at all (Doobie Brothers, "Black Water").
|
| |
|
|
|
|
|
|
|
Titel:
Verfasst am: 25.09.2006, 16:28 Uhr
|
|
Anmeldung: 07. Jun 2005
Beiträge: 252
|
|
Hi,
das der Fehler 30cm vor dem Monitor sitzt, ist klar
Ich komm nur ned drauf, was ich nicht verstehe oder verdaddelt habe....
Gruss Guido |
|
|
| |
|
|
|
|
|
|
|
Titel:
Verfasst am: 25.09.2006, 18:52 Uhr
|
|
Anmeldung: 06. Feb 2005
Beiträge: 1194
Wohnort: Mecklenburg
|
|
|
guido17 hat folgendes geschrieben::
das der Fehler 30cm vor dem Monitor sitzt, ist klar
Ich würde einfach zum Ausgangspunkt zurückgehen:
-> su
-> apt-get update && apt-get remove freenx --purge && apt-get install freenx && dpkg-reconfigure freenx
MfG T. |
_________________
Notebook: Kanotix2006-1-rc1, Kernel 2.6.17.13-kanotix-2, ECS A531,Transmeta-Crusoe 1GHz,256MB, IceWM,
PC: Kanotix2006-1-rc1, Kernel 2.6.17.13-kanotix-2, VIA-Ezra 933MHz, 256MB, XFCE4
|
| |
|
|
|
|
|
|
|
Titel:
Verfasst am: 26.09.2006, 07:33 Uhr
|
|
Anmeldung: 02. Sep 2004
Beiträge: 145
|
|
Hi,
bitte poste mal die Fehlermeldung des NX-Clients und zumindest die relevanten Zeilen des NX-Logs. |
_________________
Beste Grüße, rh
|
| |
|
|
|
|
|
|
|
Titel:
Verfasst am: 26.09.2006, 16:10 Uhr
|
|
Anmeldung: 07. Jun 2005
Beiträge: 252
|
|
Hi,
danke für die tipps, komm aber es am WE dazu..
Gruss Guido |
|
|
| |
|
|
|
|
|
|
