Re: Windows XP and OpenSSH problem...

From: Pierre Asselin (pa_at_see.signature.invalid)
Date: 01/25/05


Date: Tue, 25 Jan 2005 01:51:42 +0000 (UTC)

Matthew O Donnell <News1234@matthewodonnell.co.uk> wrote:
> Hi, hoping someone can help me with a OpenSSH problem. I have managed to
> get OpenSSH up and running and can succesfully connect to my Windows XP
> Pro machine from any machine I like.

> The problem is that everytime I reboot I must start up a command prompt
> and stop the service (net stop opensshd) and then restart the
> service(net start openssh) otherwise I get an

> ssh_exchange_identification: connection closed by remote host

> error. I get this even when I attempt to connect to localhost.

Interesting. My Win2k computer at work has the same symptoms...
and didn't use to ! I could reboot and the sshd service (Cygwin,
in my case) would restart normally. Now I have to net stop sshd
and net start it again like you do.

Not sure when the change occurred, maybe two or three months ago.
I'm completely in the dark as to the *cause* of the change.

> Is there
> any way around this, because it can be annoying if my machine at home is
> rebooted when I am away as I can no longer connect.

No kidding.

Would a batch script work ? How do you get a script to run
after every reboot ? How do you say "sleep 180" in Windowsish ?

-- 
pa at panix dot com


Relevant Pages

  • login disabled during reboot
    ... I am using openssh on Linux. ... Today I had to reboot my server because ... I upgraded the Kernel and there I found out, that if the Server wont let ... I used the correct Username/Password, ...
    (comp.security.ssh)
  • Re: login disabled during reboot
    ... Today I had to reboot my server ... > Login incorrect ... It depends on the version of openssh you use, ...
    (comp.security.ssh)
  • Windows XP and OpenSSH problem...
    ... hoping someone can help me with a OpenSSH problem. ... get OpenSSH up and running and can succesfully connect to my Windows XP ... The problem is that everytime I reboot I must start up a command prompt ...
    (comp.security.ssh)