Can't connect via SSH from WIndows 10











up vote
1
down vote

favorite












I'm trying to connect to another device on my local network: 192.168.0.55 with Putty. I can do it fine from one computer but another does not work. The one that does not work is running Windows 10 and only has the built in firewall and Windows Defender installed. This is the error message I get



error message



I tried adding rules to the Windows firewall to allow incoming and outgoing connections on port 22 but it didn't make a difference. It used to work fine.










share|improve this question


























    up vote
    1
    down vote

    favorite












    I'm trying to connect to another device on my local network: 192.168.0.55 with Putty. I can do it fine from one computer but another does not work. The one that does not work is running Windows 10 and only has the built in firewall and Windows Defender installed. This is the error message I get



    error message



    I tried adding rules to the Windows firewall to allow incoming and outgoing connections on port 22 but it didn't make a difference. It used to work fine.










    share|improve this question
























      up vote
      1
      down vote

      favorite









      up vote
      1
      down vote

      favorite











      I'm trying to connect to another device on my local network: 192.168.0.55 with Putty. I can do it fine from one computer but another does not work. The one that does not work is running Windows 10 and only has the built in firewall and Windows Defender installed. This is the error message I get



      error message



      I tried adding rules to the Windows firewall to allow incoming and outgoing connections on port 22 but it didn't make a difference. It used to work fine.










      share|improve this question













      I'm trying to connect to another device on my local network: 192.168.0.55 with Putty. I can do it fine from one computer but another does not work. The one that does not work is running Windows 10 and only has the built in firewall and Windows Defender installed. This is the error message I get



      error message



      I tried adding rules to the Windows firewall to allow incoming and outgoing connections on port 22 but it didn't make a difference. It used to work fine.







      windows-10 ssh firewall putty






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Jul 19 at 6:56









      northerner

      5542613




      5542613






















          2 Answers
          2






          active

          oldest

          votes

















          up vote
          0
          down vote



          accepted










          First, outbound SSH traffic does not use port 22, it is being redirected to port 22. By default, it chooses a port from the dynamic range. And also, you need no rules for outbound SSH connections, unless such connections are explicitly blocked by the firewall. A network connection will be established via stateful connection tracking (supported by almost any modern firewall, read more here).

          You shouldn't be worried for your outbound connection ports at all.



          Reasons why you might experience that behaviour:





          1. PuTTY isn't in the list of allowed applications in the firewall -- it is not allowed to establish connections.

          2. Depending on how you've added it, your rule might also not work. A bug on some versions on Windows (most commonly Windows 7) is seen, where a firewall rule will not work if the allowed path contains variables (like %username%). If PuTTY is allowed in the firewall, but still not able to connect, then make sure you don't have a path with variables and make sure PuTTY is just located on an absolute path without those. An example of this bug can be found here.


          3. PuTTY might need administrator rights to create a socket, from TCP/IP Raw Sockets:


            Raw sockets offer the capability to manipulate the underlying transport, so they can be used for malicious purposes that pose a security threat. Therefore, only members of the Administrators group can create sockets of type SOCK_RAW on Windows 2000 and later.





          A quick guide for allowing applications through the firewall:
          Windows 10: Allow/Block Apps in Windows Firewall






          share|improve this answer























          • "you need no rules for outbound SSH connections" ... unless the firewall is configured to block such connections...
            – Attie
            Jul 19 at 11:21










          • @Attie then you remove that rule, not add a new one :)
            – Fanatique
            Jul 19 at 11:22










          • Unless its a wider rule that happens to catch SSH connections too :)
            – Attie
            Jul 19 at 11:23










          • Well, you are right. In a corporate network that might be more common. I'll add that case.
            – Fanatique
            Jul 19 at 11:29










          • The GROK link is no longer working.
            – Bonzo
            Dec 3 at 22:05


















          up vote
          0
          down vote













          I'm fairly certain that outgoing SSH connections aren't on port 22 - otherwise how would you be able to have outgoing SSH connection on a computer that also runs SSH server?



          Rather than opening ports, you should try adding putty.exe to the list of allowed applications. Also check if your remote device is not blocking the connections with firewall or if the SSH server in that device is still running.






          share|improve this answer





















            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "3"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1341418%2fcant-connect-via-ssh-from-windows-10%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            2 Answers
            2






            active

            oldest

            votes








            2 Answers
            2






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            0
            down vote



            accepted










            First, outbound SSH traffic does not use port 22, it is being redirected to port 22. By default, it chooses a port from the dynamic range. And also, you need no rules for outbound SSH connections, unless such connections are explicitly blocked by the firewall. A network connection will be established via stateful connection tracking (supported by almost any modern firewall, read more here).

            You shouldn't be worried for your outbound connection ports at all.



            Reasons why you might experience that behaviour:





            1. PuTTY isn't in the list of allowed applications in the firewall -- it is not allowed to establish connections.

            2. Depending on how you've added it, your rule might also not work. A bug on some versions on Windows (most commonly Windows 7) is seen, where a firewall rule will not work if the allowed path contains variables (like %username%). If PuTTY is allowed in the firewall, but still not able to connect, then make sure you don't have a path with variables and make sure PuTTY is just located on an absolute path without those. An example of this bug can be found here.


            3. PuTTY might need administrator rights to create a socket, from TCP/IP Raw Sockets:


              Raw sockets offer the capability to manipulate the underlying transport, so they can be used for malicious purposes that pose a security threat. Therefore, only members of the Administrators group can create sockets of type SOCK_RAW on Windows 2000 and later.





            A quick guide for allowing applications through the firewall:
            Windows 10: Allow/Block Apps in Windows Firewall






            share|improve this answer























            • "you need no rules for outbound SSH connections" ... unless the firewall is configured to block such connections...
              – Attie
              Jul 19 at 11:21










            • @Attie then you remove that rule, not add a new one :)
              – Fanatique
              Jul 19 at 11:22










            • Unless its a wider rule that happens to catch SSH connections too :)
              – Attie
              Jul 19 at 11:23










            • Well, you are right. In a corporate network that might be more common. I'll add that case.
              – Fanatique
              Jul 19 at 11:29










            • The GROK link is no longer working.
              – Bonzo
              Dec 3 at 22:05















            up vote
            0
            down vote



            accepted










            First, outbound SSH traffic does not use port 22, it is being redirected to port 22. By default, it chooses a port from the dynamic range. And also, you need no rules for outbound SSH connections, unless such connections are explicitly blocked by the firewall. A network connection will be established via stateful connection tracking (supported by almost any modern firewall, read more here).

            You shouldn't be worried for your outbound connection ports at all.



            Reasons why you might experience that behaviour:





            1. PuTTY isn't in the list of allowed applications in the firewall -- it is not allowed to establish connections.

            2. Depending on how you've added it, your rule might also not work. A bug on some versions on Windows (most commonly Windows 7) is seen, where a firewall rule will not work if the allowed path contains variables (like %username%). If PuTTY is allowed in the firewall, but still not able to connect, then make sure you don't have a path with variables and make sure PuTTY is just located on an absolute path without those. An example of this bug can be found here.


            3. PuTTY might need administrator rights to create a socket, from TCP/IP Raw Sockets:


              Raw sockets offer the capability to manipulate the underlying transport, so they can be used for malicious purposes that pose a security threat. Therefore, only members of the Administrators group can create sockets of type SOCK_RAW on Windows 2000 and later.





            A quick guide for allowing applications through the firewall:
            Windows 10: Allow/Block Apps in Windows Firewall






            share|improve this answer























            • "you need no rules for outbound SSH connections" ... unless the firewall is configured to block such connections...
              – Attie
              Jul 19 at 11:21










            • @Attie then you remove that rule, not add a new one :)
              – Fanatique
              Jul 19 at 11:22










            • Unless its a wider rule that happens to catch SSH connections too :)
              – Attie
              Jul 19 at 11:23










            • Well, you are right. In a corporate network that might be more common. I'll add that case.
              – Fanatique
              Jul 19 at 11:29










            • The GROK link is no longer working.
              – Bonzo
              Dec 3 at 22:05













            up vote
            0
            down vote



            accepted







            up vote
            0
            down vote



            accepted






            First, outbound SSH traffic does not use port 22, it is being redirected to port 22. By default, it chooses a port from the dynamic range. And also, you need no rules for outbound SSH connections, unless such connections are explicitly blocked by the firewall. A network connection will be established via stateful connection tracking (supported by almost any modern firewall, read more here).

            You shouldn't be worried for your outbound connection ports at all.



            Reasons why you might experience that behaviour:





            1. PuTTY isn't in the list of allowed applications in the firewall -- it is not allowed to establish connections.

            2. Depending on how you've added it, your rule might also not work. A bug on some versions on Windows (most commonly Windows 7) is seen, where a firewall rule will not work if the allowed path contains variables (like %username%). If PuTTY is allowed in the firewall, but still not able to connect, then make sure you don't have a path with variables and make sure PuTTY is just located on an absolute path without those. An example of this bug can be found here.


            3. PuTTY might need administrator rights to create a socket, from TCP/IP Raw Sockets:


              Raw sockets offer the capability to manipulate the underlying transport, so they can be used for malicious purposes that pose a security threat. Therefore, only members of the Administrators group can create sockets of type SOCK_RAW on Windows 2000 and later.





            A quick guide for allowing applications through the firewall:
            Windows 10: Allow/Block Apps in Windows Firewall






            share|improve this answer














            First, outbound SSH traffic does not use port 22, it is being redirected to port 22. By default, it chooses a port from the dynamic range. And also, you need no rules for outbound SSH connections, unless such connections are explicitly blocked by the firewall. A network connection will be established via stateful connection tracking (supported by almost any modern firewall, read more here).

            You shouldn't be worried for your outbound connection ports at all.



            Reasons why you might experience that behaviour:





            1. PuTTY isn't in the list of allowed applications in the firewall -- it is not allowed to establish connections.

            2. Depending on how you've added it, your rule might also not work. A bug on some versions on Windows (most commonly Windows 7) is seen, where a firewall rule will not work if the allowed path contains variables (like %username%). If PuTTY is allowed in the firewall, but still not able to connect, then make sure you don't have a path with variables and make sure PuTTY is just located on an absolute path without those. An example of this bug can be found here.


            3. PuTTY might need administrator rights to create a socket, from TCP/IP Raw Sockets:


              Raw sockets offer the capability to manipulate the underlying transport, so they can be used for malicious purposes that pose a security threat. Therefore, only members of the Administrators group can create sockets of type SOCK_RAW on Windows 2000 and later.





            A quick guide for allowing applications through the firewall:
            Windows 10: Allow/Block Apps in Windows Firewall







            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited Dec 4 at 12:45

























            answered Jul 19 at 10:58









            Fanatique

            1,8521316




            1,8521316












            • "you need no rules for outbound SSH connections" ... unless the firewall is configured to block such connections...
              – Attie
              Jul 19 at 11:21










            • @Attie then you remove that rule, not add a new one :)
              – Fanatique
              Jul 19 at 11:22










            • Unless its a wider rule that happens to catch SSH connections too :)
              – Attie
              Jul 19 at 11:23










            • Well, you are right. In a corporate network that might be more common. I'll add that case.
              – Fanatique
              Jul 19 at 11:29










            • The GROK link is no longer working.
              – Bonzo
              Dec 3 at 22:05


















            • "you need no rules for outbound SSH connections" ... unless the firewall is configured to block such connections...
              – Attie
              Jul 19 at 11:21










            • @Attie then you remove that rule, not add a new one :)
              – Fanatique
              Jul 19 at 11:22










            • Unless its a wider rule that happens to catch SSH connections too :)
              – Attie
              Jul 19 at 11:23










            • Well, you are right. In a corporate network that might be more common. I'll add that case.
              – Fanatique
              Jul 19 at 11:29










            • The GROK link is no longer working.
              – Bonzo
              Dec 3 at 22:05
















            "you need no rules for outbound SSH connections" ... unless the firewall is configured to block such connections...
            – Attie
            Jul 19 at 11:21




            "you need no rules for outbound SSH connections" ... unless the firewall is configured to block such connections...
            – Attie
            Jul 19 at 11:21












            @Attie then you remove that rule, not add a new one :)
            – Fanatique
            Jul 19 at 11:22




            @Attie then you remove that rule, not add a new one :)
            – Fanatique
            Jul 19 at 11:22












            Unless its a wider rule that happens to catch SSH connections too :)
            – Attie
            Jul 19 at 11:23




            Unless its a wider rule that happens to catch SSH connections too :)
            – Attie
            Jul 19 at 11:23












            Well, you are right. In a corporate network that might be more common. I'll add that case.
            – Fanatique
            Jul 19 at 11:29




            Well, you are right. In a corporate network that might be more common. I'll add that case.
            – Fanatique
            Jul 19 at 11:29












            The GROK link is no longer working.
            – Bonzo
            Dec 3 at 22:05




            The GROK link is no longer working.
            – Bonzo
            Dec 3 at 22:05












            up vote
            0
            down vote













            I'm fairly certain that outgoing SSH connections aren't on port 22 - otherwise how would you be able to have outgoing SSH connection on a computer that also runs SSH server?



            Rather than opening ports, you should try adding putty.exe to the list of allowed applications. Also check if your remote device is not blocking the connections with firewall or if the SSH server in that device is still running.






            share|improve this answer

























              up vote
              0
              down vote













              I'm fairly certain that outgoing SSH connections aren't on port 22 - otherwise how would you be able to have outgoing SSH connection on a computer that also runs SSH server?



              Rather than opening ports, you should try adding putty.exe to the list of allowed applications. Also check if your remote device is not blocking the connections with firewall or if the SSH server in that device is still running.






              share|improve this answer























                up vote
                0
                down vote










                up vote
                0
                down vote









                I'm fairly certain that outgoing SSH connections aren't on port 22 - otherwise how would you be able to have outgoing SSH connection on a computer that also runs SSH server?



                Rather than opening ports, you should try adding putty.exe to the list of allowed applications. Also check if your remote device is not blocking the connections with firewall or if the SSH server in that device is still running.






                share|improve this answer












                I'm fairly certain that outgoing SSH connections aren't on port 22 - otherwise how would you be able to have outgoing SSH connection on a computer that also runs SSH server?



                Rather than opening ports, you should try adding putty.exe to the list of allowed applications. Also check if your remote device is not blocking the connections with firewall or if the SSH server in that device is still running.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Jul 19 at 7:05









                Konrad Botor

                2947




                2947






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Super User!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.





                    Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                    Please pay close attention to the following guidance:


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1341418%2fcant-connect-via-ssh-from-windows-10%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

                    Mangá

                     ⁒  ․,‪⁊‑⁙ ⁖, ⁇‒※‌, †,⁖‗‌⁝    ‾‸⁘,‖⁔⁣,⁂‾
”‑,‥–,‬ ,⁀‹⁋‴⁑ ‒ ,‴⁋”‼ ⁨,‷⁔„ ‰′,‐‚ ‥‡‎“‷⁃⁨⁅⁣,⁔
⁇‘⁔⁡⁏⁌⁡‿‶‏⁨ ⁣⁕⁖⁨⁩⁥‽⁀  ‴‬⁜‟ ⁃‣‧⁕‮ …‍⁨‴ ⁩,⁚⁖‫ ,‵ ⁀,‮⁝‣‣ ⁑  ⁂– ․, ‾‽ ‏⁁“⁗‸ ‾… ‹‡⁌⁎‸‘ ‡⁏⁌‪ ‵⁛ ‎⁨ ―⁦⁤⁄⁕