On Wed, 25 May 2005, Boaz Harrosh wrote: > Alexander Gottwald wrote: > > > Maybe ssh -v -v -v wil give you a clue what is happening. > > Right!! try running sshd in a consul in the foreground. (Check what switch > makes it run in the foreground (-d?))
Both -D and -d do (Cygwin's ssh-host-config uses the -D option for the service). -d is much more verbose (into the system log, which by default is the Windows Event Log), and will only accept one connection. > Than see what prints you have. > If this works it is not the end. SYSTEM user is different than the > foreground user, sshd is very picky about permissions been to low or to > high. You can run sshd from a SYSTEM-owned shell (Google for "system owned shell shortcut"). Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ [EMAIL PROTECTED] ZZZzz /,`.-'`' -. ;-;;,_ [EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! "The Sun will pass between the Earth and the Moon tonight for a total Lunar eclipse..." -- WCBS Radio Newsbrief, Oct 27 2004, 12:01 pm EDT