You say telnet and pop3 connections take "hours" to start? Do you really
mean that?
If they really take 2 or 3 minutes, rather than an hour or more, then the
difference is probably caused by DNS problems. Specifically:
-- you have inetd set (through tcpd or one of the other tcp wrapper
apps) to do a reverse lookup on any address that telnets or pop3s in -- and
you haven't provided the needed reverse lookup entries, or /etc/hosts
entries, for your dial-in IP addresses. But ...
-- you have your Web server set not to do similar lookups - you have
it logging by address only (a common setup, though I don't know that apache
defaults to it - assuming of course that you use apache).
This is only a guess, and it is based on the assumption that you are
exaggerating the magnitude of the delays. To fix it, all you should need to
do is add the ppp IP addresses to /etc/hosts (or to your named data files if
the server runs named).
If I've assumed wrong, and you really meant "hours", it's probably something
more serious, so please accept my apologies for an incorrect guess.
At 11:58 AM 11/4/99 +0530, Gaurav Agarwal wrote:
> I have got a new problem with my red hat 6 linux server ...
>I have setup my server as a dial in server, where people log into and
>establish ppp connection from their windows machine ...
>Now after i have connected, when i type 192.168.5.3 (that's the ip address
>of my server.) on my browser, i get the correct
>It worked page very quickly.
>though when i use telnet 192.168.5.3 it is taking hours to display the
>prompt ....
>also when i check my mail with my pop3 client (outlook) it waits at the
>connecting and authorising stage for a very very long time.
>( i removed the # sign before pop3 in /etc/inetd.conf file)
------------------------------------"Never tell me the odds!"---
Ray Olszewski -- Han Solo
Palo Alto, CA [EMAIL PROTECTED]
----------------------------------------------------------------
