I think I had to actually reboot the machine - just restarting X didn't
work.... It's been a while since I ran into this, and I haven't set one up
from scratch for a while. We are still running SuSE 9.0 in production, I
just have a couple of boxes that I am loaded 9.1 and 9.2 with to test back
before the holidays...
Kevin Gassiot
Advanced Systems Group
Visualization Systems Support
Veritas DGC
10300 Town Park Dr.
Houston, Texas 77072
832-351-8978
kevin_gassiot@veritasdgc.com
Joe Georger
Find the files that have the "nolisten tcp" string in them : smut:/ # find / -exec grep -H nolisten {} \;
On both SuSE 9.1 and 9.2, I had to change the file /etc/opt/kde3/share/config/kdm/Xservers to get rid of the -nolisten tcp line for display :0 I think I had to reboot for it to take effect...
smut:/ # cat /etc/opt/kde3/share/config/kdm/Xservers # Xservers - local X-server list # # This file should contain an entry to start the server on the # local display; if you have more than one display (not screen), # you can add entries to the list (one per line). # If you also have some X terminals connected which do not support XDMCP, # you can add them here as well; you will want to leave those terminals # on and connected to the network, else kdm will have a tougher time # managing them. Each X terminal line should look like: # XTerminalName:0 foreign #
# use such a line to enable the console login option in the kdm menu #:0 local@tty1 /usr/X11R6/bin/X vt7 # "reserve" means that the X server gets only started on request (only kdm)
---> :0 local /usr/X11R6/bin/X -br vt7 :1 local reserve /usr/X11R6/bin/X -nolisten tcp -br :1 vt8 :2 local reserve /usr/X11R6/bin/X -nolisten tcp -br :2 vt9 :3 local reserve /usr/X11R6/bin/X -nolisten tcp -br :3 vt10 :4 local reserve /usr/X11R6/bin/X -nolisten tcp -br :4 vt11 :5 local reserve /usr/X11R6/bin/X -nolisten tcp -br :5 vt12
You might also have to turn off the firewalls that were turned on by default after the install...
chkconfig --list | grep -i firewal chkconfig SuSEfirewall2_final off chkconfig SuSEfirewall2_init off chkconfig SuSEfirewall2_setup off
Kevin Gassiot Advanced Systems Group Visualization Systems Support
Veritas DGC 10300 Town Park Dr. Houston, Texas 77072 832-351-8978 kevin_gassiot@veritasdgc.com
Joe Georger
edu> To
Andreas Jaeger
01/04/2005 11:35 cc
AM suse-amd64@suse.com
Subject
Re: [suse-amd64] no remote X after
upgrades to 9.1/9.2
That was set to "no" - I changed it to "yes" and restarted X. Same problem....
Andreas Jaeger wrote:
Joe Georger
writes: I spoke too soon..... The following worked for my 9.1 box but did not work for my 9.2 box. On the latter I also tried to removed the -nolisten tcp flag in /etc/X11/xdm/Xservers file for display 0 but that didn't work either. Any other ideas?
Did you check: /etc/sysconfig/displaymanager: DISPLAYMANAGER_REMOTE_ACCESS
Andreas
-- Check the List-Unsubscribe header to unsubscribe For additional commands, email: suse-amd64-help@suse.com
-- Check the List-Unsubscribe header to unsubscribe For additional commands, email: suse-amd64-help@suse.com