Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-ID:	<000301c524d4$87607740$6402a8c0@humphrey>
From:	=?iso-8859-1?Q?Frank_W=FCbbeling?= <wuebbel AT math DOT uni-muenster DOT de>
To:	<cygwin AT cygwin DOT com>
Subject:	sshd/Mcafee revisited
Date:	Wed, 9 Mar 2005 19:19:25 +0100
MIME-Version:	1.0

Yesterday, I was troubled by the sshd/McAfee-Problem that was already 
reported several times here.

In short: On the server, there's McAfee and sshd installed as a service. 
After reboot, sshd service is started, but every access from outside gives 
"ssh_exchange_identification: Connection closed by remote host". Restarting 
the service repairs the problem until next reboot.

In some contributions here McAfee was blamed for the problem, delaying the 
sshd start until after McAfee start helped, some proposed to use rebaseall 
instead. Maybe somebody who was also struck with this is interested to hear 
that I had to do both: Neither helped by itself, but using rebaseall once 
*and* delaying the service actually worked.

I am not claiming that I remotely understand why this worked. If this was a 
"rebase"-problem, I would not have expected a service restart to solve it... 
Well, I don't care. Works.

Frank 


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -