Linux - Security This forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here. |
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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
|
07-28-2004, 04:08 PM
|
#1
|
LQ Newbie
Registered: Oct 2003
Posts: 10
Rep:
|
can't open display (SuSE 9.1)
Hello,
I am having trouble with a new SuSE 9.1 install.
I am familure with xhost and xauth for use with remote display.
I am getting errors from my local host and remote machines when I try to export my DISPLAY.
Here is what I am doing.
Local host: ifconfig shows local host is 10.170.8.1
xhost +
ssh -l system 10.170.8.2
export DISPLAY=10.170.8.1:0
xclock
Error: Can't open display: 10.170.8.1:0
even when I just go to root on localhost, the only way it works is when I
export DISPLAY=:0
export DISPLAY=10.170.8.1:0 gets error.
Please help!
Thank you!
Brian
Last edited by userbr; 07-28-2004 at 04:18 PM.
|
|
|
07-28-2004, 08:02 PM
|
#2
|
Member
Registered: Sep 2002
Location: .at
Distribution: SuSE, Knoppix
Posts: 532
Rep:
|
check /etc/sysconfig/displaymanager
find:
DISPLAYMANAGER_XSERVER_TCP_PORT_6000_OPEN="no"
and change to:
DISPLAYMANAGER_XSERVER_TCP_PORT_6000_OPEN="yes"
|
|
|
07-29-2004, 02:51 PM
|
#3
|
LQ Newbie
Registered: Oct 2003
Posts: 10
Original Poster
Rep:
|
Although this was a good tip, this did not fix my issue. I did change this parameter and even rebooted just in case, still the same issue.
Are there any logs I could look at to see if I get a better idea of what is blocking me from exporting my DISPLAY?
Thanks again,
Brian
|
|
|
07-30-2004, 06:56 PM
|
#4
|
Member
Registered: Sep 2002
Location: .at
Distribution: SuSE, Knoppix
Posts: 532
Rep:
|
Do you have SUSEFIREWALL2 running ?
if yes:
Probably you should check "/etc/sysconfig/SuSEfirewall2"
FW_PROTECT_FROM_INTERNAL="yes"
to
FW_PROTECT_FROM_INTERNAL="no"
or modify
FW_SERVICES_INT_XXX
to allow X11
|
|
|
08-02-2004, 02:26 PM
|
#5
|
LQ Newbie
Registered: Oct 2003
Posts: 10
Original Poster
Rep:
|
It still is not working.
If X11 is listening shouldn't netstat -peat show it?
This is my netstat -peat
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name
tcp 0 0 *:5801 *:* LISTEN root 4519 2838/xinetd
tcp 0 0 *:5901 *:* LISTEN root 4518 2838/xinetd
tcp 0 0 *:sunrpc *:* LISTEN root 2494 1640/portmap
tcp 0 0 *:ipp *:* LISTEN root 4532 2488/cupsd
tcp 0 0 localhost:smtp *:* LISTEN root 4042 2621/master
tcp 0 0 *:ssh *:* LISTEN root 3110 2058/sshd
tcp 0 0 localhost:smtp *:* LISTEN root 4043 2621/master
|
|
|
08-02-2004, 03:22 PM
|
#6
|
LQ Newbie
Registered: Oct 2003
Posts: 10
Original Poster
Rep:
|
Ok! Finally figured it out.
All I did was go into Yast and it said my monitor wasn't setup. It was setup during install as a VESA basic monitor.
I set it up to my monitor's specs and restarted X and it works fine.
Does anyone know why it didn't find the montior during setup of 9.1 (8.2 found it fine before).
Also, why would that matter, as long as it had a valid display, it at least still work, right?
Thanks for all of your assistance, keep up the good work!!!
Brian
|
|
|
08-31-2004, 02:30 AM
|
#7
|
LQ Newbie
Registered: Aug 2004
Posts: 2
Rep:
|
Hi,
I seem to have the same problem, however, the hints supplied didn't work for me. I'm still trying to figure it out, but I learned a couple of lessons along the way. Note: I am running gdm and gnome, which is not the default for Suse.
1) The graphical yast2 does not have an option for shutting down the firewall completely. Switch to console mode and try yast2 there. All the sudden "disable firewall" was there again
2) netstat -peat really shows the listening X server, you should see a line like the following:
tcp 0 0 *:6000 *:* LISTEN root 9921 4576/X
3) setting DISPLAYMANAGER_XSERVER_TCP_PORT_6000_OPEN=yes didn't have any effect for me, i.e. the open port did not show up with netstat.
4) here's a workaround if you need to get up a display for your favourite headless server:
- go to console mode
- log in as root
- execute "init 3"
- log out and in as user
- execute "startx gnome"
Cheers!
Andy
|
|
|
All times are GMT -5. The time now is 06:31 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|