Thanks Jim, On Thursday 03 November 2005 02:35, Jim Cunning wrote:
On Wed, 2005-11-02 at 02:02, Peter Sutter wrote:
I have problems in accessing some SuSE V9.2 systems remotely. A
X -query system :port
works with all those X servers that were originally running SuSE 8.2 and were upgraded to SuSE 9.2; it fails to connect to all systems on which SuSE 9.2 was installed from scratch.
What baffles me, is that if I choose xdm as the display manager on the server, it works, if I choose kdm as display manager, it doesn't. Where does the difference in behaviour come from? The display manager settings in YaST is on all systems exactly the same, /etc/sysconfig/diaplaymanager is identical, as is /etc/X11/xdm/xdm-config.
Are you trying to login as root? What value are you using for ":port"? Note that it isn't really a port you're specifying on the command line, but a display number. Presuming you're already running X locally on display :0.0, you need to specify :1 or greater to succeed.
Yes, I use the local display so I have to set the display > 0.
Also verify that /etc/sysconfig/displaymanager has at least:
DISPLAYMANAGER_REMOTE_ACCESS="yes"
This is so.
and, if you're trying to login as root (not recommended):
DISPLAYMANAGER_ROOT_LOGIN_REMOTE="yes"
This is so too
Then, be sure you've run "SuSEconfig" and restarted KDM any time either of these values is changed. Changing them inside yast2 with /etc/sysconfig editor, probably doesn't restart KDM when you exit yast, because that would essentially pull the rug from under your feet, unless you do it from a virtual console. I'm not sure KDM actually is restarted when you logout and login from KDE. The best way to restart KDM is login as root from a virtual console (Ctrl-Alt-F1 - F6), and enter "telinit 3" followed by "telinit 5"
Switching runlevel does not help.
You can tell KDM is listening for X queries by running "netstat -an" and looking for port 177. You won't see it before restarting KDM and should see it afterward.
I will check that when I am back in the office. The DISPLAYMANAGER... settings must be correct, as it works with DISPLAYMANAGER xdm, but not with kdm. It is only when the default is kdm that it does not work, all other displaymanagers work. There must be a difference in the configuration files for kdm between systems that begun as SuSE 8.2 systems and got upgraded to SuSE 9.2 vs. systems that were SuSE 9.2 was installed from scratch. But where?
I am running 9.1, but I suspect 9.2 is similar.
-- Jim Cunning <jcunning@cunning.ods.org>