Windows firewall blocks remote desktop with custom portRemote desktop on custom portsCan't connect with...

Called into a meeting and told we are being made redundant (laid off) and "not to share outside". Can I tell my partner?

What type of postprocessing gives the effect of people standing out

Can chords be played on the flute?

What are these green text/line displays shown during the livestream of Crew Dragon's approach to dock with the ISS?

Most significant research articles for practical investors with research perspectives

Sometimes a banana is just a banana

Is there any relevance to Thor getting his hair cut other than comedic value?

GeometricMean definition

Must a tritone substitution use a dominant seventh chord?

Equivalent to "source" in OpenBSD?

When was drinking water recognized as crucial in marathon running?

Second-rate spelling

How do ISS astronauts "get their stripes"?

Contradiction with Banach Fixed Point Theorem

How to deny access to SQL Server to certain login over SSMS, but allow over .Net SqlClient Data Provider

Compare four integers, return word based on maximum

Make me a metasequence

Why does Starman/Roadster have radial acceleration?

Reason Why Dimensional Travelling Would be Restricted

Are small insurances worth it

Non-Italian European mafias in USA?

How can I handle a player who pre-plans arguments about my rulings on RAW?

How to avoid being sexist when trying to employ someone to function in a very sexist environment?

Where is this triangular-shaped space station from?



Windows firewall blocks remote desktop with custom port


Remote desktop on custom portsCan't connect with Remote Desktop ConnectionRemote Desktop access Windows 7 system from Windows 8Remote Desktop over Internetremote desktop port forwardingfirewall blocks connection even though allowedEnabling Remote Connection through FIrewall with Firewall diasbledRemote desktop is not working - no port 3389 is boundRemote Desktop Failed With Port Open & Listening And Allowed Through FirewallFirewall blocks VirtualBox remote display













6















I was able to use my remote desktop with custom port when I was using Kaspersky Internet Security. Now, I have uninstalled my Kaspersky and switch to Avast!. Therefore, the windows firewall is turned on back again. However, after the firewall is turned on, I cannot connect to the remote desktop. I have set the remote desktop "checked" in the windows firewall as shown by here: http://windows.microsoft.com/en-my/windows7/use-remote-desktop-when-windows-firewall-is-on.



So, I am guessing it is caused by the custom port setting of my remote desktop. So, how can I unblock that on firewall to make my remote desktop works again?



Thank you.










share|improve this question























  • You are essentially asking how do you add a port to the windows firewall. (which would be windows firewall behaving as one would want from a firewall!)

    – barlop
    Mar 3 '14 at 9:20
















6















I was able to use my remote desktop with custom port when I was using Kaspersky Internet Security. Now, I have uninstalled my Kaspersky and switch to Avast!. Therefore, the windows firewall is turned on back again. However, after the firewall is turned on, I cannot connect to the remote desktop. I have set the remote desktop "checked" in the windows firewall as shown by here: http://windows.microsoft.com/en-my/windows7/use-remote-desktop-when-windows-firewall-is-on.



So, I am guessing it is caused by the custom port setting of my remote desktop. So, how can I unblock that on firewall to make my remote desktop works again?



Thank you.










share|improve this question























  • You are essentially asking how do you add a port to the windows firewall. (which would be windows firewall behaving as one would want from a firewall!)

    – barlop
    Mar 3 '14 at 9:20














6












6








6


3






I was able to use my remote desktop with custom port when I was using Kaspersky Internet Security. Now, I have uninstalled my Kaspersky and switch to Avast!. Therefore, the windows firewall is turned on back again. However, after the firewall is turned on, I cannot connect to the remote desktop. I have set the remote desktop "checked" in the windows firewall as shown by here: http://windows.microsoft.com/en-my/windows7/use-remote-desktop-when-windows-firewall-is-on.



So, I am guessing it is caused by the custom port setting of my remote desktop. So, how can I unblock that on firewall to make my remote desktop works again?



Thank you.










share|improve this question














I was able to use my remote desktop with custom port when I was using Kaspersky Internet Security. Now, I have uninstalled my Kaspersky and switch to Avast!. Therefore, the windows firewall is turned on back again. However, after the firewall is turned on, I cannot connect to the remote desktop. I have set the remote desktop "checked" in the windows firewall as shown by here: http://windows.microsoft.com/en-my/windows7/use-remote-desktop-when-windows-firewall-is-on.



So, I am guessing it is caused by the custom port setting of my remote desktop. So, how can I unblock that on firewall to make my remote desktop works again?



Thank you.







windows-7 windows networking remote-desktop firewall






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Mar 3 '14 at 6:53









user1995781user1995781

2343513




2343513













  • You are essentially asking how do you add a port to the windows firewall. (which would be windows firewall behaving as one would want from a firewall!)

    – barlop
    Mar 3 '14 at 9:20



















  • You are essentially asking how do you add a port to the windows firewall. (which would be windows firewall behaving as one would want from a firewall!)

    – barlop
    Mar 3 '14 at 9:20

















You are essentially asking how do you add a port to the windows firewall. (which would be windows firewall behaving as one would want from a firewall!)

– barlop
Mar 3 '14 at 9:20





You are essentially asking how do you add a port to the windows firewall. (which would be windows firewall behaving as one would want from a firewall!)

– barlop
Mar 3 '14 at 9:20










3 Answers
3






active

oldest

votes


















7














To open custom port in Windows Firewall, you can do the following:





  1. In your Windows Firewall in Control Panel, click on the
    Advanced Settings option on the left.

  2. In the Windows Firewall with Advanced Security window that
    opens, click on the Inbound Rules on the left.

  3. Click on the New Rule on the right side of the window.

  4. Select Port on the list of options.

  5. Select TCP (or UDP if that is what you require) and Specific local ports, and then write your
    ports in the text box to the right of Specific local ports (i.e.
    1234).

  6. Select Allow the connection in the next window.

  7. Select the options which you need from Domain, Private, Public
    (private and public are the network types that you select when you
    connect to the new network, and windows asks you to select the
    network type, and domain is obviously your domain).

  8. Finally, write a Name and Description in the window that
    shows next. Click FINISH.




Your port should be now allowed through the Windows Firewall.






share|improve this answer


























  • I would like to highlight step #2-#8!!!! I have spent hours after having opened ports through my home router, only to get confused about why none of my other Windows PC with customized ports should be inaccessible for RDP without having disabled the firewall completely.

    – llinfeng
    Dec 10 '18 at 4:41



















0














If you changed the RDP listening port you will need to create a custom Windows firewall rule to listen on that port.



Create a firewall rule for new port:




  • Open Windows Firewall with Advanced Security


    1. Create a new rule

    2. Select "Inbound Rules" on the top left

    3. Right-click and select "New Rule…"

    4. A new "Inbound Rule Wizard" window opens

    5. Select "Program"

    6. click Next

    7. Select “This program path:”

    8. Type System in the text field

    9. Click Next

    10. Select “Allow the connection”

    11. Click Next

    12. Choose the profiles that the rule is for

    13. Click Next

    14. Name the new rule

    15. I would use something like “RDP3390” or whatever the new port number is

    16. Click "Finish"

    17. Test your port by going to www.whatsmyip.org and use their port scanner. You should be able to turn the rule off and off the scan fail.








share|improve this answer

































    0














    To complete the previous answers I must add the following:



    In case that you want to connect to a Virtualbox machine through a RDP custom port
    you have to disabled the "Virtual Box Manager" default rule, who is blocking all the connection to the Virtual Box Software, without this, the inbound rules that you add will not work.






    share|improve this answer
























    • Welcome to Super User! This is really a comment and not an answer to the original question. To critique or request clarification from an author, leave a comment below their post - you can always comment on your own posts, and once you have sufficient reputation you will be able to comment on any post. Please read Why do I need 50 reputation to comment? What can I do instead?

      – DavidPostill
      Jun 16 '16 at 9:12











    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%2f723832%2fwindows-firewall-blocks-remote-desktop-with-custom-port%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    3 Answers
    3






    active

    oldest

    votes








    3 Answers
    3






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    7














    To open custom port in Windows Firewall, you can do the following:





    1. In your Windows Firewall in Control Panel, click on the
      Advanced Settings option on the left.

    2. In the Windows Firewall with Advanced Security window that
      opens, click on the Inbound Rules on the left.

    3. Click on the New Rule on the right side of the window.

    4. Select Port on the list of options.

    5. Select TCP (or UDP if that is what you require) and Specific local ports, and then write your
      ports in the text box to the right of Specific local ports (i.e.
      1234).

    6. Select Allow the connection in the next window.

    7. Select the options which you need from Domain, Private, Public
      (private and public are the network types that you select when you
      connect to the new network, and windows asks you to select the
      network type, and domain is obviously your domain).

    8. Finally, write a Name and Description in the window that
      shows next. Click FINISH.




    Your port should be now allowed through the Windows Firewall.






    share|improve this answer


























    • I would like to highlight step #2-#8!!!! I have spent hours after having opened ports through my home router, only to get confused about why none of my other Windows PC with customized ports should be inaccessible for RDP without having disabled the firewall completely.

      – llinfeng
      Dec 10 '18 at 4:41
















    7














    To open custom port in Windows Firewall, you can do the following:





    1. In your Windows Firewall in Control Panel, click on the
      Advanced Settings option on the left.

    2. In the Windows Firewall with Advanced Security window that
      opens, click on the Inbound Rules on the left.

    3. Click on the New Rule on the right side of the window.

    4. Select Port on the list of options.

    5. Select TCP (or UDP if that is what you require) and Specific local ports, and then write your
      ports in the text box to the right of Specific local ports (i.e.
      1234).

    6. Select Allow the connection in the next window.

    7. Select the options which you need from Domain, Private, Public
      (private and public are the network types that you select when you
      connect to the new network, and windows asks you to select the
      network type, and domain is obviously your domain).

    8. Finally, write a Name and Description in the window that
      shows next. Click FINISH.




    Your port should be now allowed through the Windows Firewall.






    share|improve this answer


























    • I would like to highlight step #2-#8!!!! I have spent hours after having opened ports through my home router, only to get confused about why none of my other Windows PC with customized ports should be inaccessible for RDP without having disabled the firewall completely.

      – llinfeng
      Dec 10 '18 at 4:41














    7












    7








    7







    To open custom port in Windows Firewall, you can do the following:





    1. In your Windows Firewall in Control Panel, click on the
      Advanced Settings option on the left.

    2. In the Windows Firewall with Advanced Security window that
      opens, click on the Inbound Rules on the left.

    3. Click on the New Rule on the right side of the window.

    4. Select Port on the list of options.

    5. Select TCP (or UDP if that is what you require) and Specific local ports, and then write your
      ports in the text box to the right of Specific local ports (i.e.
      1234).

    6. Select Allow the connection in the next window.

    7. Select the options which you need from Domain, Private, Public
      (private and public are the network types that you select when you
      connect to the new network, and windows asks you to select the
      network type, and domain is obviously your domain).

    8. Finally, write a Name and Description in the window that
      shows next. Click FINISH.




    Your port should be now allowed through the Windows Firewall.






    share|improve this answer















    To open custom port in Windows Firewall, you can do the following:





    1. In your Windows Firewall in Control Panel, click on the
      Advanced Settings option on the left.

    2. In the Windows Firewall with Advanced Security window that
      opens, click on the Inbound Rules on the left.

    3. Click on the New Rule on the right side of the window.

    4. Select Port on the list of options.

    5. Select TCP (or UDP if that is what you require) and Specific local ports, and then write your
      ports in the text box to the right of Specific local ports (i.e.
      1234).

    6. Select Allow the connection in the next window.

    7. Select the options which you need from Domain, Private, Public
      (private and public are the network types that you select when you
      connect to the new network, and windows asks you to select the
      network type, and domain is obviously your domain).

    8. Finally, write a Name and Description in the window that
      shows next. Click FINISH.




    Your port should be now allowed through the Windows Firewall.







    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited Mar 3 '14 at 9:17









    barlop

    15.6k2590149




    15.6k2590149










    answered Mar 3 '14 at 8:42









    Damir KasipovicDamir Kasipovic

    807510




    807510













    • I would like to highlight step #2-#8!!!! I have spent hours after having opened ports through my home router, only to get confused about why none of my other Windows PC with customized ports should be inaccessible for RDP without having disabled the firewall completely.

      – llinfeng
      Dec 10 '18 at 4:41



















    • I would like to highlight step #2-#8!!!! I have spent hours after having opened ports through my home router, only to get confused about why none of my other Windows PC with customized ports should be inaccessible for RDP without having disabled the firewall completely.

      – llinfeng
      Dec 10 '18 at 4:41

















    I would like to highlight step #2-#8!!!! I have spent hours after having opened ports through my home router, only to get confused about why none of my other Windows PC with customized ports should be inaccessible for RDP without having disabled the firewall completely.

    – llinfeng
    Dec 10 '18 at 4:41





    I would like to highlight step #2-#8!!!! I have spent hours after having opened ports through my home router, only to get confused about why none of my other Windows PC with customized ports should be inaccessible for RDP without having disabled the firewall completely.

    – llinfeng
    Dec 10 '18 at 4:41













    0














    If you changed the RDP listening port you will need to create a custom Windows firewall rule to listen on that port.



    Create a firewall rule for new port:




    • Open Windows Firewall with Advanced Security


      1. Create a new rule

      2. Select "Inbound Rules" on the top left

      3. Right-click and select "New Rule…"

      4. A new "Inbound Rule Wizard" window opens

      5. Select "Program"

      6. click Next

      7. Select “This program path:”

      8. Type System in the text field

      9. Click Next

      10. Select “Allow the connection”

      11. Click Next

      12. Choose the profiles that the rule is for

      13. Click Next

      14. Name the new rule

      15. I would use something like “RDP3390” or whatever the new port number is

      16. Click "Finish"

      17. Test your port by going to www.whatsmyip.org and use their port scanner. You should be able to turn the rule off and off the scan fail.








    share|improve this answer






























      0














      If you changed the RDP listening port you will need to create a custom Windows firewall rule to listen on that port.



      Create a firewall rule for new port:




      • Open Windows Firewall with Advanced Security


        1. Create a new rule

        2. Select "Inbound Rules" on the top left

        3. Right-click and select "New Rule…"

        4. A new "Inbound Rule Wizard" window opens

        5. Select "Program"

        6. click Next

        7. Select “This program path:”

        8. Type System in the text field

        9. Click Next

        10. Select “Allow the connection”

        11. Click Next

        12. Choose the profiles that the rule is for

        13. Click Next

        14. Name the new rule

        15. I would use something like “RDP3390” or whatever the new port number is

        16. Click "Finish"

        17. Test your port by going to www.whatsmyip.org and use their port scanner. You should be able to turn the rule off and off the scan fail.








      share|improve this answer




























        0












        0








        0







        If you changed the RDP listening port you will need to create a custom Windows firewall rule to listen on that port.



        Create a firewall rule for new port:




        • Open Windows Firewall with Advanced Security


          1. Create a new rule

          2. Select "Inbound Rules" on the top left

          3. Right-click and select "New Rule…"

          4. A new "Inbound Rule Wizard" window opens

          5. Select "Program"

          6. click Next

          7. Select “This program path:”

          8. Type System in the text field

          9. Click Next

          10. Select “Allow the connection”

          11. Click Next

          12. Choose the profiles that the rule is for

          13. Click Next

          14. Name the new rule

          15. I would use something like “RDP3390” or whatever the new port number is

          16. Click "Finish"

          17. Test your port by going to www.whatsmyip.org and use their port scanner. You should be able to turn the rule off and off the scan fail.








        share|improve this answer















        If you changed the RDP listening port you will need to create a custom Windows firewall rule to listen on that port.



        Create a firewall rule for new port:




        • Open Windows Firewall with Advanced Security


          1. Create a new rule

          2. Select "Inbound Rules" on the top left

          3. Right-click and select "New Rule…"

          4. A new "Inbound Rule Wizard" window opens

          5. Select "Program"

          6. click Next

          7. Select “This program path:”

          8. Type System in the text field

          9. Click Next

          10. Select “Allow the connection”

          11. Click Next

          12. Choose the profiles that the rule is for

          13. Click Next

          14. Name the new rule

          15. I would use something like “RDP3390” or whatever the new port number is

          16. Click "Finish"

          17. Test your port by going to www.whatsmyip.org and use their port scanner. You should be able to turn the rule off and off the scan fail.









        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Nov 1 '14 at 7:03

























        answered Nov 1 '14 at 6:57









        no3godsno3gods

        11




        11























            0














            To complete the previous answers I must add the following:



            In case that you want to connect to a Virtualbox machine through a RDP custom port
            you have to disabled the "Virtual Box Manager" default rule, who is blocking all the connection to the Virtual Box Software, without this, the inbound rules that you add will not work.






            share|improve this answer
























            • Welcome to Super User! This is really a comment and not an answer to the original question. To critique or request clarification from an author, leave a comment below their post - you can always comment on your own posts, and once you have sufficient reputation you will be able to comment on any post. Please read Why do I need 50 reputation to comment? What can I do instead?

              – DavidPostill
              Jun 16 '16 at 9:12
















            0














            To complete the previous answers I must add the following:



            In case that you want to connect to a Virtualbox machine through a RDP custom port
            you have to disabled the "Virtual Box Manager" default rule, who is blocking all the connection to the Virtual Box Software, without this, the inbound rules that you add will not work.






            share|improve this answer
























            • Welcome to Super User! This is really a comment and not an answer to the original question. To critique or request clarification from an author, leave a comment below their post - you can always comment on your own posts, and once you have sufficient reputation you will be able to comment on any post. Please read Why do I need 50 reputation to comment? What can I do instead?

              – DavidPostill
              Jun 16 '16 at 9:12














            0












            0








            0







            To complete the previous answers I must add the following:



            In case that you want to connect to a Virtualbox machine through a RDP custom port
            you have to disabled the "Virtual Box Manager" default rule, who is blocking all the connection to the Virtual Box Software, without this, the inbound rules that you add will not work.






            share|improve this answer













            To complete the previous answers I must add the following:



            In case that you want to connect to a Virtualbox machine through a RDP custom port
            you have to disabled the "Virtual Box Manager" default rule, who is blocking all the connection to the Virtual Box Software, without this, the inbound rules that you add will not work.







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Jun 16 '16 at 0:14









            MatiMati

            1




            1













            • Welcome to Super User! This is really a comment and not an answer to the original question. To critique or request clarification from an author, leave a comment below their post - you can always comment on your own posts, and once you have sufficient reputation you will be able to comment on any post. Please read Why do I need 50 reputation to comment? What can I do instead?

              – DavidPostill
              Jun 16 '16 at 9:12



















            • Welcome to Super User! This is really a comment and not an answer to the original question. To critique or request clarification from an author, leave a comment below their post - you can always comment on your own posts, and once you have sufficient reputation you will be able to comment on any post. Please read Why do I need 50 reputation to comment? What can I do instead?

              – DavidPostill
              Jun 16 '16 at 9:12

















            Welcome to Super User! This is really a comment and not an answer to the original question. To critique or request clarification from an author, leave a comment below their post - you can always comment on your own posts, and once you have sufficient reputation you will be able to comment on any post. Please read Why do I need 50 reputation to comment? What can I do instead?

            – DavidPostill
            Jun 16 '16 at 9:12





            Welcome to Super User! This is really a comment and not an answer to the original question. To critique or request clarification from an author, leave a comment below their post - you can always comment on your own posts, and once you have sufficient reputation you will be able to comment on any post. Please read Why do I need 50 reputation to comment? What can I do instead?

            – DavidPostill
            Jun 16 '16 at 9:12


















            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%2f723832%2fwindows-firewall-blocks-remote-desktop-with-custom-port%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

            Couldn't open a raw socket. Error: Permission denied (13) (nmap)Is it possible to run networking commands...

            VNC viewer RFB protocol error: bad desktop size 0x0I Cannot Type the Key 'd' (lowercase) in VNC Viewer...

            Why not use the yoke to control yaw, as well as pitch and roll? Announcing the arrival of...