- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- delayed login on a L2000
Operating System - Linux
1752805
Members
5534
Online
108789
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
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
тАО08-06-2001 01:27 PM
тАО08-06-2001 01:27 PM
delayed login on a L2000
I have L2000 server running hpux 11.0, When I added a nameserver to the resolv.conf I started experiencing delayed logins on my server from our remote sites. This happens intermittently, mostly on the first login. We are using kermit95 to telnet to the server but i do not think it is the problem. I have also edited nsswitch.conf and removed the nis lookup but still no go. I could use any idea's you may have to help resolve this problem.
Thanks,
Paul Romanek
Thanks,
Paul Romanek
You Can Have My Unix System When You Pry It From My Cold Dead Fingers!
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-06-2001 02:10 PM
тАО08-06-2001 02:10 PM
Re: delayed login on a L2000
Paul,
The problem is Host lookup. When you telnet to the machine, it tries to resolve your host name. It first tries files, then DNS and NIS if you have it setup that way in the nsswitch.conf file.
You can do 2 things.
1. remove DNS from the "hosts" line in the nsswitch.conf file. The problem with this is that if you're using it for e-mail and other internet stuff, it won't work properly, because it will not use DNS to lookup hostnames.
example:
hosts: files [NOTFOUND=return]# dns nisplus nis
This will check the /etc/hosts file and then quit trying to resolve the hostname. It works.
2. Edit the /etc/hosts file to include all the machines that need to connect to this server.
This may not be entirely practical, but it could be the easiest. Depending on how many workstations are going to connect and if you are using DHCP.
Hope this helps.
John
The problem is Host lookup. When you telnet to the machine, it tries to resolve your host name. It first tries files, then DNS and NIS if you have it setup that way in the nsswitch.conf file.
You can do 2 things.
1. remove DNS from the "hosts" line in the nsswitch.conf file. The problem with this is that if you're using it for e-mail and other internet stuff, it won't work properly, because it will not use DNS to lookup hostnames.
example:
hosts: files [NOTFOUND=return]# dns nisplus nis
This will check the /etc/hosts file and then quit trying to resolve the hostname. It works.
2. Edit the /etc/hosts file to include all the machines that need to connect to this server.
This may not be entirely practical, but it could be the easiest. Depending on how many workstations are going to connect and if you are using DHCP.
Hope this helps.
John
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-07-2001 11:43 AM
тАО08-07-2001 11:43 AM
Re: delayed login on a L2000
You might also try running a traceroute to the IP address of one of those workstations and also to the DNS name. See if the times or route paths differ. If they do, then your DNS server is either slow to respond or is causing a different route path to be followed.
There are 10 types of people in the world, those who understand binary and those who don't - Author Unknown
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-16-2001 02:09 PM
тАО08-16-2001 02:09 PM
Re: delayed login on a L2000
1. Try reverse lookup on the remote servers to see if there is any delay.
2. On the server try both nslookup and lookups on the remote servers
2. Check your name server to see if itself is able to resolve the remote systems.
A pure DNS problem.
-Sri
2. On the server try both nslookup and lookups on the remote servers
2. Check your name server to see if itself is able to resolve the remote systems.
A pure DNS problem.
-Sri
You may be disappointed if you fail, but you are doomed if you don't try
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