Get the App
SLTechnology News&Howtos  ›  Servers  › 

Example Analysis of suse linux 11 xmanager connection configuration

Shulou Source: shulou.com Published: 2022-06-01 06:31:50 10月02日 Update

Suse linux 11 xmanager connection configuration example analysis, I believe that many inexperienced people do not know what to do, so this article summarizes the causes of the problem and solutions, through this article I hope you can solve this problem.

Suse 10 and suse 11 have different settings. Here is how to set up suse 11. The relevant configuration files are modified as follows:

1. Modify / etc/sysconfig/displaymanager

DISPLAYMANAGER_REMOTE_ACCESS= "yes"

DISPLAYMANAGER_ROOT_LOGIN_REMOTE= "yes"

DISPLAYMANAGER_XSERVER_TCP_PORT_6000_OPEN= "yes"

You can also modify DISPLAYMANAGER= "gdm" (default is GDM)

Can be changed to DISPLAYMANAGER= "kdm"

(modify / etc/gdm/gdm_sysconfig.conf

Formerly known as

# custom.conf was last time updated with following sysconfig:

DISPLAYMANAGER_REMOTE_ACCESS= "no"

DISPLAYMANAGER_ROOT_LOGIN_REMOTE= "no"

DISPLAYMANAGER_STARTS_XSERVER= "yes"

DISPLAYMANAGER_XSERVER_TCP_PORT_6000_OPEN= "no"

DISPLAYMANAGER_AUTOLOGIN= ""

DISPLAYMANAGER_PASSWORD_LESS_LOGIN= "yes"

DISPLAYMANAGER_AD_INTEGRATION= "no"

DISPLAYMANAGER_SHUTDOWN= "root"

PERMISSION_SECURITY= "easy local"

Modify to

DISPLAYMANAGER_REMOTE_ACCESS= "yes"

DISPLAYMANAGER_ROOT_LOGIN_REMOTE= "yes"

DISPLAYMANAGER_STARTS_XSERVER= "yes"

DISPLAYMANAGER_XSERVER_TCP_PORT_6000_OPEN= "yes"

DISPLAYMANAGER_AUTOLOGIN= "no"

DISPLAYMANAGER_PASSWORD_LESS_LOGIN= "no"

DISPLAYMANAGER_AD_INTEGRATION= "no"

DISPLAYMANAGER_SHUTDOWN= "root"

PERMISSION_SECURITY= "easy local")

Note: it has been verified that if you have modified gdm_sysconfig.conf instead of displaymanager, you will find that you do not have port 177and cannot connect remotely when you finally start XDM.

II. Modify / etc/gdm/custom.conf

Formerly known as

# GDM configuration storage

[xdmcp]

# SuSEconfig: displaymanager:DISPLAYMANAGER_REMOTE_ACCESS

Enable=false

[chooser]

[security]

# SuSEconfig: displaymanager:~DISPLAYMANAGER_XSERVER_TCP_PORT_6000_OPEN

DisallowTCP=true

# SuSEconfig: displaymanager:DISPLAYMANAGER_ROOT_LOGIN_REMOTE

AllowRemoteRoot=false

[debug]

Modify to

# GDM configuration storage

[xdmcp]

# SuSEconfig: displaymanager:DISPLAYMANAGER_REMOTE_ACCESS

Enable=true

Port=177 (optional or not)

[chooser]

[security]

# SuSEconfig: displaymanager:~DISPLAYMANAGER_XSERVER_TCP_PORT_6000_OPEN

DisallowTCP=true (set to TRUE to shut down 6000 and FALSE to open port 6000)

# SuSEconfig: displaymanager:DISPLAYMANAGER_ROOT_LOGIN_REMOTE

AllowRemoteRoot=true

[debug]

The Enable above should be set to ture.

Third, change / etc/X11/xdm/xdm-config and cancel this line (add a!)

! DisplayManager.requestPort: 0

4. Restart xdm

# / etc/init.d/xdm restart

(if the remote server (PC) is not connected to the monitor, it may fail to restart gdm in SSH.)

Or # rcxdm restart

Or # service xdm restart

Fifth, after setting up, you can connect to the server graphically remotely through XMANAGER. But SUSE 11 is a little strange, whether it's ROOT or other users connecting to the server remotely, you can log in directly without verifying your password, so you still need to set security restrictions.

After reading the above, have you mastered the method of sample analysis of suse linux 11 xmanager connection configuration? If you want to learn more skills or want to know more about it, you are welcome to follow the industry information channel, thank you for reading!

Tags: Configuration method server service example analysis content original more port experience problem different security helpless for this one line reason graph password Apple Docker Huawei Linux macOS MariaDB Microsoft MySQL NVidia OPPO Reno Microsoft Linux OPPO Reno Huawei NVidia