Operating System - HP-UX
1825642 Members
4202 Online
109684 Solutions
New Discussion

Re: Problem with X tunneling, xclock & dtterm works but not hpterm or xterm

 
Thomas Lindholm
Occasional Contributor

Problem with X tunneling, xclock & dtterm works but not hpterm or xterm

Hi,

I'm having problem using SSH and xterm on a HPUX 11 box.
Tunneling is on and xclock or dtterm works fine, just pops up.
Whenever I try to start xterm or hpterm I get the following error message:

$ xterm
Xlib: connection to "localhost:13.0" refused by server
Xlib: SSH gateway: X11 authentication failed.
Error: Can't open display: localhost:13.0
Error: Couldn't find per display information

I have tried to change the attributes for $HOME/.Xauthority and also to set the XAUTHORITY variabel in the shell but nothing works.

Would be very glad if someone knows what happends.

Regards
Thomas
- http://thomaz.se
2 REPLIES 2
T G Manikandan
Honored Contributor

Re: Problem with X tunneling, xclock & dtterm works but not hpterm or xterm

To provide permission to a certain machine permanently,
create a file called X0.hosts file in the /etc directory.
Enter the hostname of the local machine and any remote machine you would want to have permission.

check for the man pages of Xserver .
Thomas Lindholm
Occasional Contributor

Re: Problem with X tunneling, xclock & dtterm works but not hpterm or xterm

Hmm... Maybe was a little bit quick there.
Found an answer from Rick Beldin in a older message:

X11R5 clients will have problems with SSH because of the built-in way that X111R5's XOpenDisplay() tries to be 'smart' about the transport. Depending on the format of the DISPLAY variable, XOpenDisplay() will try different methods of creating the socket connections. The form of localhost:n will force it to use Unix sockets, which ssh is not listening to. There is a somewhat vague note in the ssh release notes about this. X11R6 clients do not have this limitation.

To correct this, modify the sshd_config on the HP-UX side to have the following entry:

X11UseLocalhost no

This will force the remote DISPLAY name to be of the form
ip-address:10. XOpenDisplay() from R5 thinks that this refers to a remote connection and xterm, xclock and other R5 clients will then start to work.


This works fine!!!
- http://thomaz.se