|
Home > Archive > Red Hat Configuration > January 2004 > xterm 'Can't open display" error
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
xterm 'Can't open display" error
|
|
|
| Hi,
I'm trying to open an xterm process running on a solaris 8 server in a
redhat v. 9 xterm display. Even using xhost +, I get a 'Can't open
display" error.
Xterm works fine from another Sun on the same network as the Sony GRV
550 notebook running redhat. This is a dual-boot config with Windows
XP on another partition. If I boot the same notbook in the same
location to windows and instead use WebtermX, the xterm connection is
also fine. All other web connections in redhat are okay.
I'm thinking there must be something I'm missing about the redhat
config - any hints on what it could be?
Thanks
| |
| Alexander Dalloz 2004-01-23, 7:10 pm |
| umls <umls2003@hotmail.com> wrote:
quote:
> Hi,
>
> I'm trying to open an xterm process running on a solaris 8 server in a
> redhat v. 9 xterm display. Even using xhost +, I get a 'Can't open
> display" error.
> Xterm works fine from another Sun on the same network as the Sony GRV
> 550 notebook running redhat. This is a dual-boot config with Windows
> XP on another partition. If I boot the same notbook in the same
> location to windows and instead use WebtermX, the xterm connection is
> also fine. All other web connections in redhat are okay.
>
> I'm thinking there must be something I'm missing about the redhat
> config - any hints on what it could be?
>
> Thanks
export DISPLAY=:0.0
Alexander
--
Alexander Dalloz | Enger, Germany
PGP key valid: made 13.07.1999
PGP fingerprint: 2307 88FD 2D41 038E 7416 14CD E197 6E88 ED69 5653
| |
| Bit Twister 2004-01-23, 7:10 pm |
| On Wed, 2 Jul 2003 23:28:40 +0200, Alexander Dalloz wrote:quote:
> umls <umls2003@hotmail.com> wrote:
>
>
> export DISPLAY=:0.0
that would be if it was a local connection. It would be
export DISPLAY=Redhat_ip_here:0.0 on the sun box.
User may have X inbound ports blocked in his firewall.
| |
| Bit Twister 2004-01-23, 7:10 pm |
| On 2 Jul 2003 13:41:37 -0700, umls wrote:quote:
> I'm trying to open an xterm process running on a solaris 8 server in a
> redhat v. 9 xterm display. Even using xhost +, I get a 'Can't open
> display" error.
> Xterm works fine from another Sun on the same network as the Sony GRV
> 550 notebook running redhat. This is a dual-boot config with Windows
> XP on another partition. If I boot the same notbook in the same
> location to windows and instead use WebtermX, the xterm connection is
> also fine. All other web connections in redhat are okay.
>
> I'm thinking there must be something I'm missing about the redhat
> config - any hints on what it could be?
I would have to guess it is something in:
the firewall
/etc/hosts.allow
/etc/hosts.deny
because you have indicated, line 4, that you were able to do the same
thing from another Sun box.
This is assuming you can perform the same thing sun to solaris and you
have hard coded the ip address in /etc/hosts for the solaris 8 server.
| |
| Bit Twister 2004-01-23, 7:10 pm |
| On 2 Jul 2003 13:41:37 -0700, umls wrote:quote:
> I'm trying to open an xterm process running on a solaris 8 server in a
> redhat v. 9 xterm display. Even using xhost +, I get a 'Can't open
> display" error.
> Xterm works fine from another Sun on the same network as the Sony GRV
> 550 notebook running redhat. This is a dual-boot config with Windows
> XP on another partition. If I boot the same notbook in the same
> location to windows and instead use WebtermX, the xterm connection is
> also fine. All other web connections in redhat are okay.
>
> I'm thinking there must be something I'm missing about the redhat
> config - any hints on what it could be?
I would have to guess it is something in:
the firewall
/etc/hosts.allow
/etc/hosts.deny
because you have indicated, line 4, that you were able to do the same
thing from another Sun box.
This is assuming you can perform the same thing sun to solaris and you
have hard coded the ip address in /etc/hosts for the solaris 8 server.
| |
| Bit Twister 2004-01-23, 7:10 pm |
| On 2 Jul 2003 13:41:37 -0700, umls wrote:quote:
> I'm trying to open an xterm process running on a solaris 8 server in a
> redhat v. 9 xterm display. Even using xhost +, I get a 'Can't open
> display" error.
> Xterm works fine from another Sun on the same network as the Sony GRV
> 550 notebook running redhat. This is a dual-boot config with Windows
> XP on another partition. If I boot the same notbook in the same
> location to windows and instead use WebtermX, the xterm connection is
> also fine. All other web connections in redhat are okay.
>
> I'm thinking there must be something I'm missing about the redhat
> config - any hints on what it could be?
I would have to guess it is something in:
the firewall
/etc/hosts.allow
/etc/hosts.deny
because you have indicated, line 4, that you were able to do the same
thing from another Sun box.
This is assuming you can perform the same thing sun to solaris and you
have hard coded the ip address in /etc/hosts for the solaris 8 server.
| |
| David Efflandt 2004-01-23, 7:10 pm |
| On 2 Jul 2003 13:41:37 -0700, umls <umls2003@hotmail.com> wrote:quote:
> Hi,
>
> I'm trying to open an xterm process running on a solaris 8 server in a
> redhat v. 9 xterm display. Even using xhost +, I get a 'Can't open
> display" error.
> Xterm works fine from another Sun on the same network as the Sony GRV
> 550 notebook running redhat. This is a dual-boot config with Windows
> XP on another partition. If I boot the same notbook in the same
> location to windows and instead use WebtermX, the xterm connection is
> also fine. All other web connections in redhat are okay.
>
> I'm thinking there must be something I'm missing about the redhat
> config - any hints on what it could be?
Wouldn't it be easier, safer, faster to use X11Forward (and compression)
via ssh (instead of telnet)? Then as long as the ssh can connect, you
would not have to worry about setting DISPLAY or xhost, or opening other
ports.
--
David Efflandt - All spam ignored http://www.de-srv.com/
http://www.autox.chicago.il.us/ http://www.berniesfloral.net/
http://cgi-help.virtualave.net/ http://hammer.prohosting.com/~cgi-wiz/
| |
| David Efflandt 2004-01-23, 7:10 pm |
| On 2 Jul 2003 13:41:37 -0700, umls <umls2003@hotmail.com> wrote:quote:
> Hi,
>
> I'm trying to open an xterm process running on a solaris 8 server in a
> redhat v. 9 xterm display. Even using xhost +, I get a 'Can't open
> display" error.
> Xterm works fine from another Sun on the same network as the Sony GRV
> 550 notebook running redhat. This is a dual-boot config with Windows
> XP on another partition. If I boot the same notbook in the same
> location to windows and instead use WebtermX, the xterm connection is
> also fine. All other web connections in redhat are okay.
>
> I'm thinking there must be something I'm missing about the redhat
> config - any hints on what it could be?
Wouldn't it be easier, safer, faster to use X11Forward (and compression)
via ssh (instead of telnet)? Then as long as the ssh can connect, you
would not have to worry about setting DISPLAY or xhost, or opening other
ports.
--
David Efflandt - All spam ignored http://www.de-srv.com/
http://www.autox.chicago.il.us/ http://www.berniesfloral.net/
http://cgi-help.virtualave.net/ http://hammer.prohosting.com/~cgi-wiz/
| |
| David Efflandt 2004-01-23, 7:10 pm |
| On 2 Jul 2003 13:41:37 -0700, umls <umls2003@hotmail.com> wrote:quote:
> Hi,
>
> I'm trying to open an xterm process running on a solaris 8 server in a
> redhat v. 9 xterm display. Even using xhost +, I get a 'Can't open
> display" error.
> Xterm works fine from another Sun on the same network as the Sony GRV
> 550 notebook running redhat. This is a dual-boot config with Windows
> XP on another partition. If I boot the same notbook in the same
> location to windows and instead use WebtermX, the xterm connection is
> also fine. All other web connections in redhat are okay.
>
> I'm thinking there must be something I'm missing about the redhat
> config - any hints on what it could be?
Wouldn't it be easier, safer, faster to use X11Forward (and compression)
via ssh (instead of telnet)? Then as long as the ssh can connect, you
would not have to worry about setting DISPLAY or xhost, or opening other
ports.
--
David Efflandt - All spam ignored http://www.de-srv.com/
http://www.autox.chicago.il.us/ http://www.berniesfloral.net/
http://cgi-help.virtualave.net/ http://hammer.prohosting.com/~cgi-wiz/
| |
|
| Bit Twister <BitTwister@localhost.localdomain> wrote in message news:<slrnbg9fvp.fg6.BitTwister@wb.home>...quote:
> On 2 Jul 2003 13:41:37 -0700, umls wrote:
>
> I would have to guess it is something in:
> the firewall
> /etc/hosts.allow
> /etc/hosts.deny
> because you have indicated, line 4, that you were able to do the same
> thing from another Sun box.
>
> This is assuming you can perform the same thing sun to solaris and you
> have hard coded the ip address in /etc/hosts for the solaris 8 server.
The way I finally solved this was to edit these files in /etc/X11/xdm:
Xaccess uncommented the + before CHOOSER BROADCAST
xdm-config commented out the last line DisplayManager.requestPort: 0
and then did iptables -F. *Then* x worked like a charm. This is all
probably in a redhat v.9 FAQ somewhere, but it sure would be nice if
it were better publicized.
| |
|
| Bit Twister <BitTwister@localhost.localdomain> wrote in message news:<slrnbg9fvp.fg6.BitTwister@wb.home>...quote:
> On 2 Jul 2003 13:41:37 -0700, umls wrote:
>
> I would have to guess it is something in:
> the firewall
> /etc/hosts.allow
> /etc/hosts.deny
> because you have indicated, line 4, that you were able to do the same
> thing from another Sun box.
>
> This is assuming you can perform the same thing sun to solaris and you
> have hard coded the ip address in /etc/hosts for the solaris 8 server.
The way I finally solved this was to edit these files in /etc/X11/xdm:
Xaccess uncommented the + before CHOOSER BROADCAST
xdm-config commented out the last line DisplayManager.requestPort: 0
and then did iptables -F. *Then* x worked like a charm. This is all
probably in a redhat v.9 FAQ somewhere, but it sure would be nice if
it were better publicized.
| |
|
| Bit Twister <BitTwister@localhost.localdomain> wrote in message news:<slrnbg9fvp.fg6.BitTwister@wb.home>...quote:
> On 2 Jul 2003 13:41:37 -0700, umls wrote:
>
> I would have to guess it is something in:
> the firewall
> /etc/hosts.allow
> /etc/hosts.deny
> because you have indicated, line 4, that you were able to do the same
> thing from another Sun box.
>
> This is assuming you can perform the same thing sun to solaris and you
> have hard coded the ip address in /etc/hosts for the solaris 8 server.
The way I finally solved this was to edit these files in /etc/X11/xdm:
Xaccess uncommented the + before CHOOSER BROADCAST
xdm-config commented out the last line DisplayManager.requestPort: 0
and then did iptables -F. *Then* x worked like a charm. This is all
probably in a redhat v.9 FAQ somewhere, but it sure would be nice if
it were better publicized.
|
|
|
|
|