HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Problem with X tunneling, xclock & dtterm work...
Operating System - HP-UX
1825642
Members
4202
Online
109684
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-21-2003 04:33 AM
03-21-2003 04:33 AM
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
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-21-2003 04:42 AM
03-21-2003 04:42 AM
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 .
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 .
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-21-2003 04:42 AM
03-21-2003 04:42 AM
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!!!
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
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP