Trouble connecting to Ubuntu server using ssh












0















I been having trouble connecting to my Ubuntu 18.10 server using ssh. Whenever I try to connect with my college network this is the output



    ssh -vvv root@my.server

OpenSSH_7.9p1, OpenSSL 1.1.1a 20 Nov 2018
debug1: Reading configuration data /home/tintin/.ssh/config
debug1: Reading configuration data /etc/ssh/ssh_config
debug2: resolve_canonicalize: hostname my.server.ip is address
debug2: ssh_connect_direct
debug1: Connecting to my.server.ip [my.server.ip] port 22.
debug1: Connection established.
debug1: identity file /home/tintin/.ssh/id_rsa type 0
debug1: identity file /home/tintin/.ssh/id_rsa-cert type -1
debug1: identity file /home/tintin/.ssh/id_dsa type -1
debug1: identity file /home/tintin/.ssh/id_dsa-cert type -1
debug1: identity file /home/tintin/.ssh/id_ecdsa type -1
debug1: identity file /home/tintin/.ssh/id_ecdsa-cert type -1
debug1: identity file /home/tintin/.ssh/id_ed25519 type -1
debug1: identity file /home/tintin/.ssh/id_ed25519-cert type -1
debug1: identity file /home/tintin/.ssh/id_xmss type -1
debug1: identity file /home/tintin/.ssh/id_xmss-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_7.9


And then it completely hangs and nothing else appears. I tried using other ports like 443, 80 but with no better result than the previous one. I even tried to reboot the server but with no results again.



This is the telnet output



   telnet my.server.ip 22

Trying my.server.ip...
Connected to my.server.ip.
Escape character is '^]'.
SSH-2.0-OpenSSH_7.7p1 Ubuntu-4ubuntu0.1
Connection closed by foreign host.


But there's no problem connecting to the server from other networks. Is there any way to connect to my server using this college network?



Edit:
As far as I could gather while surfing the net for this problem is that the problem basically resides in the network. So is there anyway to bypass this security feature ?










share|improve this question





























    0















    I been having trouble connecting to my Ubuntu 18.10 server using ssh. Whenever I try to connect with my college network this is the output



        ssh -vvv root@my.server

    OpenSSH_7.9p1, OpenSSL 1.1.1a 20 Nov 2018
    debug1: Reading configuration data /home/tintin/.ssh/config
    debug1: Reading configuration data /etc/ssh/ssh_config
    debug2: resolve_canonicalize: hostname my.server.ip is address
    debug2: ssh_connect_direct
    debug1: Connecting to my.server.ip [my.server.ip] port 22.
    debug1: Connection established.
    debug1: identity file /home/tintin/.ssh/id_rsa type 0
    debug1: identity file /home/tintin/.ssh/id_rsa-cert type -1
    debug1: identity file /home/tintin/.ssh/id_dsa type -1
    debug1: identity file /home/tintin/.ssh/id_dsa-cert type -1
    debug1: identity file /home/tintin/.ssh/id_ecdsa type -1
    debug1: identity file /home/tintin/.ssh/id_ecdsa-cert type -1
    debug1: identity file /home/tintin/.ssh/id_ed25519 type -1
    debug1: identity file /home/tintin/.ssh/id_ed25519-cert type -1
    debug1: identity file /home/tintin/.ssh/id_xmss type -1
    debug1: identity file /home/tintin/.ssh/id_xmss-cert type -1
    debug1: Local version string SSH-2.0-OpenSSH_7.9


    And then it completely hangs and nothing else appears. I tried using other ports like 443, 80 but with no better result than the previous one. I even tried to reboot the server but with no results again.



    This is the telnet output



       telnet my.server.ip 22

    Trying my.server.ip...
    Connected to my.server.ip.
    Escape character is '^]'.
    SSH-2.0-OpenSSH_7.7p1 Ubuntu-4ubuntu0.1
    Connection closed by foreign host.


    But there's no problem connecting to the server from other networks. Is there any way to connect to my server using this college network?



    Edit:
    As far as I could gather while surfing the net for this problem is that the problem basically resides in the network. So is there anyway to bypass this security feature ?










    share|improve this question



























      0












      0








      0








      I been having trouble connecting to my Ubuntu 18.10 server using ssh. Whenever I try to connect with my college network this is the output



          ssh -vvv root@my.server

      OpenSSH_7.9p1, OpenSSL 1.1.1a 20 Nov 2018
      debug1: Reading configuration data /home/tintin/.ssh/config
      debug1: Reading configuration data /etc/ssh/ssh_config
      debug2: resolve_canonicalize: hostname my.server.ip is address
      debug2: ssh_connect_direct
      debug1: Connecting to my.server.ip [my.server.ip] port 22.
      debug1: Connection established.
      debug1: identity file /home/tintin/.ssh/id_rsa type 0
      debug1: identity file /home/tintin/.ssh/id_rsa-cert type -1
      debug1: identity file /home/tintin/.ssh/id_dsa type -1
      debug1: identity file /home/tintin/.ssh/id_dsa-cert type -1
      debug1: identity file /home/tintin/.ssh/id_ecdsa type -1
      debug1: identity file /home/tintin/.ssh/id_ecdsa-cert type -1
      debug1: identity file /home/tintin/.ssh/id_ed25519 type -1
      debug1: identity file /home/tintin/.ssh/id_ed25519-cert type -1
      debug1: identity file /home/tintin/.ssh/id_xmss type -1
      debug1: identity file /home/tintin/.ssh/id_xmss-cert type -1
      debug1: Local version string SSH-2.0-OpenSSH_7.9


      And then it completely hangs and nothing else appears. I tried using other ports like 443, 80 but with no better result than the previous one. I even tried to reboot the server but with no results again.



      This is the telnet output



         telnet my.server.ip 22

      Trying my.server.ip...
      Connected to my.server.ip.
      Escape character is '^]'.
      SSH-2.0-OpenSSH_7.7p1 Ubuntu-4ubuntu0.1
      Connection closed by foreign host.


      But there's no problem connecting to the server from other networks. Is there any way to connect to my server using this college network?



      Edit:
      As far as I could gather while surfing the net for this problem is that the problem basically resides in the network. So is there anyway to bypass this security feature ?










      share|improve this question
















      I been having trouble connecting to my Ubuntu 18.10 server using ssh. Whenever I try to connect with my college network this is the output



          ssh -vvv root@my.server

      OpenSSH_7.9p1, OpenSSL 1.1.1a 20 Nov 2018
      debug1: Reading configuration data /home/tintin/.ssh/config
      debug1: Reading configuration data /etc/ssh/ssh_config
      debug2: resolve_canonicalize: hostname my.server.ip is address
      debug2: ssh_connect_direct
      debug1: Connecting to my.server.ip [my.server.ip] port 22.
      debug1: Connection established.
      debug1: identity file /home/tintin/.ssh/id_rsa type 0
      debug1: identity file /home/tintin/.ssh/id_rsa-cert type -1
      debug1: identity file /home/tintin/.ssh/id_dsa type -1
      debug1: identity file /home/tintin/.ssh/id_dsa-cert type -1
      debug1: identity file /home/tintin/.ssh/id_ecdsa type -1
      debug1: identity file /home/tintin/.ssh/id_ecdsa-cert type -1
      debug1: identity file /home/tintin/.ssh/id_ed25519 type -1
      debug1: identity file /home/tintin/.ssh/id_ed25519-cert type -1
      debug1: identity file /home/tintin/.ssh/id_xmss type -1
      debug1: identity file /home/tintin/.ssh/id_xmss-cert type -1
      debug1: Local version string SSH-2.0-OpenSSH_7.9


      And then it completely hangs and nothing else appears. I tried using other ports like 443, 80 but with no better result than the previous one. I even tried to reboot the server but with no results again.



      This is the telnet output



         telnet my.server.ip 22

      Trying my.server.ip...
      Connected to my.server.ip.
      Escape character is '^]'.
      SSH-2.0-OpenSSH_7.7p1 Ubuntu-4ubuntu0.1
      Connection closed by foreign host.


      But there's no problem connecting to the server from other networks. Is there any way to connect to my server using this college network?



      Edit:
      As far as I could gather while surfing the net for this problem is that the problem basically resides in the network. So is there anyway to bypass this security feature ?







      linux networking ubuntu ssh telnet






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Jan 5 at 13:08







      Tintin

















      asked Jan 4 at 2:19









      TintinTintin

      13




      13






















          2 Answers
          2






          active

          oldest

          votes


















          0














          Strange that it does say connection established. If you had the port wrong it wouldn't establish a connection. Port 22 is the standard. Other servers try not to use port 22 for security reasons (because 22 is the default), like some may use 6922 or something. It's one shot to make sure you are supposed to connect over port 22 (or if it's worked in the past).



          My next thought is that some server admins do not allow root access over SSH for security reasons. I'd try getting ssh to maybe the /www folder and seeing if that works. Wish I had better ideas.






          share|improve this answer
























          • I surfed through the internet a bit more and got to know that there are other people too who faced the same sort of issues and the reason is that their network won't allow ssh on any port. I have really no idea what to do to bypass this security measure. Different people faced the same problem but no one could give a proper solution to this problem. And thanks for your suggestion but that doen't work either. I tried connecting to other servers, tried other users but with no result at all. Guess I have to use the web console for accessing the server or use another network completely.

            – Tintin
            Jan 5 at 12:35





















          0














          After much surfing over the topic finally solved the issue. In this the network administrator is blocking any sort of ssh connection over the network so it's not a problem related to which port I'm using for ssh.



          The only solution that I found is to use a VPN and everything would be okay.






          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',
            autoActivateHeartbeat: false,
            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%2f1390353%2ftrouble-connecting-to-ubuntu-server-using-ssh%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









            0














            Strange that it does say connection established. If you had the port wrong it wouldn't establish a connection. Port 22 is the standard. Other servers try not to use port 22 for security reasons (because 22 is the default), like some may use 6922 or something. It's one shot to make sure you are supposed to connect over port 22 (or if it's worked in the past).



            My next thought is that some server admins do not allow root access over SSH for security reasons. I'd try getting ssh to maybe the /www folder and seeing if that works. Wish I had better ideas.






            share|improve this answer
























            • I surfed through the internet a bit more and got to know that there are other people too who faced the same sort of issues and the reason is that their network won't allow ssh on any port. I have really no idea what to do to bypass this security measure. Different people faced the same problem but no one could give a proper solution to this problem. And thanks for your suggestion but that doen't work either. I tried connecting to other servers, tried other users but with no result at all. Guess I have to use the web console for accessing the server or use another network completely.

              – Tintin
              Jan 5 at 12:35


















            0














            Strange that it does say connection established. If you had the port wrong it wouldn't establish a connection. Port 22 is the standard. Other servers try not to use port 22 for security reasons (because 22 is the default), like some may use 6922 or something. It's one shot to make sure you are supposed to connect over port 22 (or if it's worked in the past).



            My next thought is that some server admins do not allow root access over SSH for security reasons. I'd try getting ssh to maybe the /www folder and seeing if that works. Wish I had better ideas.






            share|improve this answer
























            • I surfed through the internet a bit more and got to know that there are other people too who faced the same sort of issues and the reason is that their network won't allow ssh on any port. I have really no idea what to do to bypass this security measure. Different people faced the same problem but no one could give a proper solution to this problem. And thanks for your suggestion but that doen't work either. I tried connecting to other servers, tried other users but with no result at all. Guess I have to use the web console for accessing the server or use another network completely.

              – Tintin
              Jan 5 at 12:35
















            0












            0








            0







            Strange that it does say connection established. If you had the port wrong it wouldn't establish a connection. Port 22 is the standard. Other servers try not to use port 22 for security reasons (because 22 is the default), like some may use 6922 or something. It's one shot to make sure you are supposed to connect over port 22 (or if it's worked in the past).



            My next thought is that some server admins do not allow root access over SSH for security reasons. I'd try getting ssh to maybe the /www folder and seeing if that works. Wish I had better ideas.






            share|improve this answer













            Strange that it does say connection established. If you had the port wrong it wouldn't establish a connection. Port 22 is the standard. Other servers try not to use port 22 for security reasons (because 22 is the default), like some may use 6922 or something. It's one shot to make sure you are supposed to connect over port 22 (or if it's worked in the past).



            My next thought is that some server admins do not allow root access over SSH for security reasons. I'd try getting ssh to maybe the /www folder and seeing if that works. Wish I had better ideas.







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Jan 4 at 21:54









            gu3milesgu3miles

            1




            1













            • I surfed through the internet a bit more and got to know that there are other people too who faced the same sort of issues and the reason is that their network won't allow ssh on any port. I have really no idea what to do to bypass this security measure. Different people faced the same problem but no one could give a proper solution to this problem. And thanks for your suggestion but that doen't work either. I tried connecting to other servers, tried other users but with no result at all. Guess I have to use the web console for accessing the server or use another network completely.

              – Tintin
              Jan 5 at 12:35





















            • I surfed through the internet a bit more and got to know that there are other people too who faced the same sort of issues and the reason is that their network won't allow ssh on any port. I have really no idea what to do to bypass this security measure. Different people faced the same problem but no one could give a proper solution to this problem. And thanks for your suggestion but that doen't work either. I tried connecting to other servers, tried other users but with no result at all. Guess I have to use the web console for accessing the server or use another network completely.

              – Tintin
              Jan 5 at 12:35



















            I surfed through the internet a bit more and got to know that there are other people too who faced the same sort of issues and the reason is that their network won't allow ssh on any port. I have really no idea what to do to bypass this security measure. Different people faced the same problem but no one could give a proper solution to this problem. And thanks for your suggestion but that doen't work either. I tried connecting to other servers, tried other users but with no result at all. Guess I have to use the web console for accessing the server or use another network completely.

            – Tintin
            Jan 5 at 12:35







            I surfed through the internet a bit more and got to know that there are other people too who faced the same sort of issues and the reason is that their network won't allow ssh on any port. I have really no idea what to do to bypass this security measure. Different people faced the same problem but no one could give a proper solution to this problem. And thanks for your suggestion but that doen't work either. I tried connecting to other servers, tried other users but with no result at all. Guess I have to use the web console for accessing the server or use another network completely.

            – Tintin
            Jan 5 at 12:35















            0














            After much surfing over the topic finally solved the issue. In this the network administrator is blocking any sort of ssh connection over the network so it's not a problem related to which port I'm using for ssh.



            The only solution that I found is to use a VPN and everything would be okay.






            share|improve this answer




























              0














              After much surfing over the topic finally solved the issue. In this the network administrator is blocking any sort of ssh connection over the network so it's not a problem related to which port I'm using for ssh.



              The only solution that I found is to use a VPN and everything would be okay.






              share|improve this answer


























                0












                0








                0







                After much surfing over the topic finally solved the issue. In this the network administrator is blocking any sort of ssh connection over the network so it's not a problem related to which port I'm using for ssh.



                The only solution that I found is to use a VPN and everything would be okay.






                share|improve this answer













                After much surfing over the topic finally solved the issue. In this the network administrator is blocking any sort of ssh connection over the network so it's not a problem related to which port I'm using for ssh.



                The only solution that I found is to use a VPN and everything would be okay.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Jan 7 at 3:23









                TintinTintin

                13




                13






























                    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.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1390353%2ftrouble-connecting-to-ubuntu-server-using-ssh%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

                    Сан-Квентин

                    Алькесар

                    Josef Freinademetz