>>>>> "J" == Jeremy Porter <jerry@fc.net> writes:
J>
J> Actually I found the problem. It wasn't a dns lookup issue at
J> all, at least with the portmasters. It happened to be a coincidence
J> that the machines in question were running TCP mappers and the
J> DNS was not setup for the portmaster (i.e. IN-ADDR and A records).
J>
J> The error message dispalyed by the portmaster was less than
J> helpful. If I had been able to tell that it was refusing
J> connections that would have been one thing.
J>
J> An error message index indicating what the message means
J> would be helpful, or some way to get a diagnostic on the error.
Technically, your system was accepting the TCP connection. It's just
that after a short delay, TCP wrappers was closing the connection
because of the misconfigured DNS. As far as the portmaster is
concerned, this is a perfectly valid connection.
- --
Jeffrey C. Ollie
Iowa Network Services System Administrator
-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
Comment: Processed by Mailcrypt 3.4beta, an Emacs/PGP interface
iQCVAwUBMHmAepwkOQz8sbZFAQFfTgQA5OQTfx9KjC9tqIH2IMvo7R8Wv3/rirpx
owe6Qa/5LpbVfoPWsfuvC3YIp6HIgux+sw2kNnCt+R8FG+F/LkHb1mTspJdySkQK
nbFSh5rr0hvpuURgY7Po7ozWuQPXH8ipxveCeHRBV6yIzkh3W0IgkilTCfZ2qUCP
hxLXdJDVrQQ=
=Fnf6
-----END PGP SIGNATURE-----