Hi,

I just installed Suse 9.2 on my new AMD 64 box. Everything works fine expect the following problem.

Let say this box name is hostA. I have useA and useB on this box. After I login as userA, I can see the DISPLAY is set to :0.0. I can run any Xwindow application without any problem.

If I run the following command:

xhost +

I can see the message "Access control is disable. All hosts are allowed ". Then I run:

su - userB
OR
sux - userB

I will login as userB (Default shell is bash). Then I set the DISPLAY as

export DISPLAY=hostA:0.0

After this, I can't run any Xwindow application under userB. Everytime I will get this error message:
"Can't connect to X server on Display hostA:0.0"

But if I set DISPLAY=:0.0, then I can run Xapplication.

I have the following question:

1) This makes me can't run any Xwindow application from hostB to hostA. What I means is that if I login as userA on hostA, then ssh to userB on hostB, I can't run any X application on hostB and want the DISPLAY on hostA

2) I never have this problem on Suse 8.x. I disable the fiirewall on Suse 9.2. I think "xhost+" should be enough. Am I wrong?

3) I have another box installed Redhat Enterprise AS 3. I login as userA, then su to userB. No matter which user I login, I don't need to set "xhost +" and "export DISPLAY=". The X application just works. How to configure that on suse 9.2?

Thanks for your kind help!

I am not very familiar with those type of things, but there is this option (disabled per default), that the X server should listen to XDMCP requests. Maybe you need to enable this option in /etc/X11/xdm-config

Here is my xdm-config file under /etc/X11/xdm

Anything wrong? It looks the same as mine Suse 8.1, which I don't have this problem. Any more thoughts?

!
! xdm-config: Configuration of the xdm
!
DisplayManager.errorLogFile: /var/log/xdm.errors
DisplayManager.pidFile: /var/run/xdm.pid
DisplayManager.authDir: /var/lib/xdm
DisplayManager.keyFile: /etc/X11/xdm/xdm-keys
DisplayManager.servers: /etc/X11/xdm/Xservers
DisplayManager.accessFile: /etc/X11/xdm/Xaccess
DisplayManager.willing: su nobody -c /etc/X11/xdm/Xwilling
!
! ATTENTION: `authName' should be in general MIT-MAGIC-COOKIE-1
! For XDM-AUTHENTICATION-1 which is default for xterminals see
! manual page of xdm and the manual coming with the xterminal.
!
DisplayManager.*.authName: MIT-MAGIC-COOKIE-1
DisplayManager.*.authComplain: false
!
! All displays should use authorization, but we cannot be sure
! X terminals will be configured that way, so by default
! use authorization only for local displays :0, :1, etc.
!
DisplayManager._0.authorize: true
DisplayManager._1.authorize: true
!
! The scripts handling the setup, the startup, the session its self,
! and the reset of an X session.
!
DisplayManager.*.setup: /etc/X11/xdm/Xsetup
DisplayManager.*.chooser: /etc/X11/xdm/RunChooser
DisplayManager.*.startup: /etc/X11/xdm/Xstartup
DisplayManager.*.session: /etc/X11/xdm/Xsession
DisplayManager.*.reset: /etc/X11/xdm/Xreset
!
DisplayManager._0.terminateServer: true
!
DisplayManager*resources: /etc/X11/xdm/Xresources
DisplayManager.*.terminateServer: false
!
! SECURITY: do not listen for XDMCP or Chooser requests
! Comment out this line if you want to manage X terminals with xdm
!
DisplayManager.requestPort: 0

As per your now closed thread, this is moved to SuSE.

If I scan my suse 8.2 and redhat linux using nmap, I can see the TCP port 6000 is active for X11. But it is not ture for my Suse 9.2. Is that the reason any x application can't connect to the X server on my Suse 9.2 even I dsiable access control by 'xhost +'?

Where is the port X11 is running on Suse 9.2 now?

Thanks

Finally, I got the answer!

I have to vi the file /etc/X11/xdm/Xservers

The default setting of suse 9.2 is having 'nolisten tcp' into xserver. That's why the remote machine can't connect to xserver no matter the access control you try to set up, because the Xserver is not active on tcp connection.

Why nobody complain this before? I search google.com, suse mailing list and LQF, no luck for all.

You guys don't have another machine and you don't want to run the program remotely on your X window? I know this is maybe a security reason, but it is so inconvenient. It looks like I am the only one complain this.

Any way, find the answer finally and the feeling is great!

I actually had the exact same problem...

For all users with this problem using Gentoo linux

The -nolisten tcp option is set in /usr/X11R6/bin/startx

You should remove that line in the startx file to get it working.

Hey,

I am having the same problem, yet i have changed so many different values, exported variables, tries many different methods of ssh and still... nothing! All i get is the error:
here is what i am trying to do:

I have suse 9.2 on my desktop (192.168.1.103), and suse 8.2 on my web server (192.168.1.111).
I ssh (-X -Y you name it!) to the web server as root, or as user type the following:
or
with the first one, there is no delay between pressing enter and the error message, but with the second one, there is a 5-10 second delay... so am i correct in assuming the latter is the one to use.

I also have been typing:
as user and root, the command fails as root (due to me being logged in as user), but works fine as user.

No matter what files i change, and how many different files i remove "-nolisten tcp" from, it refuses to connect.

I am quite convinced that my desktop (192.168.1.103) is blocking the tcp request for the xserver, so that programs sitting on my webserver will not load up onto my desktop.. for example - i wish to administer suse 8.2 through yast2, while being in suse 9.2... make sense?

I did have xhost working fine between the following:
mandrake 10.0 - mandrake 10.0
mandrake 10.1 - mandrake 10.0
mandrake 10.1 - mandrake 10.1
mandrake 10.1 - suse 8.2
but not any good with
suse 9.2 - suse 8.2

Any help resolving this matter would be fantastic!!!

All i needed to do was have the xserver running on my server.... sounds logical enough! I'll be buggered why i didn't think of that earlier!!!

So now i have ssh and xhost connections working, along with the transportation of x-programs from my server to my desktop!

Thanks guys!!!