Symptom: sshd disconnects immediately after connection, logging error
message "Read from socket failed: Resource temporarily unavailable". This is
apparently caused by windows returning status code WSAEWOULDBLOCK, which is
what it does if you attempt to do a non-blocking read when there is no data
Sorry: Forgot about our overenthusiastic attachment defanger.
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 unavai
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.c
3 matches
Mail list logo