Share via

Windows 11 ssh broken

Anonymous
2022-08-24T12:57:19+00:00

Hi I have recently updated to windows 11 and I am unable to use ssh to control my server anymore. Putty keeps giving me Network error: Connection timed out. I'm assuming it has closed ports, specifically 22 but netstat in cmd didn't give me any information and I'm still unable to access my server. I started a new outbound rule for putty but still times out. Literally out of ideas and can't roll back, so I have a £1000 brick. Any help appreciated

Windows for home | Windows 11 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

6 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2022-08-24T18:38:53+00:00

    I just got ssh working yesterday on a clean install of Windows 11 after some thrashing. It does work. This is possibly a config difference that tends to happen. In fact, it worked as smoothly in Windows 11 as Windows 10 previously. With SSH, config differences can be a good amount of brain work :)

    You can debug on the Windows 11 machine itself which I find the easiest since you can connect through the network the same and it makes things easier to get it working that way first.

    PowerShell: ssh -v -p PORT USERNAME@IP ie ssh -v -p 22 foo@192.168.1.100

    That will show ssh connection debug info and you can see all of what's actually going on. If it works then it will log you into SSH. Then you can simply duplicate it on the other system. Outside of that then it would be a firewall or router issue as it should otherwise work on other systems if the above works.

    But, if that doesn't work then you have a ssh configuration issue. The issues there are the ssh config in the ssh folder and the user .ssh folder stuff.

    Was this answer helpful?

    6 people found this answer helpful.
    0 comments
  2. Anonymous
    2022-08-24T15:27:42+00:00

    No I can ping the router but when I ping the server nodes I get destination host unreachable. I don't think there's an issue with the Ubuntu server as it confirmed it is listening on port 22. I have also changed my ip address but that didn't help either. Any ideas? Bitvise just gave me the error code 10060

    Was this answer helpful?

    0 comments
  3. Anonymous
    2022-08-24T15:20:37+00:00

    Ok so you can't ping the server either? Do you know if the server has an IP whitelist setup?

    Kind Regards,

    Elise

    Was this answer helpful?

    0 comments
  4. Anonymous
    2022-08-24T15:03:29+00:00

    Hi Elise thanks for the reply. The server is at home and I would usually just use putty an ssh client to connect. I have now tried switching network connections on as they were down. I have also tried ipconfig commands in command like renew and flushdns but it's still not receiving my ping

    Was this answer helpful?

    0 comments
  5. Anonymous
    2022-08-24T14:55:22+00:00

    Hi, I'm Elise, and I'd be happy to help with your issue.

    Outbound connections are not usually blocked by Windows firewall, could you give some further information on where the server is located and how you route to this from your PC?

    Kind Regards,

    Elise

    Was this answer helpful?

    0 comments