Can't figure out why ssh port seems to be blocked

[laredotornado]

Hi,

I'm using Win XP SP 2. I just installed CygWin tools with OpenSSH. I
confirmed everything was installed and configured successfully because
I can run

$ ssh localhost

successfully from the Cygwin window. However, when I try to access
the machine by its IP (which I got from running "ipconfnig" in the Run
-> cmd window)

$ ssh 192.168.199.131
ssh_exchange_identification: Connection closed by remote host

I have turned off Windows firewall settings (just to see if this would
work) but I still get the above error. Any ideas how to troubleshoot
this or how I can unblock SSH? Thanks, - Dave

 

[Paul]

Hi,

I'm using Win XP SP 2. I just installed CygWin tools with OpenSSH. I
confirmed everything was installed and configured successfully because
I can run

$ ssh localhost

successfully from the Cygwin window. However, when I try to access
the machine by its IP (which I got from running "ipconfnig" in the Run
-> cmd window)

$ ssh 192.168.199.131
ssh_exchange_identification: Connection closed by remote host

I have turned off Windows firewall settings (just to see if this would
work) but I still get the above error. Any ideas how to troubleshoot
this or how I can unblock SSH? Thanks, - Dave

You can use Wireshark for debugging networking problems.

http://en.wikipedia.org/wiki/Wireshark

http://www.wireshark.org/download.html

But on an encrypted connection or session, don't expect
to be able to read the payload contents You may be
able to verify though, whether a packet is arriving or not.
If you run Wireshark on both the client machine and the
server machine, you can see a packet leave one machine,
and the same packet arrive at the other machine.

*******

But before doing that, there is one other thing you could try.

For that to work, SSHD probably has to be running on the hosting machine.
It would be listening on a particular port. If the service isn't running,
that may result in the "Connection closed" thing. There is a picture
here, of a CYGWIN flavored SSHD running. I have no idea whether
this is your problem, but it's worth a check.

http://www.ibm.com/developerworks/library/s-ssh/image004.jpg

Just a guess,
Paul