GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- telnet slow or not responding
Operating System - HP-UX
1847009
Members
4149
Online
110258
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
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
06-01-2002 01:35 PM
06-01-2002 01:35 PM
telnet slow or not responding
I have install ux 11.11 with DNS and a gateway outside. so I can ftp to any site and af course telnet.
But when I telnet a local host name, the respond is unknow host. I have create /etc/nsswitch.conf file with "hosts:files" but now a can't telnet outside the network. It is a problem with DNS and the rest.
But I want use then both.
But when I telnet a local host name, the respond is unknow host. I have create /etc/nsswitch.conf file with "hosts:files" but now a can't telnet outside the network. It is a problem with DNS and the rest.
But I want use then both.
Jos de Ruiter
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-01-2002 01:53 PM
06-01-2002 01:53 PM
Re: telnet slow or not responding
You need to modify your /etc/nsswitch.conf file so that both files and dns will be used. The hosts line should look something like this:
hosts: files [NOTFOUND=continue] dns
This can be modified on the fly, no reboot or anything else is required. Just modify the file, save it, and you should be good to go.
hosts: files [NOTFOUND=continue] dns
This can be modified on the fly, no reboot or anything else is required. Just modify the file, save it, and you should be good to go.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-01-2002 02:50 PM
06-01-2002 02:50 PM
Re: telnet slow or not responding
Hi Jos
A little expansion on Patrick's reply
The entry in nsswitch is related to as the 'fall back mechanism'
When you send a query to the lookup resource always yields one of 4 results
SUCCESS - source found requested entry
UNAVAIL - Source is not configured
NOTFOUND - source responded "no such entry"
TRYAGAIN - server not responding
When the resolver receives one of these responses you can configure it to react in 2 ways
continue - Try the next source in the list
return - quit searching
Lets say we have the following in /etc/nsswitch
hosts: dns files
The above says that the resolver should try DNS first - SUCCESS = return else use the /etc/hosts files
As per Patrick's example - he is more explicitly defining the fallback mechanism
hosts : files [NOTFOUND=continue] dns
With the above entry , if the host is not found using /etc/hosts then the resolver will consult dns
If these actions are not specified the resolver uses the following defaults
SUCCESS=return
NOTFOUND=return
UNAVAIL=continue
TRYAGIN=continue
Therefore the UNAVAIL and TRYAGAIN lines ensure that the other specified resource is used
Hope this helps
Steve
A little expansion on Patrick's reply
The entry in nsswitch is related to as the 'fall back mechanism'
When you send a query to the lookup resource always yields one of 4 results
SUCCESS - source found requested entry
UNAVAIL - Source is not configured
NOTFOUND - source responded "no such entry"
TRYAGAIN - server not responding
When the resolver receives one of these responses you can configure it to react in 2 ways
continue - Try the next source in the list
return - quit searching
Lets say we have the following in /etc/nsswitch
hosts: dns files
The above says that the resolver should try DNS first - SUCCESS = return else use the /etc/hosts files
As per Patrick's example - he is more explicitly defining the fallback mechanism
hosts : files [NOTFOUND=continue] dns
With the above entry , if the host is not found using /etc/hosts then the resolver will consult dns
If these actions are not specified the resolver uses the following defaults
SUCCESS=return
NOTFOUND=return
UNAVAIL=continue
TRYAGIN=continue
Therefore the UNAVAIL and TRYAGAIN lines ensure that the other specified resource is used
Hope this helps
Steve
take your time and think things through
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
Events and news
Customer resources
© Copyright 2026 Hewlett Packard Enterprise Development LP