nxserver von außen erreichen, macht probleme

S

seeadler

Tripel-As
#
# 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 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=0
 
Lern doch bitte erstmal deine Frage zu stellen.
Wir sind hier ja willig zu helfen.
Aber das schießt doch eindeutig den Vogel ab!
 
Problem zu verstehen macht Probleme

:D
Was willst du fragen?
Aber Jeder hat eine zweite Chance. :devil:

Debian oder Ubuntu?


Wolfgang
 
sorry, tut mir leid;
system: debian etch
meine ddclient konfiguration

# Configuration file for ddclient generated by debconf
#
# /etc/ddclient.conf
id=/var/run/ddclient.pid
protocol=dyndns2
use=web
server=members.dyndns.org
login=xxxxx
password='xxxx'
xxxxx.dyndns.org

wenn ich mich nun mit dem nxclient von einer windows machine mit dem nxserver auf debian verbinden möchte, wird folgende meldung ausgegeben:
Code:

neoiating failure


meine nxserver konfiguration:
# 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 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=0


aus im lan erreiche ich meinen server ohne probleme
welche konfiguration muss ich vornehmen, damit ich auch meinen nxserver von außen erreiche?
 
Zuletzt bearbeitet:
stichwort "portforwarding" am router
editier mal bitte die posts und setz den code in
Code:
-tags
 
haben den port 22 am router geforwardet
tcp 22/22
 
wenn ich das programm putty auf dem windows - rechner habe und ich mit diesem auf den linux server verbinden möchte,
ist diese Verbindung dann auch verschlüsselt?
 

Ähnliche Themen

Nginx als Reverse Proxy für Nextcloud und Emby

Zugriff Ubuntu 16.04. auf Freigabe 18.04. LTS nicht möglich

Email via script via Exchange Server (SASL)

Samba-Server mit Univention Corporate Server

Senior System & Network Admin in Berlin

Zurück
Oben