Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Message-ID:	<B56392D22C80D411AF7900508BDC91450C5085@maestro.in.aventail.com>
From:	Gil Markham <gmarkham AT aventail DOT com>
To:	"'cygwin AT sources DOT redhat DOT com'" <cygwin AT sources DOT redhat DOT com>
Subject:	getpeername problem on NT?
Date:	Wed, 4 Oct 2000 14:11:14 -0700
MIME-Version:	1.0
X-Mailer:	Internet Mail Service (5.5.2650.21)

I recently posted about having problems with sshd on NT.  After further
testing with inetd and all of the other network daemons I've found that my
problem appears to be somehow related to getpeername.  When connecting to
any of the network daemons I initially connect fine and then I get an error
message like:

getpeername: The descriptor is a file, not a socket

I can't imagine that I'm the only one to ever run into this.  Is there some
configuration or something that needs to be done before using any of these
daemons?  

I've already went through every combination of user privledges, CYGWIN
variables WinNT service setups etc. I could think of or have found in the
mailing list archives.

Thanks,
Gil Markham

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -