> '/var/log/sshd.log'. But it will be empty if nothing noteworthy > has occurred. If you want to see more chatter, add a new service entry > to run sshd with debug flags. You can grab the details for how to set up > a sshd service from '/bin/ssh-host-config' but the basics are: > > /usr/bin/cygrunsrv -I sshd_debug -d "CYGWIN Debug sshd" -p /usr/sbin/sshd -a > "-D -d -d -d" -y tcpip -u cyg_server -w <your cyg_server password here> > > The three "-d" flags are the important part. To start this service, use: > > /usr/bin/cygrunsrv -S sshd_debug > > This will need to be restarted with each connection attempt. Also, you > should stop your regular sshd service while running this so they don't > conflict. > > /usr/bin/cygrunsrv -E sshd > > Apologies for typos. > > -- > Larry
Tried the debug launch, this is the log for a failed connection: http://pastebin.com/3WyrhdXq So it looks like the client is closing the connection (I think). It seems it cannot find /dev/tty, even though it is there and it has the rights to access it. What I find very strange is that there's a different behavior from the command line and when launched from an application. The command is exactly the same :( _____________ Costin Caraivan -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple