UBUNTU HYPERTERM SWITCH WORKSPACE INSTALL

If I will need to reinstall newly installed OS for such stupid problem, I won't install Win11 back. I can't find any official KB for the same behavior.

I'm getting paranoid, does anyone have any idea before I will have to reinstall the OS? I take this as the very last option, since it is one month old clean installation on formatted SSD, and I am always keeping my OS as clean as possible, avoiding any SW which is not necessary, or rarely used. How is it possible that any server is reachable (so routing, connection all is ok) using a putty client, but ssh doesn't work using cmd, powershell, or wls linux? Interesting is also that Hyper terminal worked few days, after the issue occurred in wls, but not any more. Firewall reset to defaults (although it is the same when turned off)

UBUNTU HYPERTERM SWITCH WORKSPACE DRIVER

I've tried already LAN cable connection to rule out wifi-card's driver I am unable to SSH neither any internal guest VMs, before I was always able to ssh any VM on virtualbox, but atm I can see the same behavior, ping works, ncat can communicate with the port, but SSH timeouts It simply doesn't work only within host OS Win 11. SSH works also from guest Win10 (VM in vbox on the same laptop), it works well using cmd, power shell etc. The issue became more interesting when I found out that it works well when using putty, for the same servers, ports etc. As first I was suspecting a Win firewall as root cuase, but the issue was always present also when firewall disabled I found out the same behavior in cmd, and power-shell

It was working as first which is weird because I ran into the same behavior after few days As first I've tried 3rd-party Hyper Terminal. ncat works - I can open port 22, or custom ssh port e.g. All worked well for months on Win10 also on Win11 and I was happy, because linux console and built-in features work for me betterĪfter some time, ssh to a remote server stopped working within a wls linux. Previously I was using Ubuntu deployed in wls 2.0 (earlier on Win10 and now Win11) also for SSH-ing any remote servers, or internal VMs (vbox machines), among other things. Maybe I am missing something, but can't find a reason of the behavior bellow: I am posting this, sine I am running out of ideas.

Ubuntu hyperterm switch workspace