This could be due to service start-up delays. There was discussion on this in last October or thereabouts: exactly what other services sshd should depend on to start reliably. IIRC there were different solutions for different conditions and no universal solution; the failures were caused by TCP/IP or some related part had not properly started yet at the time sshd was attempting to start.
Search the mail archive for more details. Look into your event logs to see if there are differences in the service startup order, especially on the failing machines. //lat -- Klein bottle for rent; enquire within. -- 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/
