It is probably a DNS problem -- if I recall correctly, tcpd will try to do a
reverse lookup on the source of a connection attempt before letting it
complete (even with ALL: ALL set). Check whether you have valid nameserver
entries in /etc/resolv.conf . Connects from the console may be being
validated against /etc/hosts, which would be faster than BIND-based DNS.
Compare a log entry for a remote connect with a local one to see what is
different.
The httpd speed is probably irrelevant. Most likely, httpd runs directly,
not through inetd -- even if you do run it through inetd (rare, but not
unheard of), you are unlikely to be using tcpd with it. As to "other
services like httpd" -- well, other than httpd itself, I don't know what
they are so can't comment.
P.S. html duplication is not customary on this list; for future postings,
please turn this feature of your mailer off.
At 02:17 PM 8/31/99 -0300, Ricardo Cropalato de Melo wrote:
> I am with a strange problem. I am with a RED HAT, that are using a tcpd
to start telnet and ftp daemon. But when some one try to connect with this
services (remotely) is necessarily wait a long time to connect. Other
services like httpd it is not true.
> When the connection is started from the console, is fast. the
hosts.allow is "ALL: ALL", hosts.deny there is no entry.
------------------------------------"Never tell me the odds!"---
Ray Olszewski -- Han Solo
Palo Alto, CA 94303-3603 [EMAIL PROTECTED]
----------------------------------------------------------------
