- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Slow login to HP-UX box through Telnet
Operating System - HP-UX
1752572
Members
4730
Online
108788
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
Discussions
Discussions
Forums
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
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
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
тАО11-09-2007 09:36 AM
тАО11-09-2007 09:36 AM
I have 9 HP9000 boxes running HP-UX 11.11. When I telnet into them it takes a long time for the login prompt to show up. I have no problwems telnetting out of the box. Telnetting between the 9 boxes shows no delays.
Basically there is a several minutes wait to proceed from telnet's connection to displaying the login prompt.
Here is what I see:
$ telnet 10.40.35.10
Trying...
Connected to 10.40.35.10.
Escape character is '^]'.
The wait time is about one minute to one adn a half minutes.
Basically there is a several minutes wait to proceed from telnet's connection to displaying the login prompt.
Here is what I see:
$ telnet 10.40.35.10
Trying...
Connected to 10.40.35.10.
Escape character is '^]'.
The wait time is about one minute to one adn a half minutes.
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-09-2007 09:39 AM
тАО11-09-2007 09:39 AM
Solution
99% of the time this is due to DNS issues.
The server is attempting to reverse lookup your IP address to make an entry in the log. If DNS is not configured correctly the search takes many seconds / minutes. Hence the delay.
Either configure DNS correctly or disable DNS completely.
The server is attempting to reverse lookup your IP address to make an entry in the log. If DNS is not configured correctly the search takes many seconds / minutes. Hence the delay.
Either configure DNS correctly or disable DNS completely.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-09-2007 09:41 AM
тАО11-09-2007 09:41 AM
Re: Slow login to HP-UX box through Telnet
Wow, that was the fastest response ever! I was suspecting DNS. Thanks for confirming my suspicion.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-09-2007 09:45 AM
тАО11-09-2007 09:45 AM
Re: Slow login to HP-UX box through Telnet
Check your /etc/resolv.conf
hosts: files [notfound=continue] dns
A great test is to telnet from the server back to itself. The localhost lookup should be instant.
Even for PCs on the lan that typically do not have DNS hostname entries, if DNS is configured correctly in the environment it should at least return an unknown vs trying to send the resolution up the chain forever and ever.
I have typically seen this where the DNS is run by the Windows folks. They do not set up a reverse lookup domain. They need to at least configure it. Even if they do not plan on having reverse lookups. This way the DNS server will immediately return an unknown or notfound.
hosts: files [notfound=continue] dns
A great test is to telnet from the server back to itself. The localhost lookup should be instant.
Even for PCs on the lan that typically do not have DNS hostname entries, if DNS is configured correctly in the environment it should at least return an unknown vs trying to send the resolution up the chain forever and ever.
I have typically seen this where the DNS is run by the Windows folks. They do not set up a reverse lookup domain. They need to at least configure it. Even if they do not plan on having reverse lookups. This way the DNS server will immediately return an unknown or notfound.
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP