no remote X after upgrades to 9.1/9.2

Joe Georger

4 Jan 2005 4 Jan '05

13:13

I have 2 Opteron machines. Both were running Suse 9.0 amd64. I upgraded one to Suse 9.1 and the other to Suse 9.2. Now I cannot open X applications remotely when using rlogin. I get the "cannot connect to X server" even after using xhost + and setting the DISPLAY env variable on the remote machine. I am aware that ssh -X is preferable - and that does seem to work between my Suse boxes - but not all machines are configured properly as ssh servers. We are behind a firewall here, and we also have some machines on private lans, so if there is a way around this I would like to know. Thanks, Joe

Show replies by date

Rainer Koenig

4 Jan 4 Jan

13:27

New subject: [suse-amd64] no remote X after upgrades to 9.1/9.2

Joe Georger writes:

...

I have 2 Opteron machines. Both were running Suse 9.0 amd64. I upgraded one to Suse 9.1 and the other to Suse 9.2. Now I cannot open X applications remotely when using rlogin. I get the "cannot connect to X server" even after using xhost + and setting the DISPLAY env variable on the remote machine. I am aware that ssh -X is preferable - and that does seem to work between my Suse boxes - but not all machines are configured properly as ssh servers. We are behind a firewall here, and we also have some machines on private lans, so if there is a way around this I would like to know.

First thing I would check is a $ ps `pidof X` In my case this command brings the also the following line: 4849 ? S< 3:39 /usr/bin/X11/X :0 -deferglyphs 16 -nolisten tcp -auth \ /var/lib/gdm/:0.Xauth vt7 The interesting part ist the "-nolisten tcp", that says that the X server doesn't respond to network connections. And I think, ssh -X works because the X forwarding goes via a SSH tunnel and the local X server doesn't notice that a network is involved at all. HTH Rainer -- Dipl.-Inf. (FH) Rainer Koenig Project Manager Linux Fujitsu Siemens Computers VP BC E SW OS Phone: +49-821-804-3321 Fax: +49-821-804-2131

Bernd Paysan

13:28

New subject: [suse-amd64] no remote X after upgrades to 9.1/9.2

On Tuesday 04 January 2005 14:12, Joe Georger wrote:

...

I have 2 Opteron machines. Both were running Suse 9.0 amd64. I upgraded one to Suse 9.1 and the other to Suse 9.2. Now I cannot open X applications remotely when using rlogin. I get the "cannot connect to X server" even after using xhost + and setting the DISPLAY env variable on the remote machine. I am aware that ssh -X is preferable - and that does seem to work between my Suse boxes - but not all machines are configured properly as ssh servers. We are behind a firewall here, and we also have some machines on private lans, so if there is a way around this I would like to know.

Open the /etc/sysconfig-Editor in yast2, and choose Desktop -> Display manager -> DISPLAYMANAGER_XSERVER_TCP_PORT_6000_OPEN Set this to yes. -- Bernd Paysan "If you want it done right, you have to do it yourself" http://www.jwdt.com/~paysan/

Joe Georger

15:50

New subject: [suse-amd64] no remote X after upgrades to 9.1/9.2

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? Thanks, Joe Bernd Paysan wrote:

...

On Tuesday 04 January 2005 14:12, Joe Georger wrote:

...
I have 2 Opteron machines. Both were running Suse 9.0 amd64. I upgraded one to Suse 9.1 and the other to Suse 9.2. Now I cannot open X applications remotely when using rlogin. I get the "cannot connect to X server" even after using xhost + and setting the DISPLAY env variable on the remote machine. I am aware that ssh -X is preferable - and that does seem to work between my Suse boxes - but not all machines are configured properly as ssh servers. We are behind a firewall here, and we also have some machines on private lans, so if there is a way around this I would like to know.

Open the /etc/sysconfig-Editor in yast2, and choose

Desktop -> Display manager -> DISPLAYMANAGER_XSERVER_TCP_PORT_6000_OPEN

Set this to yes.

Andreas Jaeger

16:18

New subject: [suse-amd64] no remote X after upgrades to 9.1/9.2

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 -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

Mike Brown

5 Jan 5 Jan

09:51

New subject: [suse-amd64] no remote X after upgrades to 9.1/9.2

We just ran across this in gdm (gnome) and the fix is likely to be similar for the other display managers. Look in /etc/opt/gnome/gdm/gdm.conf for the setting DisallowTCP=true and set it to false That allowed X to start without "nolisten tcp" Mike On Tue, 2005-01-04 at 10:18, 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

Andreas Jaeger

10:12

New subject: [suse-amd64] no remote X after upgrades to 9.1/9.2

Mike Brown writes:

...

We just ran across this in gdm (gnome) and the fix is likely to be similar for the other display managers.

Look in /etc/opt/gnome/gdm/gdm.conf for the setting DisallowTCP=true and set it to false

That allowed X to start without "nolisten tcp"

If you set the variable DISPLAY_MANAGER_REMOTE_ACCESS and then run SuSEconfig, gdm and kdm should be setup correctly. Btw. this is documented in the 9.1 Release Notes, Andreas

...

Mike

On Tue, 2005-01-04 at 10:18, 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

Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

Mike Brown

17:06

New subject: [suse-amd64] no remote X after upgrades to 9.1/9.2

Thanks Andreas, I went back and reran SuSEconfig by hand to make my preferred change consistent with other display managers. That said, prior to editing the gdm.conf by hand I set the DISPLAY_MANAGER_REMOTE_ACCESS=yes via YAST /etc/sysconfig editor. The setting change was not propagated to the gdm display manager. Mike On Wed, 2005-01-05 at 04:08, Andreas Jaeger wrote:

...

Mike Brown writes:

...
We just ran across this in gdm (gnome) and the fix is likely to be similar for the other display managers.

Look in /etc/opt/gnome/gdm/gdm.conf for the setting DisallowTCP=true and set it to false

That allowed X to start without "nolisten tcp"

If you set the variable DISPLAY_MANAGER_REMOTE_ACCESS and then run SuSEconfig, gdm and kdm should be setup correctly.

Btw. this is documented in the 9.1 Release Notes,

Andreas

...
Mike

On Tue, 2005-01-04 at 10:18, 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

Andreas

Joe Georger

17:12

New subject: [suse-amd64] no remote X after upgrades to 9.1/9.2

Andreas, I did this, and still no luck. This is a 9.2 machine btw. If I do a ps -ex | grep X I notice X is still running with the -nolisten tcp flag.... Thanks, Joe Andreas Jaeger wrote:

...

Mike Brown writes:

...
We just ran across this in gdm (gnome) and the fix is likely to be similar for the other display managers.

Look in /etc/opt/gnome/gdm/gdm.conf for the setting DisallowTCP=true and set it to false

That allowed X to start without "nolisten tcp"

If you set the variable DISPLAY_MANAGER_REMOTE_ACCESS and then run SuSEconfig, gdm and kdm should be setup correctly.

Btw. this is documented in the 9.1 Release Notes,

Andreas

...
Mike

On Tue, 2005-01-04 at 10:18, 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

Andreas

Andreas Jaeger

19:34

New subject: [suse-amd64] no remote X after upgrades to 9.1/9.2

Joe Georger writes:

...

Andreas,

I did this, and still no luck. This is a 9.2 machine btw. If I do a ps -ex | grep X I notice X is still running with the -nolisten tcp flag....

Did you restart X after running SuSEconfig? Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

Joe Georger

6 Jan 6 Jan

15:04

New subject: [suse-amd64] no remote X after upgrade 9.0 to 9.2

Yes, I have been restarting X after every change.... Joe Andreas Jaeger wrote:

...

Joe Georger writes:

...
Andreas,

I did this, and still no luck. This is a 9.2 machine btw. If I do a ps -ex | grep X I notice X is still running with the -nolisten tcp flag....

Did you restart X after running SuSEconfig?

Andreas

Joe Georger

5 Jan 5 Jan

17:09

New subject: [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

Kevin_Gassiot＠veritasdgc.com

7 Jan 7 Jan

14:40

New subject: [suse-amd64] no remote X after upgrades to 9.1/9.2

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 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

Joe Georger

15:37

New subject: [suse-amd64] no remote X after upgrades to 9.1/9.2

Kevin, My Xservers file does not have "nolisten" in it. Got that out a few tries ago. I also checked the firewall and it's all off..... Reboot or restart X? Thanks, Joe Kevin_Gassiot@veritasdgc.com wrote:

...

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 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

Kevin_Gassiot＠veritasdgc.com

16:23

New subject: [suse-amd64] no remote X after upgrades to 9.1/9.2

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 To Kevin_Gassiot@veritasdgc.com 01/07/2005 09:36 cc AM Andreas Jaeger , suse-amd64@suse.com Subject Re: [suse-amd64] no remote X after upgrades to 9.1/9.2 Kevin, My Xservers file does not have "nolisten" in it. Got that out a few tries ago. I also checked the firewall and it's all off..... Reboot or restart X? Thanks, Joe Kevin_Gassiot@veritasdgc.com wrote:

...

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

Joe Georger

18:28

New subject: [suse-amd64] no remote X after upgrades to 9.1/9.2

That did it Kevin. Thanks! Joe Kevin_Gassiot@veritasdgc.com wrote:

...

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 To Kevin_Gassiot@veritasdgc.com 01/07/2005 09:36 cc AM Andreas Jaeger , suse-amd64@suse.com Subject Re: [suse-amd64] no remote X after upgrades to 9.1/9.2

Kevin,

My Xservers file does not have "nolisten" in it. Got that out a few tries ago. I also checked the firewall and it's all off.....

Reboot or restart X?

Thanks, Joe

Kevin_Gassiot@veritasdgc.com wrote:

...
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

7053

Age (days ago)

7056

Last active (days ago)

List overview

Download

15 comments

6 participants

participants (6)

Andreas Jaeger
Bernd Paysan
Joe Georger
Kevin_Gassiot＠veritasdgc.com
Mike Brown
Rainer Koenig