On Wed, 29 Jun 2016, ?ngel Gonz?lez wrote:> On 29/06/16 22:57, Wallace Forman wrote: >> I used the latest version from here: >> >> http://www.mls-software.com/opensshd.html >> >> On my other (Windows 10) machine (on which openssh works), I have cygwin >> installed, but if ssh was using cygwin, I wasn't aware of it. I just ran >> ssh from the command prompt. >> >> Wallace Forman > > Yes, that ssh server is cygwin-based. It is however including the basic > cygwin files it needs, so the fact that it actually doesn't work without a > normal cygwin install seems a bug in the package.I wasn't really paying attention but the first thing I thought of was this sounds like the problem I usually see when my shell is broken. Can you log into the account using the console? -- Hisashi T Fujinaka - htodd at twofifty.com BSEE + BSChem + BAEnglish + MSCS + $2.50 = coffee
Embarrassing to say, I'm really not sure what constitutes a "console" or "shell". To explain what does and does not seem to be working: 1) I have two windows computers on the same wireless network, both with openssh for windows installed from the link previously sent. 2) On computer 1, sshd is running, but when connecting with "ssh localhost" from the command prompt on that same computer, sshd seems to be accepting the password, but closing immediately (see output in previous messages). 3) On computer 2, sshd runs, and I can connect on that computer from the command prompt or from putty. 4) When I try to connect from computer 2 to computer 1 (from putty or command prompt), the session closes immediately, as when I try to connect from Computer 1. 5) Also, Computer 2 does not seem to be accepting the password input from computer 1. Haven't really tried to troubleshoot this yet, perhaps this is an sshd_config issue. Wallace Forman 913-669-4453 On Wed, Jun 29, 2016 at 11:23 PM, Hisashi T Fujinaka <htodd at twofifty.com> wrote:> On Wed, 29 Jun 2016, ?ngel Gonz?lez wrote: > > On 29/06/16 22:57, Wallace Forman wrote: >> >>> I used the latest version from here: >>> >>> http://www.mls-software.com/opensshd.html >>> >>> On my other (Windows 10) machine (on which openssh works), I have cygwin >>> installed, but if ssh was using cygwin, I wasn't aware of it. I just ran >>> ssh from the command prompt. >>> >>> Wallace Forman >>> >> >> Yes, that ssh server is cygwin-based. It is however including the basic >> cygwin files it needs, so the fact that it actually doesn't work without a >> normal cygwin install seems a bug in the package. >> > > I wasn't really paying attention but the first thing I thought of was > this sounds like the problem I usually see when my shell is broken. Can > you log into the account using the console? > > -- > Hisashi T Fujinaka - htodd at twofifty.com > BSEE + BSChem + BAEnglish + MSCS + $2.50 = coffee >
On 30/06/16 17:12, Wallace Forman wrote:> Embarrassing to say, I'm really not sure what constitutes a "console" > or "shell".The shell is the program that reads the commands you write and executes them. ssh doesn't run "cd" It handles the secure layer, launches your shell and leaves you to communicate with it however you want. So for instance if your shell is cmd.exe you would list the contents of a folder with "dir", but use "ls" in bash. If after authentication sshd is not able to run your shell (errors reading the user profile, the shell is not executable, etc.), then it closes the connection, as you report.> To explain what does and does not seem to be working: > (?) > > 2) On computer 1, sshd is running, but when connecting with "ssh > localhost" from the command prompt on that same computer, sshd seems > to be accepting the password, but closing immediately (see output in > previous messages).You can verify whether it is really accepting the password by entering a wrong one.> > 4) When I try to connect from computer 2 to computer 1 (from putty or > command prompt), the session closes immediately, as when I try to > connect from Computer 1.This is the same as #2 Regards