Windows 10: Weird SSH issue with WSL2 and WSL1

Hello all,


So this is something that has been bugging me for a while now.


I have this situation where I connect using SSH: My_Computer --SSH-> ServerA --SSH-> ServerB

The connection to ServerA is done with public key auth, and the connection from ServerA to ServerB is regular username/password.


For some strange reason, whenever I use WSL2 with an Ubuntu image the default over the Windows Store, I never get to connect to ServerB. I successfully connect from my computer to ServerA with my key and from there the moment I input "ssh username@serverB" I immediately get the error "ssh_exchange_identification: Connection closed by remote host", like instantly, which is very weird, as I assume the segment ServerA -> ServerB doesn't have much to do with WSL2, especially since the first connection from my computer running WSL2 to ServerA works perfectly fine.


I can replicate this issue on several computers and always with WSL 1 and 2.

Using any other solution, like Putty, SolarPutty, SnowflakeSSH, actual Ubuntu VM using Hyper-V/Virtualbox/VMWare works perfectly fine all the way up to ServerB.


Can anyone shed any light into this?



Thanks.

:)

 

WSL2 will be generally available in Windows 10 version 2004

Source: https://devblogs.microsoft.com/comma...-version-2004/

 

New Windows 10 Insider Preview Fast+Skip Build 18980 (20H1) - Sept. 11 Insider

Hi folks

WSL2 breaks running any GUI programs you had working with WSL1 -- seen some suggestions on Google but I'll wait until some more people have played with it -- seems there's a problem with accessing the display properly due to generated IP addresses -- but I'm not fiddling with that any more.

Running Ubuntu LTS on WSL1 with lightweight LXDE desktop works - some GUI programs run as they do if you install the KDE desktop.

WSL2 breaks the whole kybosh -- but for running command line scripts and non GUI executables it seems fine (WSL2) . You need to install an X-server on windows and use the XLaunch icon on your desktop before starting the Linux GUI -- also you'll need to export DISPLAY=0:0 before using your command on wsl to launch the GUI e.g startlxde. (Lxde is s super dooper lightweight desktop gui which is good for testing if the thing works --you can install more heavyweight stuff once you've got the X-Server working properly.

OK WSL isn't meant to be a complete Linux desktop distro or a fully endowed virtual machine - but what's wrong in testing these things to their limits !!!!

What is nice is you can reset or switch your Linux distro to WSL1 or WSL2 back and forth without having to re-install your distro -- you can also set the default WSL level -- I'd keep the default at 1 until WSL2 is a bit more commonly used -- most things (non GUI) that work on WSL1 will probably work on WSL2 -- file manager is good on WSL2 and you can natively access Linux file systems (with long file names too !!!!!) over a LAN or even attached to the Windows machine. The Windows machine is simply another server as far as WSL2 is concerned.

Cheers
jimbo

 

AMD FX OC'ers Club

That's what the auto setting will do since you're over the 1333 mark it jumps to the next step which isn't listed or officially supported I assume by that ram.

At this point though I would suggest dropping the multi one step or .5 so that we can get something stable and possibly take the heat issue out of the picture for now.