LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 07-21-2010, 02:25 PM   #1
xri
Member
 
Registered: Aug 2002
Distribution: Archlinux, Garuda Linux
Posts: 283
Blog Entries: 11

Rep: Reputation: 41
Question freenx: Authentication works but session fails


  1. I installed freenx-0.7.3-i486-1alien.tgz on the server (with Slack 12.1), all according to instructions.
  2. I installed the nomachine nxclient 3.4.0-7 on the client (with Slack 12.2).
  3. I ran setup and configured. I used the default no-machine keys, not custom ones.
  4. Since authentication failed at the beginning, I enabled DBauthentication, and added my user and password, which seemed to allow authentication to occur.
  5. Here is my node.conf:

    Quote:
    # 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
    #
    # SVN: $Id: node.conf.sample 580 2008-08-22 00:44:43Z fabianx $

    #########################################################################
    # 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="0"

    # Require all users to be in the passdb, regardless of authentication method
    #ENABLE_USER_DB="0"


    # 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 ENABLE_SLAVE_MODE="1" the user will be just logged in _once_ and the
    # communication is done via nxnode slave mode.
    #
    # This is useful for one time passwords or to have less traffic in utmp
    # and wtmp.
    #
    # Also session startup times are much faster in slave mode. This is true especially
    # if many printers or shares have to be added.
    #
    # For this to work the binary nxserver-helper has to be installed in
    # PATH_BIN.
    #
    #ENABLE_SLAVE_MODE="1"

    # If ENABLE_LOG_FAILED_LOGINS="1" then failed login attempts are logged to the system
    # auth.log.
    #
    # This is useful in combination with tools like fail2ban.
    #
    # The default is to log failed login attemps via syslog (3).
    #
    ENABLE_LOG_FAILED_LOGINS="1"

    #########################################################################
    # 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=""

    # This enables the mirroring of running sessions via VNC feature.
    #
    # Session is marked as resumable and type is vnc-mirrored.
    #
    #ENABLE_MIRROR_VIA_VNC=1

    # This enables the sharing of :0 via VNC feature.
    #
    # Session is marked as resumable and type is vnc-local.
    #
    # Note: You need to have the rights to access the display
    # else it does not work.
    #
    #ENABLE_DESKTOP_SHARING=1

    #
    # General shadowing / mirroring notes:
    #
    # By default shadowing is only allowed for the same user.
    #
    # If nxserver finds nxshadowacl binary, it asks it, for which users
    # the permission is granted.
    #
    # nxshadowacl <user>
    #
    # Exit code:
    #
    # 0 -> Save cookie in session file for other users
    # 1 -> Do not save cookie
    #
    # Check if user is allowed to be shadowed by admin user.
    #
    # nxshadowacl <user> <admin>
    #
    # Exit code:
    #
    # 0 -> Yes, allow shadowing and add to list
    # 1 -> No, don't allow shadowing
    #

    #
    # When using NX 3.0 shadowing, this enables asking the user whether
    # he authorizes another user to shadow his session
    #
    # 0: No authorization request will be presented,
    # and the session will be shadowed as if the user had approved.
    # 1: (default) Ask for authorization
    #
    #ENABLE_SESSION_SHADOWING_AUTHORIZATION=1

    # Allow session shadowing in interactive mode:
    #
    # 1: The shadowing user can interact with the shadowed session.
    #
    # 0: The shadowed session is view-only. No interaction with the
    # shadowed session is possible.
    #
    #ENABLE_INTERACTIVE_SESSION_SHADOWING=1

    #
    # Enable or disable clipboard:
    #
    # client: The content copied on the client can be pasted inside the
    # NX session.
    #
    # server: The content copied inside the NX session can be pasted
    # on the client.
    #
    # both: The copy&paste operations are allowed both between the
    # client and the NX session and vice-versa.
    #
    # none: The copy&paste operations between the client and the NX
    # session are never allowed.
    #
    #ENABLE_CLIPBOARD="both"


    #
    # Enable or disable the pulldown dialog, which provides a graphical
    # way to suspend or terminate the rootless session:
    #
    # 1: Enabled. The pulldown menu is shown when the mouse pointer
    # moves near the middle of the top boundary of a window and
    # allows the user to suspend or terminate the session by means
    # of an icon-click.
    #
    # 0: Disabled. The ctrl+alt+T key combination has to be issued
    # to get the dialog for suspending or terminating the session.
    #
    #ENABLE_PULLDOWN_MENU="1"


    # The option USE_PROCESSOR_TASKSET is for setting the CPU affinity of all
    # nx related processes.
    #
    # Note: To have for example startkde run on even another core, just specify:
    #
    # COMMAND_STARTKDE="taskset -c 2 -- startkde"
    #
    # FreeNX runs this option like: $COMMAND_TASKSET -cp "$USE_PROCESSOR_TASKSET" $$
    #
    # So with $USE_PROCESSOR_TASKSET set to 3,4 it would balance the tasks to cores
    # 3 and 4.
    #
    # If this option is empty, no balance to cores is done.
    #
    #USE_PROCESSOR_TASKSET=""

    # If you set ENABLE_ADVANCED_SESSION_CONTROL="1" you can start a new application in an already
    # running rootless session by using "add <rest of name>" as session name.
    #
    # Note: The client will return a message on that.
    #
    #ENABLE_ADVANCED_SESSION_CONTROL="0"

    # If you set ENABLE_SHOW_RUNNING_SESSIONS="0" then nxserver will only show
    # suspended sessions and you will not be able to resume or terminate a running
    # session.
    #
    #ENABLE_SHOW_RUNNING_SESSIONS="1"

    #########################################################################
    # 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=1

    # Before turning logging on, please make sure that NX_LOGFILE is
    # writeable for the "nx" user
    NX_LOGFILE=/home/xri/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=0

    # 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_PORT="1" will automatically forward all
    # connections to the commercial NoMachine nxserver installed on the same
    # machine, which go in by port NOMACHINE_FORWARD_PORT. This feature is introduced
    # to enable the usage of FreeNX and NoMachine NX side by side on the same machine
    # without conflicts.
    #
    # 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"

    #NOMACHINE_SERVER="/usr/NX/bin/nxserver"
    #NOMACHINE_NX_HOME_DIR="/usr/NX/home/nx"


    # LOAD BALANCING
    # ==============
    #
    # To do load balancing setup some hosts in LOAD_BALANCE_SERVERS and
    # make:
    #
    # - either sure that all incoming connections are sent to the master
    # server by using forwarding directives on the "slave" servers.
    #
    # - or share the session database space via NFS between the servers.
    # (not recommended at the moment as race conditions for DISPLAYs can
    # occur)
    #

    #LOAD_BALANCE_SERVERS=""

    # The following load_balance_algorithms are available at the moment:
    #
    # "load", "round-robin", "random"
    #
    # For "load" you need a script called nxcheckload in PATH_BIN.
    #
    # A sample script, which you can change to your needs it shipped with
    # FreeNX under the name nxcheckload.sample.

    #LOAD_BALANCE_ALGORITHM="random"

    # By setting ENABLE_LOADBALANCE="1" you can let users choose their
    # preferred host, while being forwarded to another server. Of course
    # this is just a preference. The loadbalancing algorithm can completely
    # choose to ignore the users choice.

    #ENABLE_LOAD_BALANCE_PREFERENCE="0"

    #########################################################################
    # 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 socket into it.
    #
    # If you additionally enable ENABLE_KDE_CUPS_DYNAMIC it will set the
    # Host entry to the script nxcups-gethost, which dynamically tries all
    # possible entries to find the current printing host.
    #
    # The order is: CUPS_SERVER (env var), ~/.cups/client.conf, $KDE_PRINTRC,
    # $CUPS_DEFAULT_SOCK, localhost
    #
    # So this option is most useful with ENABLE_CUPS_SERVER_EXPORT="1".
    #
    # $KDE_PRINTRC is automatically calculated if its not set.

    #ENABLE_KDE_CUPS="0"
    #ENABLE_KDE_CUPS_DYNAMIC="0"
    #KDE_PRINTRC="$KDEHOME/share/config/kdeprintrc"

    # FreeNX with ENABLE_CUPS_SERVER_EXPORT="1" will automatically
    # export the environment variable CUPS_SERVER.

    #ENABLE_CUPS_SERVER_EXPORT="1"

    # FreeNX with ENABLE_CUPS_SEAMLESS will automatically try to download the
    # necessary ppds from the client.
    #
    # As the forwarding is just active as soon as nxagent is started,
    # we need a small delay of $CUPS_SEAMLESS_DELAY.
    #
    # Note: You need to use a patched cupsd on client side.

    #ENABLE_CUPS_SEAMLESS="0"
    #CUPS_SEAMLESS_DELAY="10"

    # FreeNX with ENABLE_FOOMATIC will integrate the foomatic db to the list
    # of available ppd drivers via the $COMMAND_FOOMATIC command.

    #ENABLE_FOOMATIC="1"
    #COMMAND_FOOMATIC="/usr/lib/cups/driver/foomatic-ppdfile"

    # CUPS_BACKEND and CUPS_ETC are the corresponding paths of your CUPS
    # installation.

    #CUPS_BACKEND="/usr/lib/cups/backend"
    #CUPS_IPP_BACKEND="$CUPS_BACKEND/nxipp"
    #CUPS_DEFAULT_SOCK="/var/run/cups/cups.sock"
    #CUPS_ETC="/etc/cups"

    # SAMBA_MOUNT_SHARE_PROTOCOL is a key to configure the supported
    # protocols for mounting shares.
    #
    # This key can be set to the following values:
    #
    # both, either SMB and CIFS protocol are supported, this is the default value.
    # smbfs, only SMB protocol is supported.
    # cifs, only CIFS protocol is supported.
    # none, no network file-sharing protocol is supported.

    #SAMBA_MOUNT_SHARE_PROTOCOL="both"

    # FreeNX with ENABLE_SAMBA_PRELOAD="1" will automatically setup
    # port 445 and 139 and forward them to the used samba port.
    #
    # This enables samba browsing to the local subnet in for example
    # konqueror.
    #
    #ENABLE_SAMBA_PRELOAD="0"

    # FreeNX with ENABLE_SOURCE_BASH_PROFILE="1" will source the users ~/.bash_profile
    # before application startup as we are kind of a login shell.
    #
    # With this key this behaviour can be enabled (default) or disabled.
    #
    #ENABLE_SOURCE_BASH_PROFILE="1"

    #########################################################################
    # 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/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 command name
    # 'mount.cifs'.
    #COMMAND_SMBMOUNT_CIFS=/sbin/mount.cifs

    # The key that contains the name of the complete path of command name
    # 'umount.cifs'.
    #COMMAND_SMBUMOUNT_CIFS=/sbin/umount.cifs

    # The key that contains the name of the complete path of the 'netcat' command.
    #COMMAND_NETCAT=nc

    # 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="openssl md5"

    # The key that contains the name of the complete path of the 'rdesktop' command.
    #COMMAND_RDESKTOP=rdesktop

    # The key that contains the name of the complete path of the 'vncviewer' command.
    #COMMAND_VNCVIEWER=vncviewer

    # The key that contains the name of the complete path of the 'vncpasswd' command.
    # By default the builtin nxpasswd is used.
    #COMMAND_VNCPASSWD="$PATH_BIN/nxpasswd"

    # The key that contains the name of the complete path of the 'x11vnc' command.
    #COMMAND_X11VNC=x11vnc

    # The key that contains the name of the complete path of the 'taskset' command.
    #COMMAND_TASKSET=taskset

    #########################################################################
    # Misc directives
    #########################################################################

    # When you installed an old 1.5.0 NX Backend, set this to 1.
    #ENABLE_1_5_0_BACKEND="0"

    # 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="1"

    # 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="1"
    #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="-nolisten tcp"

    # 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=""

    # Extra options to nxproxy. See !M documentation for useful parameters.
    #PROXY_EXTRA_OPTIONS=""

    # In case you want to use an external 'rdesktop' command
    # set this to "1".
    #
    # If nxdesktop cannot be found this is set automatically to "1".
    #ENABLE_EXTERNAL_NXDESKTOP="0"

    # This configuration variable determines if 'rdesktop' command should be run with -k keyboard option
    # or if the keyboard should be autodetected.
    #
    #ENABLE_EXTERNAL_NXDESKTOP_KEYBOARD="1"

    # In case you want to use an external 'nxviewer' command
    # set this to "1".
    #
    # If nxviewer cannot be found this is set automatically to "1".
    #ENABLE_EXTERNAL_NXVIEWER="0"
  6. Here is my nxserver.log when I try to start a session from the client:

    Quote:
    -- NX SERVER START: -c /usr/bin/nxserver - ORIG_COMMAND=
    -- NX SERVER START: - ORIG_COMMAND=
    Info: Using fds #4 and #3 for communication with nxnode.
    HELLO NXSERVER - Version 3.2.0-73 OS (GPL, using backend: not detected)
    NX> 105 hello NXCLIENT - Version 3.2.0
    NX> 134 Accepted protocol: 3.2.0
    NX> 105 SET SHELL_MODE SHELL
    NX> 105 SET AUTH_MODE PASSWORD
    NX> 105 login
    NX> 101 User: xri
    NX> 102 Password:
    Info: Auth method: passdb
    NX> 103 Welcome to: darkmatter user: xri
    NX> 105 listsession --user="xri" --status="suspended,running" --geometry="1024x768x24+render" --type="unix-kde"
    NX> 127 Sessions list of user 'xri' for reconnect:

    Display Type Session ID Options Depth Screen Status Session Name
    ------- ---------------- -------------------------------- -------- ----- -------------- ----------- ------------------------------


    NX> 148 Server capacity: not reached for user: xri
    NX> 105 startsession --link="adsl" --backingstore="1" --encryption="1" --cache="16M" --images="64M" --shmem="1" --shpix="1" --strict="0" --composite="1" --media="0" --session="darkmatter" --type="unix-kde" --geometry="1024x749" --client="linux" --keyboard="pc105/us" --screeninfo="1024x749x24+render"

    &link=adsl&backingstore=1&encryption=1&cache=16M&images=64M&shmem=1&shpix=1&strict=0&composite=1&med ia=0&session=darkmatter&type=unix-kde&geometry=1024x749&client=linux&keyboard=pc105/us&screeninfo=1024x749x24+render&clientproto=3.2.0&user=xri&userip=24.29.44.192&uniqueid=981E275B713 857280052D181E3D63729&display=1000&host=127.0.0.1
    NX> 1000 NXNODE - Version 3.2.0-73 OS (GPL, using backend: not detected)
    server_nxnode_echo: NX> 1000 NXNODE - Version 3.2.0-73 OS (GPL, using backend: not detected)
    NX> 105 NX> 1004 Error: NX Agent exited with exit status 1. To troubleshoot set SESSION_LOG_CLEAN=0 in node.conf and investigate "/home/xri/.nx/F-C-darkmatter-1000-981E275B713857280052D181E3D63729/session". You might also want to try: ssh -X myserver; /usr/bin/nxnode --agent to test the basic functionality. Session log follows:
    NX> 1006 Session status: closed
    NX> 700 Session id: darkmatter-1000-981E275B713857280052D181E3D63729
    NX> 705 Session display: 1000
    NX> 703 Session type: unix-kde
    NX> 701 Proxy cookie: 480e6bc8c27fab32147355a246f024c3
    NX> 702 Proxy IP: 127.0.0.1
    NX> 706 Agent cookie: 480e6bc8c27fab32147355a246f024c3
    NX> 704 Session cache: unix-kde
    NX> 707 SSL tunneling: 1
    server_nxnode_echo: NX> 596 Session startup failed.
    NX> 596 Session startup failed.
    server_nxnode_echo: NX> 1004 Error: NX Agent exited with exit status 1. To troubleshoot set SESSION_LOG_CLEAN=0 in node.conf and investigate "/home/xri/.nx/F-C-darkmatter-1000-981E275B713857280052D181E3D63729/session". You might also want to try: ssh -X myserver; /usr/bin/nxnode --agent to test the basic functionality. Session log follows:
    session_close 981E275B713857280052D181E3D63729
    server_nxnode_echo: NX> 1006 Session status: closed
    server_nxnode_echo: NX> 700 Session id: darkmatter-1000-981E275B713857280052D181E3D63729
    server_nxnode_echo: NX> 705 Session display: 1000
    server_nxnode_echo: NX> 703 Session type: unix-kde
    server_nxnode_echo: NX> 701 Proxy cookie: 480e6bc8c27fab32147355a246f024c3
    server_nxnode_echo: NX> 702 Proxy IP: 127.0.0.1
    server_nxnode_echo: NX> 706 Agent cookie: 480e6bc8c27fab32147355a246f024c3
    server_nxnode_echo: NX> 704 Session cache: unix-kde
    server_nxnode_echo: NX> 707 SSL tunneling: 1
    NX> 1001 Bye.
    server_nxnode_echo: NX> 1001 Bye.

Thanks for reading this long post.
I hope to get some clues; I'm quite frustrated.
 
Old 07-22-2010, 07:46 AM   #2
centosboy
Senior Member
 
Registered: May 2009
Location: london
Distribution: centos5
Posts: 1,137

Rep: Reputation: 116Reputation: 116
Quote:
Originally Posted by xri View Post
  1. I installed freenx-0.7.3-i486-1alien.tgz on the server (with Slack 12.1), all according to instructions.
  2. I installed the nomachine nxclient 3.4.0-7 on the client (with Slack 12.2).
  3. I ran setup and configured. I used the default no-machine keys, not custom ones.
  4. Since authentication failed at the beginning, I enabled DBauthentication, and added my user and password, which seemed to allow authentication to occur.
  5. Here is my node.conf:



  6. Here is my nxserver.log when I try to start a session from the client:



Thanks for reading this long post.
I hope to get some clues; I'm quite frustrated.

I used this to get freenx running on suse 10.2 and centos 5.2. Should be similar for your distro
 
Old 07-22-2010, 10:28 AM   #3
Slax-Dude
Member
 
Registered: Mar 2006
Location: Valadares, V.N.Gaia, Portugal
Distribution: Slackware
Posts: 528

Rep: Reputation: 272Reputation: 272Reputation: 272
I have always used Alienbob's freenx packages and it works fine for me on slackware-12.2, 13, 13.1 and slackware64-13.1

In all of them I had to unlock the "nx" user as per Alienbob's instructions here: http://alien.slackbook.org/dokuwiki/...d=slackware:nx
 
Old 07-24-2010, 01:05 PM   #4
xri
Member
 
Registered: Aug 2002
Distribution: Archlinux, Garuda Linux
Posts: 283

Original Poster
Blog Entries: 11

Rep: Reputation: 41
Thank you guys for the links and tips. I will use them on my next attempt.
I'll use the latest versions of everything this time (I wanted to get the hang of using nx before running a full upgrade).
 
Old 12-15-2010, 01:53 PM   #5
browny_amiga
Member
 
Registered: Dec 2001
Location: /mnt/UNV/Mlkway/Earth/USA/California/Silicon Valley
Distribution: Kubuntu, Debian Buster Stable, Windoze 7
Posts: 684

Rep: Reputation: 56
I can warmly recommend x2go. I switched over from freenx, and nx server never worked well at all for me and was a constant hassle. I got tired of it after countless hours of debugging that I wished for an alternative. And it arrived.

x2go is all you wish a remote X client to be.
 
1 members found this post helpful.
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Access FreeNX session locally ufmale Linux - Software 5 10-21-2009 02:23 AM
FreeNX session ufmale Linux - Newbie 2 09-29-2009 10:51 PM
Login fails on 'std' session, works on 'failsafe' - how to fix? bjorke Linux - Newbie 3 05-26-2009 10:17 AM
LDAP Authentication Fails for Non-Root, but works for root ludwig Linux - Server 2 08-16-2008 05:53 PM
Connecting to existing session w/ FREENX Ashrack Linux - Networking 0 07-02-2006 10:02 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 03:42 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration