Activated Built-In SSH on Windows 10 - How To SSH In Though?

Feb 14, 2018
32
0
40
I know my machine IP and I've tried every username combination but cannot get it to connect.
I went to command prompt and typed "whoami" and below is what I saw:

C:\Users\ajaze\whoami
desktop-upm0eqg\ajaze

I tried the username as:
desktop-upm0eqg
upm0eqg
desktop-upm0eqg/ajaze
ajaze

I tried all combinations but it doesn't work. What I'm tying to ssh in is:

ssh <username>@<IP>

I know ssh is working on Windows 10 because when I type 'ssh' in the command prompt, it brings up the commands list. So can it only be used to ssh out and not in? or am I missing something?
 
Solution
If your mining rig is running a Pro or Enterprise version of Windows you can use the native Remote Desktop app. Teamviewer works too. Have a look at the resource usage with teamviewer or RDP. I think you'll find it's extremely small. It will tend to hit the CPU, if anything, and mining (I would imagine) is not really tapping your CPU that hard anyway is it?
Just don't log in and log out, that uses system resources. If you're just connecting to an already logged-in user account the resource hit is very small.
Are you using the "built-in" Windows SSH client? The one referred to in this article: https://www.howtogeek.com/336775/how-to-enable-and-use-windows-10s-built-in-ssh-commands/

That is an SSH client. That means you use your Windows 10 machine to connect to another machine that is running an SSH server, like a linux machine or a managed network equipment. If you want to connect from another machine to your Windows 10 host, you need to install an SSH server on the Windows host. Windows isn't really set up well for this though.

What are you wanting to do remotely on your Windows box? SSH works great on linux, but for Windows there are probably better to do whatever it is you are trying to do.
 
Ahh ok that makes sense. I did install the ssh client + ssh server but I guess it's not working how I expected.
Basically I've built a mining rig and I want a way to remotely connect to the rig and check status in real time and then if necessary make adjustments/reboot. I could use teamviewer I guess but my concern is that teamviewer can bump up the cpu/mem usage, which may add to the instability of mining with Windows.

I chose ssh because I think it's lightweight and won't take much system resources to keep connected.
 
If your mining rig is running a Pro or Enterprise version of Windows you can use the native Remote Desktop app. Teamviewer works too. Have a look at the resource usage with teamviewer or RDP. I think you'll find it's extremely small. It will tend to hit the CPU, if anything, and mining (I would imagine) is not really tapping your CPU that hard anyway is it?
Just don't log in and log out, that uses system resources. If you're just connecting to an already logged-in user account the resource hit is very small.
 
Solution
Yeah mining creates 1-2% CPU usage on my Intel Pentium G4400. I will try teamviewer, keep it logged in and see how I go. Will report back once I've tested it thoroughly. Thanks.
 
Quick update - I've managed to get smOS working so won't be continuing with Windows 10 as smOS was always my preferred choice of system. Therefore didn't get to test teamviewer load but I'm sure you're right, it would be fine providing it's logged in already.