On Wed, 17 Jan 2007, lonely wolf wrote:
Usually this message is triggered by tcp_wrappers, when the client trying to connect is denied via /etc/hosts.{allow,deny}
I found one error in the remote's /etc/hosts.allow: it did not have colons after the ALL and before the IP address. I fixed that. Still have the same problem. Here's the latest from the remote's /var/log/secure: Jan 18 11:21:42 lemna sshd[5256]: Server listening on :: port 22. Jan 18 11:21:42 lemna sshd[5256]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use. Does this help identify the problem? Rich -- Richard B. Shepard, Ph.D. | The Environmental Permitting Applied Ecosystem Services, Inc. | Accelerator(TM) <http://www.appl-ecosys.com> Voice: 503-667-4517 Fax: 503-667-8863
