Windows 10, Debian and ssh Problem

Summary:
There are two desktop computers in my home:
One running Debian Linux and one running Windows 10.

They both access the Web through a wireless router (Verizon).

The issue:

  1. I cannot use ssh from the Linux box in order to access the Windows box.
    AND NOTE: That I can use ssh from the Windows box in order to access the Linux box.

  2. In further ‘testing’, I cannot use ssh from the Windows box in order to access the Windows box.
    AND NOTE: That I can use ssh from the Linux box in order to access the Linux box.

o I’ve tried ssh from OpenSSH and also from PuTTY with the same results.
o A firewall runs on the Windows box. But I get the same results whether it’s up or down.
o I’ve tried both the IP address and the hostname.
o As a side note, the Linux box hosts an Apache Web server - which all of the household desktops successfully access.

++++++++++++++++++++++++++++++++++++
From Linux trying to get to Windows:
++++++++++++++++++++++++++++++++++++

OpenSSH:

<1 of 2> ssh matt@HOME
ssh: connect to host home port 22: No route to host

<2 of 2>> ssh [email protected]
ssh: connect to host 192.168.1.2 port 22: No route to host

PuTTY (ssh)

(Using HOME and 192.168.1.2)
No route to host

*****> Note that Linux-to-Linux works using both OpenSSH and PuTTY.

++++++++++++++++++++++++++++++++++++++++
From Windows trying to get to Windows:
++++++++++++++++++++++++++++++++++++++++

OpenSSH (from a DOS shell):

<1 of 2> C:\Windows\System32>ssh 192.168.1.2
ssh: connect to host 192.168.1.2 port 22: Connection timed out

<2 of 2> C:\Windows\System32>ssh HOME

USAGE WARNING

This is a private computer system. This computer system, including all
related equipment, networks, and network devices (specifically including

constitutes consent to monitoring for these purposes.

matt@home’s password:
Connection to home closed by remote host.
Connection to home closed.

PuTTY (ssh)

  1. With IP -
    Network error: Connection timed out
  2. With HOME -
    Server unexpectedly closed network connection

*****> Note that Windows-to-Linux works using both OpenSSH and PuTTY.

.
.
.
.
.
Anyone know what’s going on?
TIA, Matt

I didn’t think Windows had an ssh server without third party software ?

I’m really not sure.
However, ssh (whether OpenSSH or via PuTTY) does work on this Windows OS/Desktop as long as I am going out to the Linux OS/Desktop.
So, server or no, I’d still like to get into the Windows box.
For example, “ssh localhost” would suffice.

And, below, I am uncertain why it is referring to /home/matt/.ssh on Windows.
Shouldn’t it be C:\Users\matt.ssh?

C:\Windows\System32>ssh -vvv localhost
OpenSSH_7.2p1, OpenSSL 1.0.2g 1 Mar 2016
debug1: Reading configuration data /etc/ssh_config
debug2: resolving “localhost” port 22
debug2: ssh_connect_direct: needpriv 0
debug1: Connecting to localhost [::1] port 22.
debug1: Connection established.
debug1: key_load_public: No such file or directory
debug1: identity file /home/matt/.ssh/id_rsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/matt/.ssh/id_rsa-cert type -1
debug1: key_load_public: No such file or directory
.
.
.

ssh work via a SERVER ↔ CLIENT setup … as far as I know, Windows has a client out of the box, but no server.

If you’ve installed OpenSSH, have you allowed it through the firewall ?

Really this is a Windows problem, not a Linux one … it would probably be best dealt with on a Windows forum :wink:

“o A firewall runs on the Windows box. But I get the same results whether it’s up or down.”

Thanks. The first step was to ascertain that it was a Windows issue and it looks like it is.
No surprise there - my Linux OS works, but my Windoze OS doesn’t ! :wink:

Guess I’ll spend some time looking for a Windows forum.
Any suggestions?

No idea mate, but googling “ssh server on windows” might turn up something.