WARNING: This e-mail has been altered by MIMEDefang. Following this
paragraph are indications of the actual changes made. For more
information about your site's MIMEDefang policy, contact
[EMAIL PROTECTED] For more information about MIMEDefang, see:
http://www.roaringpenguin.com/mimedefang/
An attachment named sshd.log was removed from this document as it
constituted a security hazard. If you require this document, please contact
the sender and arrange an alternate means of receiving it.
Alternatively zip your attachment and resend.
An attachment named ssh.log was removed from this document as it
constituted a security hazard. If you require this document, please contact
the sender and arrange an alternate means of receiving it.
Alternatively zip your attachment and resend.
An attachment named cygcheck.log was removed from this document as it
constituted a security hazard. If you require this document, please contact
the sender and arrange an alternate means of receiving it.
Alternatively zip your attachment and resend.
W2kpro, sp2
Appears to close the socket immediately after connection.
ssh -v reports "Read from socket failed: Connection aborted"
A log of sshd (thanks to Max's instructions) shows
"Read from socket failed: Resource temporarily unavailable"
Tried deleting cygwin installation and reinstalling. Results attached.
Also tried backdating OpenSSL lib. Still didn't work :-( which suggests that
something else has changed on my system. Likely.
A search of microsoft.com for "Resource temporarily unavailable" yields:
WSAEWOULDBLOCK (10035)
Resource temporarily unavailable.
This error is returned from operations on nonblocking sockets that cannot be
completed immediately, for example recv when no data is queued to be read
from the socket. It is a nonfatal error, and the operation should be retried
later. It is normal for WSAEWOULDBLOCK to be reported as the result from
calling connect on a nonblocking SOCK_STREAM socket, since some time must
elapse for the connection to be established.
The only solution found so far is to completely reinstall W2k,
http://archive.erdelynet.com/ssh-l/2001-05/msg00003.php.
Spurious WSAEWOULDBLOCKs seem to have caused problems when closing sockets
http://www.cygwin.com/ml/cygwin-developers/2001-10/msg00212.html, and
also problems with postgres.
My theory, for what it is worth, is that windows is sending an event saying
that there is something ready to read from a socket, but returns
WSAEWOULDBLOCK when the program reads the socket. I think I read somewhere
in a Microsoft page that programs have to be able to cope with this
situation. It is likely a timing related.
HTH.
Regards
Campbell.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
