Windows 10: windows 10 cmdline ssh messed up remotely logged in linux directory

I launched windows 10's cmd line.


C:\Users\vanil>ssh

usage: ssh [-46AaCfGgKkMNnqsTtVvXxYy] [-B bind_interface]

[-b bind_address] [-c cipher_spec] [-D [bind_address:]port]

[-E log_file] [-e escape_char] [-F configfile] [-I pkcs11]

[-i identity_file] [-J [user@]host[ort]] [-L address]

[-l login_name] [-m mac_spec] [-O ctl_cmd] [-o option] [-p port]

[-Q query_option] [-R address] [-S ctl_path] [-W hostort]

[-w local_tun[:remote_tun]] destination [command]


logged into a Ubuntu workstation remotely. The directory of the cmd line is totally messed up:


Get cloud support with Ubuntu Advantage Cloud Guest:

http://www.ubuntu.com/business/services/cloud



* Canonical Livepatch is available for installation.

- Reduce system reboots and improve kernel security. Activate at:

https://ubuntu.com/livepatch


251 packages can be updated.
0 updates are security updates.
Last login: Thu Jun 20 18:22:03 2019 from 24.5.30.160

ls

aconda3-4.4.0-Linux-x86_64.sh anaconda3 cuda-repo-ubuntu1804_10.0.130-1_amd64.deb pytorch

cd pytorch

cpytorch: command not found

cd pytorch

];alla_att@tesla: ~/pytorchvanilla_att@tesla:~/pytorch$


Can anybody provide an idea about it?

:)

 

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

 

Remote desktop client: SSH tunnel

Hi Thanatica... Do you mean use Powershell over SSH? I use this myself all the time to connect to my remote servers.

See link.

To set it up you will need to enable windows remote management on both ends.

Make sure in services.msc the windows remote management service is running. Also in windows firewall make sure port 5986 is enabled.

https://docs.microsoft.com/en-us/powershell/scr...

If the machines you are trying to connect to are on a different domain\subnet you will need to add them to your trusted host list.

See link.

https://docs.microsoft.com/en-us/previous-versi...(v=msdn.10)

 

Can Windows 10 Generate SSH Key-Pairs for SSH Access to Itself?


If the Linux machine is running OpenSSH, it will generate the key for you to log into it from Putty or FTP. If you log into the Windows Machine with FTP, you would need a SSH keygen running on the Windows machine. Both machines cannot generate a separate SSH key for the same session. When the keys get out of sync on the remote system, for what is stored on the computer you are logging into it with. You have to physically go in to the remote machine at its actual keyboard and monitor to reset the Key, so that the Keygen can create the same one.

It works just like when you use a codeword between two people to validate that they are friend or foe. If say the keyword was "Chocolate Ice Cream". But you state "I went to the store to pick up some Vanilla Ice Cream." The reply would be "Not correct". SSH is a way to make sure that the computer trusts those who are logging in via a remote access.