Solved

telnet respond slowly

Posted on 2001-06-11
7
341 Views
Last Modified: 2013-12-27
I have a solaris2.6 server, in /etc/nsswitch.conf: hosts xfn nisplus,dns,files, then telnet respond slowly; when modified /etc/nsswitch.conf like this: hosts xfn,nisplus,files, then telnet respond quickly. I don't understand why? Please give me directions. thanks.
(BTW, on the other machine(another solaris2.6), use the same dns service, its telnet respond normally.)
0
Comment
Question by:RebeccaYue
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
7 Comments
 
LVL 5

Expert Comment

by:Nisus091197
ID: 6176562
Hi,

The client must determine the IP address of the machine you are telnetting to.  It first looks up the /etc/nsswitch.conf file to see the order in which it should attempt to find the IP.

The fastest way is to put the IPs in the local /etc/hosts file and specify files first in the ordered list.

To make the system run even faster, put the client's IP address into the local /etc/hosts file on the machine you are telnetting to and change its /etc/nsswitch.conf file to specify 'files' first as well.

Regards, Nisus
http://www.omnimodo.com
0
 
LVL 14

Expert Comment

by:chris_calabrese
ID: 6177432
Yes, but in this case it looks like it's not so much that files are faster than DNS (true, but usually not noticable) but rather that one or more DNS servers are down, causing the access to them to timeout before the lookup continues
0
 

Expert Comment

by:arunmozhi
ID: 6185246
Hai,
    I hope you know about name servers and /etc/nsswitch.conf is the file that is useful to decide which resources to be used for determining the ip-address (in your case) .
     Resources may be files,dns,nis,nis+. When you are referring the files it is refers the needed information from the local /etc/ directory . so it will be very fast compare to the remaining resources.
     In case your telnet session is slow is because of the packet forwading by the routers will be slow and because of firewalls installed on both sending and receiving sides.
Check out all these. Changing the order is only based on the environmental needs of the project.
 
0
Get 15 Days FREE Full-Featured Trial

Benefit from a mission critical IT monitoring with Monitis Premium or get it FREE for your entry level monitoring needs.
-Over 200,000 users
-More than 300,000 websites monitored
-Used in 197 countries
-Recommended by 98% of users

 

Expert Comment

by:arunmozhi
ID: 6185248
Hai,
    I hope you know about name servers and /etc/nsswitch.conf is the file that is useful to decide which resources to be used for determining the ip-address (in your case) .
     Resources may be files,dns,nis,nis+. When you are referring the files it is refers the needed information from the local /etc/ directory . so it will be very fast compare to the remaining resources.
     In case your telnet session is slow is because of the packet forwading by the routers will be slow and because of firewalls installed on both sending and receiving sides.
Check out all these. Changing the order is only based on the environmental needs of the project.
 
0
 
LVL 4

Expert Comment

by:jlms
ID: 6214829
You have to know which name services are available for host name resolution in your network.

If you have NIS+ and DNS and host name can be resolved by both means then it is pretty much a matter of trial and error to see which service is faster, keep in mind that a NIS+ server is dealing not only with hosts, but also passwords, groups, netgroups, automounter points and whatever else your sysadmin decides to throw at it. DNS deals with hosts names only, so it should be the preferd method:

hosts: files dns nisplus

Forget about puting stuff in /etc/hosts if you have a big network, it eventualy becomes a nightmare to administer.

You can speed things up a bit by enebling the Name Service cache daemon (nscd). Please check its man page.
0
 
LVL 21

Expert Comment

by:tfewster
ID: 8003142
No comment has been added lately, so it's time to clean up this Topic Area.
I will leave a recommendation for this question in the Cleanup topic area as follows:

- PAQ, no points refunded

Please leave any comments here within the next 7 days

PLEASE DO NOT ACCEPT THIS COMMENT AS AN ANSWER !

tfewster
Cleanup Volunteer
0
 

Accepted Solution

by:
SpideyMod earned 0 total points
ID: 8066008
per recommendation

SpideyMod
Community Support Moderator @Experts Exchange
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

I promised to write further about my project, and here I am.  First, I needed to setup the Primary Server.  You can read how in this article: Setup FreeBSD Server with full HDD encryption (http://www.experts-exchange.com/OS/Unix/BSD/FreeBSD/A_3660-S…
Using libpcap/Jpcap to capture and send packets on Solaris version (10/11) Library used: 1.      Libpcap (http://www.tcpdump.org) Version 1.2 2.      Jpcap(http://netresearch.ics.uci.edu/kfujii/Jpcap/doc/index.html) Version 0.6 Prerequisite: 1.      GCC …
Learn how to find files with the shell using the find and locate commands. Use locate to find a needle in a haystack.: With locate, check if the file still exists.: Use find to get the actual location of the file.:
Learn how to navigate the file tree with the shell. Use pwd to print the current working directory: Use ls to list a directory's contents: Use cd to change to a new directory: Use wildcards instead of typing out long directory names: Use ../ to move…

617 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question