> > You can solve the problem by adding the ip and *any* hostname to /etc/hosts
> > on the box you're connecting to. This wil allow the IP to be resolved (even
> > if wrongly...). (This solution won't for my situation - thus my
> > headline/cry-for-help above)
It looks to me (though I could
On Fri, 20 Mar 1998, Kevin Traas wrote:
> The reason for the problem is that telnet (and ftp, etc.) try to do a
> reverse name lookup on the IP address of the incoming connection. There are
> lots of ways to get around this problem, but I've idea on how to stop this
> lookup from happening.
>
>
On Fri, 20 Mar 1998, Kevin Traas wrote:
> >Is there a reason why I can't telnet normally to the router?
> >I don't get a login prompt when I first connect but only after 3 or
> >more minutes? even if a "ps -ex" show that in.telnetd is there
> Actually, it's 150 seconds - or 2.5 minutes - how
I don't know, but it seems there would be a way to set the 150 second
timeout to something else -- if nothing else, modifying the kernel.
john
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
>Is there a reason why I can't telnet normally to the router?
>I don't get a login prompt when I first connect but only after 3 or
>more minutes? even if a "ps -ex" show that in.telnetd is there
Actually, it's 150 seconds - or 2.5 minutes - however you look at it.
The reason for the problem
5 matches
Mail list logo
