Windows 10: ssh: connect to host port 22: Connection timed out

I tried to connect my Linux VM from computerwindows with same network but it can't be done. It's shown the result: ssh: connect to host port 22: Connection timed out. how can I get this working? Thanks.

:)

 

SSH problem / windows 10 pro

Hi all,

I can not connect with ssh in my pc.

when I do ssh from another pc in my network it gives me this message :

Permission denied (publickey,password,keyboard-interactive).

from my PC event viewer I find this in SSH operator Logs :

sshd: Connection reset by invalid user pkost 192.168.1.77 port 55388 [preauth]

and with debug in poweshell this:

> sshd -d

debug1: sshd version OpenSSH_for_Windows_8.1, LibreSSL 3.0.2

debug1: get_passwd: LookupAccountName() failed: 1332.

debug1: private host key #0: ssh-rsa SHA256:mgq7hPxSVUFnEJlP2lwcndKRzp6R9tmNiFv0kimesKc

debug1: private host key #1: ecdsa-sha2-nistp256 SHA256:sbRoPIz0aosoYcC/ec6Cdd9WI/t6qHfhph4VFhnS2tQ

debug1: private host key #2: ssh-ed25519 SHA256:3sjen7UpOJGSI8wCK6TtIIpSvKKAp2+zQ37OFtNNilg

debug1: rexec_argv[0]='C:\\Windows\\System32\\OpenSSH\\sshd.exe'

debug1: rexec_argv[1]='-d'

debug1: Bind to port 22 on ::.

Server listening on :: port 22.

debug1: Bind to port 22 on 0.0.0.0.

Server listening on 0.0.0.0 port 22.

and with whoami command S C:\Windows\system32>whoami pkost\pkost

I cannot find where is the problem please help . thank you in advance

 

Connection on local computer to Gitlab server (port 22 and 443)

So I've had this problem before at work, then it was solved by getting a new computer (it was old).

The server is located here on the premises.
Yesterday everything worked fine, this morning I try to surf to the company gitlab and couldn't connect. When I try to clone a repository to my local system I get a port 22: Connection timed out and when I try it with https I get port 443: Timed out

On chrome I get "ERR_CONNECTION_TIMED_OUT"

Edge tells me "There was a temporary DNS error. Try refreshing the page.
Error Code: INET_E_RESOURCE_NOT_FOUND"

I've pinged the ip and I get "Request timed out"

When I run $ ssh -vT git@github.com it gives me a bunch of lines but it ends in

If I run $ ssh -vT git@gitlab.company.com I just get

I've regenerated SSH keys and put them in https://gitlab.com/profile/keys (that I can acces, its just the gitlab.company.com that doesn't work).

I talked to IT at the company and they said nothing has changed, no new firewalls, no nothing.

I did install the Chrome Test Server to start making PWA but removed it after I discovered I had this gitlab problem again thinking it might have to do something with it. I rebooted my pc after the uninstall.

What more can I do? I'm on Windows 10 and run Ubuntu in Oracle VM virtual box (where I can connect just fine).

I've done a system restore to a couple of days ago, didn't help, I logged in a different windows account, still couldn't connect, I've changed network cable (using a coworker his "internet") still doesn't work. There must be something that I'm doing locally that messed things up.

 

ssh and Windows 10 Not Working

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 is that I cannot access the Windows box via ssh (OpenSSH or PuTTY).

I am able to access the Linux box from the Windows box - via ssh (via both OpenSSH and PuTTY).



For the sake of simplicity and in order to eliminate Linux from the equation, I tried:

ssh localhost

ssh 192.168.1.2

ssh HOME



ssh matt@localhost

ssh matt@192.168.1.2

ssh matt@ HOME

(where localhost, 192.168.1.2, and HOME are all the Windows box).

None of those 3 worked - either in PuTTY or in OpenSSH.

I either get:

Connection to localhost closed by remote host.

Connection to localhost closed.



Or I get:

ssh: connect to host 192.168.1.2 port 22: Connection timed out

-

I wanted to make sure that I could access this PC from another in one way or another
- so I went ahead and created a homegroup which this computer and another household Windows 10 (laptop) are part of. That other Windows 10 PC
is able to access this PC (and, for what it's worth, this PC can access the laptop).

Note that a firewall runs on the Windows box. But I get the same results whether it's up or down.

Anyone know what's going on?

TIA, Matt