[SOLVED] Cannot access port 6000 when going to Runlevel 5...
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Cannot access port 6000 when going to Runlevel 5...
Whenever I go into runlevel 5 port 6000 (X) becomes closed. This is preventing me from opening an application window from a remote computer.
This problem goes away when I go back to runlevel 3.
When in runlevel 5 which port is the X server running on, and how do I set my DISPLAY variable on a remote computer (say, remote = 192.168.0.1 and this host with runlevel 5 = 192.168.0.2) so I can open remote windows ? I have tried 192.168.0.2:0, 192.168.0.2:0.0, 192.168.0.2:0.1, 192.168.0.2:0.2 and so on, to no avail.
I would very strongly suggest using X forwarding over SSH. If you do it this way the variables will always be set for you and it will securely suck the UI aspects over a nice SSH tunnel. it should work by default really, but you can ensure X11Forwarding is set to Yes in your own ssh_config.
I would very strongly suggest using X forwarding over SSH. If you do it this way the variables will always be set for you and it will securely suck the UI aspects over a nice SSH tunnel. it should work by default really, but you can ensure X11Forwarding is set to Yes in your own ssh_config.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.