At 22:27 07-06-99 -0700, Ray Olszewski wrote:
>Well ... without knowing more about your system, I can only guess at the
>reason. But here are some possibilities.
>
>1. If you have the typical system configuration, your Web server (httpd) is
>running and even has spare processes running (you can check this with "ps
>-ax |grep http"), while telnet and ftp are managed through inetd . This
>difference *by itself* won't account for the large speed difference you are
>seeing, but it will explain a small difference. (ping, BTW, is in kernel
>code; it should be immediate.) But if your system *also* is low on memory or
>has a slow hard disk, that could slow the inetd-managed processes down even
>more. Try running "free" to see if you have enough real (not swap) memory to
>start up new processes easily.
>
>2. Your system also probably uses tcpd to enforce access restrictions on
>inetd-managed services. Depending on how you have tcpd configured (read
>"man 5 hosts_access" for details here), it too can slow things down.
>
>3. In particular, if you have tcpd configured to verify host identities via
>DNS, a bad DNS configuration (or simply a slow nameserver) could be causing
>your problem.
>
>To say more, I'd need to know the details of your hardware, your inetd
>configuration, typical system load, how the host gets DNS information, and
>your tcpd configuration.
>
>BTW, I did confirm your observations - http access took 10 seconds, telnet
>70 seconds. I also tried to telnet to port 25 (smtp - answered by sendmail)
>and it took about 30 seconds to respond. This too seems slow. Are you
>running sendmail through inetd (not usual, but not all that odd)? If not,
>this suggests that system load or name service may be the problem, rather
>than inetd-specific configuration problems. But even here, the details matter.
ok, after more than a month of late nights, hundreds of
re-installs/re-compilations, much sweat and hairloss :-), i finally got the
system going as it should. all i did was include the dns server's ip
address in a file called /etc/networks. the connection speed is now almost
instantanoeus when telnet'ing or ftp'ing to my system.
get this though, after all was running as it should, just out of curiosity
i removed the dns server's ip address from the /etc/networks file but the
connection remained quick. i reinstalled the whole system again but didn't
touch the /etc/networks file, i only added the dns server ip address to
/etc/hosts and the trouble began again (long connect times). i then added
the dns server ip address to the /etc/networks file and connection times
were almost instantaneous again via telnet and ftp. i again removed the dns
ip address from /etc/networks but the connection times remained almost
instantaneous. why is that so? it is as if the system only needed to read
the /etc/networks file once to get going and then no more.
thanks to everyone who replied to my original request for help, i really
appreciate it and thought i'd let you know how it all turned out. muchas
gracias.
-rick
>
>At 10:30 PM 6/7/99 -0600, Ricardo Denis wrote:
>>i have a computer connected to the internet 24 hours a day. why is it that
>>if i try to telnet or ftp to it, it takes about 1 minute and 40 seconds for
>>the computer to respond whereas if i http to it (or ping it) it responds
>>almost instantaneously? if you�d like to try and see what i mean then the
>>ip is 206.48.106.72. i run SuSE 5.3. thanks for any help.
>
>------------------------------------"Never tell me the odds!"---
>Ray Olszewski -- Han Solo
>762 Garland Drive
>Palo Alto, CA 94303-3603
>650.328.4219 voice [EMAIL PROTECTED]
>----------------------------------------------------------------
>
