Quote:
Originally Posted by theNbomr
Could there be other firewalls or ISP's intervening? X traffic is ordinarily sent on port 6000 for server :0. Have you tried the (better) option of using SSH with an X tunnel? On some setups, X runs with the -nolisten tcp option. SSH tunneling gets around this.
|
Hi Rod.
Thanks for the suggestion. As it turned out, it was an issue with the login manager (kdm, in my case). By default it does not allow any incoming TCP connection. Letting kdm allow it should solve the problem. The only remaining issue is, I have to figure out how to enable that with kdm. With gdm, I can set
DisallowTCP to false, which probably gets rid of the "-nolisten tcp" option you mentioned above. I temporarily switched to use gdm for now. I will go back to kdm once I figure out how to enable that option there.
I agree that "ssh -X" would be a better alternative. Unfortunately, most of our UNIX hosts do not have ssh running.
[EDIT] Okay, I figured that out... In
kdmrc, the kdm config file, there's a line that says:
Code:
ServerArgsLocal=-nolisten tcp
All I had to do was remove that line and restart X.
Again, thanks for your help.
Dai