How to connect to Windows remote domain from Linux know its gateway hostname?












1















I have credentials to connect to my University's reserved Linux virtual machine which means :




  • username

  • password

  • gateway's hostname let's say secretgateway.net

  • full hostname in .local domain let's say it's myscrethostname.local

  • domain I need to connect to let's say pluto


and some other stuff. How can I connect to this machine (either via RDP or preferably SSH ) from Ubuntu being in a remote network ?



EDIT I have the needed .rdp which I can open in Windows and connect to the machine but when I use Ubuntu's remote desktop connection (Remmina) it tries to connect straight to the hostname.local which I presume won't work.










share|improve this question

























  • What's the FQDN for the machine? Obviously it's not just hostname.local. I assume Windows accounts for the network you're already connecting from to likely complete that.

    – Daniel Chateau
    Mar 25 '14 at 21:58











  • I have updated the answer. I know that I have to connect to a windows domain and I can do that with domainjoin-cli from likewise-open5 package but how do I do that since I only know domain name pluto ?

    – Patryk
    Mar 25 '14 at 22:05


















1















I have credentials to connect to my University's reserved Linux virtual machine which means :




  • username

  • password

  • gateway's hostname let's say secretgateway.net

  • full hostname in .local domain let's say it's myscrethostname.local

  • domain I need to connect to let's say pluto


and some other stuff. How can I connect to this machine (either via RDP or preferably SSH ) from Ubuntu being in a remote network ?



EDIT I have the needed .rdp which I can open in Windows and connect to the machine but when I use Ubuntu's remote desktop connection (Remmina) it tries to connect straight to the hostname.local which I presume won't work.










share|improve this question

























  • What's the FQDN for the machine? Obviously it's not just hostname.local. I assume Windows accounts for the network you're already connecting from to likely complete that.

    – Daniel Chateau
    Mar 25 '14 at 21:58











  • I have updated the answer. I know that I have to connect to a windows domain and I can do that with domainjoin-cli from likewise-open5 package but how do I do that since I only know domain name pluto ?

    – Patryk
    Mar 25 '14 at 22:05
















1












1








1








I have credentials to connect to my University's reserved Linux virtual machine which means :




  • username

  • password

  • gateway's hostname let's say secretgateway.net

  • full hostname in .local domain let's say it's myscrethostname.local

  • domain I need to connect to let's say pluto


and some other stuff. How can I connect to this machine (either via RDP or preferably SSH ) from Ubuntu being in a remote network ?



EDIT I have the needed .rdp which I can open in Windows and connect to the machine but when I use Ubuntu's remote desktop connection (Remmina) it tries to connect straight to the hostname.local which I presume won't work.










share|improve this question
















I have credentials to connect to my University's reserved Linux virtual machine which means :




  • username

  • password

  • gateway's hostname let's say secretgateway.net

  • full hostname in .local domain let's say it's myscrethostname.local

  • domain I need to connect to let's say pluto


and some other stuff. How can I connect to this machine (either via RDP or preferably SSH ) from Ubuntu being in a remote network ?



EDIT I have the needed .rdp which I can open in Windows and connect to the machine but when I use Ubuntu's remote desktop connection (Remmina) it tries to connect straight to the hostname.local which I presume won't work.







linux networking ssh remote-desktop hostname






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Mar 25 '14 at 22:04







Patryk

















asked Mar 25 '14 at 21:18









PatrykPatryk

64531830




64531830













  • What's the FQDN for the machine? Obviously it's not just hostname.local. I assume Windows accounts for the network you're already connecting from to likely complete that.

    – Daniel Chateau
    Mar 25 '14 at 21:58











  • I have updated the answer. I know that I have to connect to a windows domain and I can do that with domainjoin-cli from likewise-open5 package but how do I do that since I only know domain name pluto ?

    – Patryk
    Mar 25 '14 at 22:05





















  • What's the FQDN for the machine? Obviously it's not just hostname.local. I assume Windows accounts for the network you're already connecting from to likely complete that.

    – Daniel Chateau
    Mar 25 '14 at 21:58











  • I have updated the answer. I know that I have to connect to a windows domain and I can do that with domainjoin-cli from likewise-open5 package but how do I do that since I only know domain name pluto ?

    – Patryk
    Mar 25 '14 at 22:05



















What's the FQDN for the machine? Obviously it's not just hostname.local. I assume Windows accounts for the network you're already connecting from to likely complete that.

– Daniel Chateau
Mar 25 '14 at 21:58





What's the FQDN for the machine? Obviously it's not just hostname.local. I assume Windows accounts for the network you're already connecting from to likely complete that.

– Daniel Chateau
Mar 25 '14 at 21:58













I have updated the answer. I know that I have to connect to a windows domain and I can do that with domainjoin-cli from likewise-open5 package but how do I do that since I only know domain name pluto ?

– Patryk
Mar 25 '14 at 22:05







I have updated the answer. I know that I have to connect to a windows domain and I can do that with domainjoin-cli from likewise-open5 package but how do I do that since I only know domain name pluto ?

– Patryk
Mar 25 '14 at 22:05












1 Answer
1






active

oldest

votes


















0














For now I have been able to connect with Remmina on a remote computer not in my LAN doing these steps on two different levels:



a) the remote computer at work (eg Windows):




  1. must be powered on (not in standby or hibernate mode)

  2. with enabled remote desktop option for your user authentication

  3. with firewall enabled for remote assistance and remote desktop on
    local and public IP


  4. you need to know its public IP, that can change for which you may
    choose to create/know a relative Dynamic DNS (DDNS). To know your
    public IP on remote computer, you can launch the following command
    on the remote computer, that works either on Windows or on Linux:



    nslookup myip.opendns.com resolver1.opendns.com



    on a remote Linux you can also run a script like the following:



    #!/bin/bash
    myip="$(dig +short myip.opendns.com @resolver1.opendns.com)"
    echo "${myip}" > ~/Desktop/my_public_ip.txt



  5. if your remote public IP changes, you need to repeat the step 4 to
    know your new public IP (not necessary if you use a Dynamic DNS) and
    use it to configure your router at home


  6. I don't know if necessary, but maybe can be necessary open 3389
    port also in the remote router: omit this sixth step for now and
    proceed further



b) your computer at home (eg. Linux):




  1. you need to configure your router, enabling the port 3389 associated
    with your local IP, by using the protocol TCP

  2. you need to open the port 3389 in the firewall; in Linux, for
    example, you can run the command:
    $ sudo firewall-cmd --zone=public --add-port=3389/tcp --permanent

  3. Install Remmina; in Fedora, for example: $ sudo dnf install remmina*

  4. open remmina and setup the remote desktop by using a RDP protocol,
    indicating the remote public IP with the port (x.x.x.x:3389) as
    server, your username and password, a domain (like WORKGROUP) if
    any, set client resolution, depth color to Truecolor 32 bpp, a
    folder to share if any, and, in advanced tab, good as quality, NLA
    (Network Level Authentication: for me it worked) or RDP as security.
    Save and connect, accepting the certificate request


Other tools



To solve the unwanted behavior found by using Remmina (and similar), that redirects the remote user to Windows lock screen, allowing only one user to be logged, you need to avoid RDP protocol.



Here a list of alternative tools:



a) NoMachine or NX that use X11 forwarding through SSH protocol



b) Anydesk



c) UltraVNC



a) NoMachine or NX that use X11 forwarding through SSH



b) Anydesk



c) UltraVNC






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%2f733521%2fhow-to-connect-to-windows-remote-domain-from-linux-know-its-gateway-hostname%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    For now I have been able to connect with Remmina on a remote computer not in my LAN doing these steps on two different levels:



    a) the remote computer at work (eg Windows):




    1. must be powered on (not in standby or hibernate mode)

    2. with enabled remote desktop option for your user authentication

    3. with firewall enabled for remote assistance and remote desktop on
      local and public IP


    4. you need to know its public IP, that can change for which you may
      choose to create/know a relative Dynamic DNS (DDNS). To know your
      public IP on remote computer, you can launch the following command
      on the remote computer, that works either on Windows or on Linux:



      nslookup myip.opendns.com resolver1.opendns.com



      on a remote Linux you can also run a script like the following:



      #!/bin/bash
      myip="$(dig +short myip.opendns.com @resolver1.opendns.com)"
      echo "${myip}" > ~/Desktop/my_public_ip.txt



    5. if your remote public IP changes, you need to repeat the step 4 to
      know your new public IP (not necessary if you use a Dynamic DNS) and
      use it to configure your router at home


    6. I don't know if necessary, but maybe can be necessary open 3389
      port also in the remote router: omit this sixth step for now and
      proceed further



    b) your computer at home (eg. Linux):




    1. you need to configure your router, enabling the port 3389 associated
      with your local IP, by using the protocol TCP

    2. you need to open the port 3389 in the firewall; in Linux, for
      example, you can run the command:
      $ sudo firewall-cmd --zone=public --add-port=3389/tcp --permanent

    3. Install Remmina; in Fedora, for example: $ sudo dnf install remmina*

    4. open remmina and setup the remote desktop by using a RDP protocol,
      indicating the remote public IP with the port (x.x.x.x:3389) as
      server, your username and password, a domain (like WORKGROUP) if
      any, set client resolution, depth color to Truecolor 32 bpp, a
      folder to share if any, and, in advanced tab, good as quality, NLA
      (Network Level Authentication: for me it worked) or RDP as security.
      Save and connect, accepting the certificate request


    Other tools



    To solve the unwanted behavior found by using Remmina (and similar), that redirects the remote user to Windows lock screen, allowing only one user to be logged, you need to avoid RDP protocol.



    Here a list of alternative tools:



    a) NoMachine or NX that use X11 forwarding through SSH protocol



    b) Anydesk



    c) UltraVNC



    a) NoMachine or NX that use X11 forwarding through SSH



    b) Anydesk



    c) UltraVNC






    share|improve this answer






























      0














      For now I have been able to connect with Remmina on a remote computer not in my LAN doing these steps on two different levels:



      a) the remote computer at work (eg Windows):




      1. must be powered on (not in standby or hibernate mode)

      2. with enabled remote desktop option for your user authentication

      3. with firewall enabled for remote assistance and remote desktop on
        local and public IP


      4. you need to know its public IP, that can change for which you may
        choose to create/know a relative Dynamic DNS (DDNS). To know your
        public IP on remote computer, you can launch the following command
        on the remote computer, that works either on Windows or on Linux:



        nslookup myip.opendns.com resolver1.opendns.com



        on a remote Linux you can also run a script like the following:



        #!/bin/bash
        myip="$(dig +short myip.opendns.com @resolver1.opendns.com)"
        echo "${myip}" > ~/Desktop/my_public_ip.txt



      5. if your remote public IP changes, you need to repeat the step 4 to
        know your new public IP (not necessary if you use a Dynamic DNS) and
        use it to configure your router at home


      6. I don't know if necessary, but maybe can be necessary open 3389
        port also in the remote router: omit this sixth step for now and
        proceed further



      b) your computer at home (eg. Linux):




      1. you need to configure your router, enabling the port 3389 associated
        with your local IP, by using the protocol TCP

      2. you need to open the port 3389 in the firewall; in Linux, for
        example, you can run the command:
        $ sudo firewall-cmd --zone=public --add-port=3389/tcp --permanent

      3. Install Remmina; in Fedora, for example: $ sudo dnf install remmina*

      4. open remmina and setup the remote desktop by using a RDP protocol,
        indicating the remote public IP with the port (x.x.x.x:3389) as
        server, your username and password, a domain (like WORKGROUP) if
        any, set client resolution, depth color to Truecolor 32 bpp, a
        folder to share if any, and, in advanced tab, good as quality, NLA
        (Network Level Authentication: for me it worked) or RDP as security.
        Save and connect, accepting the certificate request


      Other tools



      To solve the unwanted behavior found by using Remmina (and similar), that redirects the remote user to Windows lock screen, allowing only one user to be logged, you need to avoid RDP protocol.



      Here a list of alternative tools:



      a) NoMachine or NX that use X11 forwarding through SSH protocol



      b) Anydesk



      c) UltraVNC



      a) NoMachine or NX that use X11 forwarding through SSH



      b) Anydesk



      c) UltraVNC






      share|improve this answer




























        0












        0








        0







        For now I have been able to connect with Remmina on a remote computer not in my LAN doing these steps on two different levels:



        a) the remote computer at work (eg Windows):




        1. must be powered on (not in standby or hibernate mode)

        2. with enabled remote desktop option for your user authentication

        3. with firewall enabled for remote assistance and remote desktop on
          local and public IP


        4. you need to know its public IP, that can change for which you may
          choose to create/know a relative Dynamic DNS (DDNS). To know your
          public IP on remote computer, you can launch the following command
          on the remote computer, that works either on Windows or on Linux:



          nslookup myip.opendns.com resolver1.opendns.com



          on a remote Linux you can also run a script like the following:



          #!/bin/bash
          myip="$(dig +short myip.opendns.com @resolver1.opendns.com)"
          echo "${myip}" > ~/Desktop/my_public_ip.txt



        5. if your remote public IP changes, you need to repeat the step 4 to
          know your new public IP (not necessary if you use a Dynamic DNS) and
          use it to configure your router at home


        6. I don't know if necessary, but maybe can be necessary open 3389
          port also in the remote router: omit this sixth step for now and
          proceed further



        b) your computer at home (eg. Linux):




        1. you need to configure your router, enabling the port 3389 associated
          with your local IP, by using the protocol TCP

        2. you need to open the port 3389 in the firewall; in Linux, for
          example, you can run the command:
          $ sudo firewall-cmd --zone=public --add-port=3389/tcp --permanent

        3. Install Remmina; in Fedora, for example: $ sudo dnf install remmina*

        4. open remmina and setup the remote desktop by using a RDP protocol,
          indicating the remote public IP with the port (x.x.x.x:3389) as
          server, your username and password, a domain (like WORKGROUP) if
          any, set client resolution, depth color to Truecolor 32 bpp, a
          folder to share if any, and, in advanced tab, good as quality, NLA
          (Network Level Authentication: for me it worked) or RDP as security.
          Save and connect, accepting the certificate request


        Other tools



        To solve the unwanted behavior found by using Remmina (and similar), that redirects the remote user to Windows lock screen, allowing only one user to be logged, you need to avoid RDP protocol.



        Here a list of alternative tools:



        a) NoMachine or NX that use X11 forwarding through SSH protocol



        b) Anydesk



        c) UltraVNC



        a) NoMachine or NX that use X11 forwarding through SSH



        b) Anydesk



        c) UltraVNC






        share|improve this answer















        For now I have been able to connect with Remmina on a remote computer not in my LAN doing these steps on two different levels:



        a) the remote computer at work (eg Windows):




        1. must be powered on (not in standby or hibernate mode)

        2. with enabled remote desktop option for your user authentication

        3. with firewall enabled for remote assistance and remote desktop on
          local and public IP


        4. you need to know its public IP, that can change for which you may
          choose to create/know a relative Dynamic DNS (DDNS). To know your
          public IP on remote computer, you can launch the following command
          on the remote computer, that works either on Windows or on Linux:



          nslookup myip.opendns.com resolver1.opendns.com



          on a remote Linux you can also run a script like the following:



          #!/bin/bash
          myip="$(dig +short myip.opendns.com @resolver1.opendns.com)"
          echo "${myip}" > ~/Desktop/my_public_ip.txt



        5. if your remote public IP changes, you need to repeat the step 4 to
          know your new public IP (not necessary if you use a Dynamic DNS) and
          use it to configure your router at home


        6. I don't know if necessary, but maybe can be necessary open 3389
          port also in the remote router: omit this sixth step for now and
          proceed further



        b) your computer at home (eg. Linux):




        1. you need to configure your router, enabling the port 3389 associated
          with your local IP, by using the protocol TCP

        2. you need to open the port 3389 in the firewall; in Linux, for
          example, you can run the command:
          $ sudo firewall-cmd --zone=public --add-port=3389/tcp --permanent

        3. Install Remmina; in Fedora, for example: $ sudo dnf install remmina*

        4. open remmina and setup the remote desktop by using a RDP protocol,
          indicating the remote public IP with the port (x.x.x.x:3389) as
          server, your username and password, a domain (like WORKGROUP) if
          any, set client resolution, depth color to Truecolor 32 bpp, a
          folder to share if any, and, in advanced tab, good as quality, NLA
          (Network Level Authentication: for me it worked) or RDP as security.
          Save and connect, accepting the certificate request


        Other tools



        To solve the unwanted behavior found by using Remmina (and similar), that redirects the remote user to Windows lock screen, allowing only one user to be logged, you need to avoid RDP protocol.



        Here a list of alternative tools:



        a) NoMachine or NX that use X11 forwarding through SSH protocol



        b) Anydesk



        c) UltraVNC



        a) NoMachine or NX that use X11 forwarding through SSH



        b) Anydesk



        c) UltraVNC







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Mar 5 at 15:59

























        answered Feb 13 at 21:07









        Riccardo VolpeRiccardo Volpe

        1065




        1065






























            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%2f733521%2fhow-to-connect-to-windows-remote-domain-from-linux-know-its-gateway-hostname%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

            Mouse cursor on multiple screens with different PPI

            Agildo Ribeiro

            Sometime when accessing a menu: “Ubuntu 16.04 has experienced an internal error”