>Have you checked the name server entries in /etc/resolv.conf? DNS >problems are often tracked down to this point.
Yes, I have. I've got three entries in there. One is the local host entry as I'm running BIND. The other two are DNS Servers of my upstream provider. All here should be okay.... I'm thinking there must be some problem with reverse name lookups or something. I'm no expert in this area, but what else can it be? Routing is definitely not a problem. Running "ping" before trying the telnet session returns "immediate" responses. Connecting from some remote hosts is no problem, otheres there is..... Is this lookup necessary? Is there a way to disable it? Later, Kevin Traas Baan Business Systems Systems Analyst Langley, BC, Canada [EMAIL PROTECTED] (604) 882-8169 >> >Debian 1.3.1 sports a who which many are saying is "slow" while others >> >are saying the slowness is due to slow named servers. Were there >> >any notable changes leading up the the /usr/bin/who which came with >> >shellutils 1.16-2? >> >> I've been experiencing problems with some people telnetting into my system. >> Many people don't have a problem, but others do.... The problem is that the >> telnet client says "connected"; however, there is no response from my system >> for 150 seconds - 2.5 minutes! Once the client finally gets the response, >> everything is fine from there. No more delays, no more problems. >> >> Putting the client IP/hostname into /etc/hosts resolves this problem; >> however, this is an impractical solution. >> >> Any ideas? -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
