I've started trying to use remote X display on my Suse machines, and when all else failed I checked netstat -pantu and found that my Suse 10 box's X doesn't listen on the network.

Why was this made the default , and what configuration file should I edit to fix it?

I have teh same issue on my SuSE 10.0 box.. I am not sure the config file to change this in... I assume that they use by default the tcp -nolisten option when starting X. I am going to do some more hunting on my box and see what else I can find.

Thanks

Chris

Have a look in /etc/X11/xdm/xservers and the README's in the same folder.

Thanks for the input, I did some digging I even turned off the tcp --nolisten option in the recommended displaymanager file. still did not work... Out of desperation yesterday I turned on remote Administration under the YasT control pannel and then everything started working... Odd, that it effects accepting X windows from other X clients.

I wonder what all configuration files that changes I should probably read more into the README you recommended.

Thanks again

Chris

I think the file in question is /etc/sysconfig/displaymanager. Here you find settings like

DISPLAYMANAGER_XSERVER_TCP_PORT_6000_OPEN="no"
DISPLAYMANAGER_REMOTE_ACCESS="no"

I tried changing those values all to "yes" it does not work... there has to be a setting some where else which doesnt really surprise me.

I am a big fan of SuSE, I run 8.2 and 10.0... but Things seem to be much more of a hassle in 10.0. even writing a simple runlevel script is much more a hassle with 10.0 Here is an example I cant just throw a standard bash or sh script in the runlevel and expect it to work (like 8.2) anymore. it has to be in the runlevel format and must be registered with a command. This is another lame "feature"