windows 10 L2TP/Ipsec VPN with synology NAS not workingWindows 7 RTM IPSec VPNVPN ipsec tunnel from router to...

Email Account under attack (really) - anything I can do?

How to manage monthly salary

Unbreakable Formation vs. Cry of the Carnarium

Add an angle to a sphere

COUNT(id) or MAX(id) - which is faster?

Does it makes sense to buy a new cycle to learn riding?

Can produce flame be used to grapple, or as an unarmed strike, in the right circumstances?

"listening to me about as much as you're listening to this pole here"

Finding files for which a command fails

Is it possible to make sharp wind that can cut stuff from afar?

What do the Banks children have against barley water?

Does the average primeness of natural numbers tend to zero?

Shall I use personal or official e-mail account when registering to external websites for work purpose?

aging parents with no investments

Latin words with no plurals in English

Manga about a female worker who got dragged into another world together with this high school girl and she was just told she's not needed anymore

What does "enim et" mean?

Is domain driven design an anti-SQL pattern?

What is the command to reset a PC without deleting any files

Was there ever an axiom rendered a theorem?

Need help identifying/translating a plaque in Tangier, Morocco

Piano - What is the notation for a double stop where both notes in the double stop are different lengths?

Crop image to path created in TikZ?

Check if two datetimes are between two others



windows 10 L2TP/Ipsec VPN with synology NAS not working


Windows 7 RTM IPSec VPNVPN ipsec tunnel from router to single windows server computer (gateway-to-host)Synology cannot find nas after reinstall windows 8IPSec with or without L2TP?L2TP over IPSec VPN on Fedora 21L2TP IPSec doesn't work from other cityIPSec VPN Routed LANsAccessing server behind Mikrotik L2TP/IPSec ClientCan't connect to L2TP/IPSec VPN with Linux but works on Mac OSConnect Strongswan/VPN-Client (Debian) to IPSec/L2TP Server (Windows 2012) - AUTHENTIFICATION_FAILED






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







0















I am using a synology NAS that has a L2TP/Ipsec VPN server running. The NAS is located in a network with a FritzBox router.

Now I am in another network that is also established with a FritzBox router. From here I can connect to the VPN via debian and android. But on one of two Windows 10 machines it is not working.

And now I am curiouse, why the one windows 10 will not connect. To fix this one computer is my question in this post.



I have set up the registry:

DWORD AssumeUDPEncapsulationContextOnSendRule in HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesPolicyAgent with the value 2.



The services are running:
IPsec Policy Agent and IKE and AuthIP IPsec Keying Module



I configured the network adapter:
adapter settings

(Sorry that it is german.)



I checked the credentials (username, domain, password, ...) several times.

Also the preconfigured key is entered correctly.



But still I get this message:
error message

(image from another post, but it is the same message that I get, but in english.)



No error code that I can follow.



The computer that it is not working on is a Surface Pro 4, newest updates from yesterday evening.



Some things that I tried (none of them had any effect on the problem):




  • Going to the device manager -> networkadapter -> delete all WAN Miniport -> action -> search for changed hardware

  • disabeling the Xbox Live-Networkservice (was not running in the first place)

  • I tried to restart the DHCP-Client, but permission denied with code 4. So I could not restart. Trying to fix this permission issue also did not work (more permissions in the registry and adding some extra users to the admin group like system and so on.). So I tried other things.


What am I missing? Why is this setup working on several windows 10 computers, but not on this one surface?



thanks and greetings










share|improve this question














bumped to the homepage by Community 2 days ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.






















    0















    I am using a synology NAS that has a L2TP/Ipsec VPN server running. The NAS is located in a network with a FritzBox router.

    Now I am in another network that is also established with a FritzBox router. From here I can connect to the VPN via debian and android. But on one of two Windows 10 machines it is not working.

    And now I am curiouse, why the one windows 10 will not connect. To fix this one computer is my question in this post.



    I have set up the registry:

    DWORD AssumeUDPEncapsulationContextOnSendRule in HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesPolicyAgent with the value 2.



    The services are running:
    IPsec Policy Agent and IKE and AuthIP IPsec Keying Module



    I configured the network adapter:
    adapter settings

    (Sorry that it is german.)



    I checked the credentials (username, domain, password, ...) several times.

    Also the preconfigured key is entered correctly.



    But still I get this message:
    error message

    (image from another post, but it is the same message that I get, but in english.)



    No error code that I can follow.



    The computer that it is not working on is a Surface Pro 4, newest updates from yesterday evening.



    Some things that I tried (none of them had any effect on the problem):




    • Going to the device manager -> networkadapter -> delete all WAN Miniport -> action -> search for changed hardware

    • disabeling the Xbox Live-Networkservice (was not running in the first place)

    • I tried to restart the DHCP-Client, but permission denied with code 4. So I could not restart. Trying to fix this permission issue also did not work (more permissions in the registry and adding some extra users to the admin group like system and so on.). So I tried other things.


    What am I missing? Why is this setup working on several windows 10 computers, but not on this one surface?



    thanks and greetings










    share|improve this question














    bumped to the homepage by Community 2 days ago


    This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.


















      0












      0








      0








      I am using a synology NAS that has a L2TP/Ipsec VPN server running. The NAS is located in a network with a FritzBox router.

      Now I am in another network that is also established with a FritzBox router. From here I can connect to the VPN via debian and android. But on one of two Windows 10 machines it is not working.

      And now I am curiouse, why the one windows 10 will not connect. To fix this one computer is my question in this post.



      I have set up the registry:

      DWORD AssumeUDPEncapsulationContextOnSendRule in HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesPolicyAgent with the value 2.



      The services are running:
      IPsec Policy Agent and IKE and AuthIP IPsec Keying Module



      I configured the network adapter:
      adapter settings

      (Sorry that it is german.)



      I checked the credentials (username, domain, password, ...) several times.

      Also the preconfigured key is entered correctly.



      But still I get this message:
      error message

      (image from another post, but it is the same message that I get, but in english.)



      No error code that I can follow.



      The computer that it is not working on is a Surface Pro 4, newest updates from yesterday evening.



      Some things that I tried (none of them had any effect on the problem):




      • Going to the device manager -> networkadapter -> delete all WAN Miniport -> action -> search for changed hardware

      • disabeling the Xbox Live-Networkservice (was not running in the first place)

      • I tried to restart the DHCP-Client, but permission denied with code 4. So I could not restart. Trying to fix this permission issue also did not work (more permissions in the registry and adding some extra users to the admin group like system and so on.). So I tried other things.


      What am I missing? Why is this setup working on several windows 10 computers, but not on this one surface?



      thanks and greetings










      share|improve this question














      I am using a synology NAS that has a L2TP/Ipsec VPN server running. The NAS is located in a network with a FritzBox router.

      Now I am in another network that is also established with a FritzBox router. From here I can connect to the VPN via debian and android. But on one of two Windows 10 machines it is not working.

      And now I am curiouse, why the one windows 10 will not connect. To fix this one computer is my question in this post.



      I have set up the registry:

      DWORD AssumeUDPEncapsulationContextOnSendRule in HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesPolicyAgent with the value 2.



      The services are running:
      IPsec Policy Agent and IKE and AuthIP IPsec Keying Module



      I configured the network adapter:
      adapter settings

      (Sorry that it is german.)



      I checked the credentials (username, domain, password, ...) several times.

      Also the preconfigured key is entered correctly.



      But still I get this message:
      error message

      (image from another post, but it is the same message that I get, but in english.)



      No error code that I can follow.



      The computer that it is not working on is a Surface Pro 4, newest updates from yesterday evening.



      Some things that I tried (none of them had any effect on the problem):




      • Going to the device manager -> networkadapter -> delete all WAN Miniport -> action -> search for changed hardware

      • disabeling the Xbox Live-Networkservice (was not running in the first place)

      • I tried to restart the DHCP-Client, but permission denied with code 4. So I could not restart. Trying to fix this permission issue also did not work (more permissions in the registry and adding some extra users to the admin group like system and so on.). So I tried other things.


      What am I missing? Why is this setup working on several windows 10 computers, but not on this one surface?



      thanks and greetings







      networking vpn nas






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Sep 12 '18 at 12:47









      christopher2007christopher2007

      1067




      1067





      bumped to the homepage by Community 2 days ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







      bumped to the homepage by Community 2 days ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
























          2 Answers
          2






          active

          oldest

          votes


















          0














          If your Windows 10 Version matches 1709, try uninstalling Update KB4457142.



          I've had a similar Problem with IKEv2 yesterday and resolved it by temporary uninstalling the Update.






          share|improve this answer


























          • hi, thanks for the answer. But unfortunately I am using 1803. And uninstalling also had no effect. But worth a try :)

            – christopher2007
            Sep 13 '18 at 21:28



















          0














          We've had similar problems with VPN/IKEv2 and KB4457142 on version 1709. Removing KB4457142 fixes the problem. Version 1803 with the equalent KB4457128 works fine with VPN/IKEv2






          share|improve this answer
























          • also no effect.

            – christopher2007
            Sep 18 '18 at 10:08












          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%2f1357544%2fwindows-10-l2tp-ipsec-vpn-with-synology-nas-not-working%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














          If your Windows 10 Version matches 1709, try uninstalling Update KB4457142.



          I've had a similar Problem with IKEv2 yesterday and resolved it by temporary uninstalling the Update.






          share|improve this answer


























          • hi, thanks for the answer. But unfortunately I am using 1803. And uninstalling also had no effect. But worth a try :)

            – christopher2007
            Sep 13 '18 at 21:28
















          0














          If your Windows 10 Version matches 1709, try uninstalling Update KB4457142.



          I've had a similar Problem with IKEv2 yesterday and resolved it by temporary uninstalling the Update.






          share|improve this answer


























          • hi, thanks for the answer. But unfortunately I am using 1803. And uninstalling also had no effect. But worth a try :)

            – christopher2007
            Sep 13 '18 at 21:28














          0












          0








          0







          If your Windows 10 Version matches 1709, try uninstalling Update KB4457142.



          I've had a similar Problem with IKEv2 yesterday and resolved it by temporary uninstalling the Update.






          share|improve this answer















          If your Windows 10 Version matches 1709, try uninstalling Update KB4457142.



          I've had a similar Problem with IKEv2 yesterday and resolved it by temporary uninstalling the Update.







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Sep 13 '18 at 16:37









          Ramhound

          21.1k156287




          21.1k156287










          answered Sep 13 '18 at 16:05









          JIT SolutionJIT Solution

          11




          11













          • hi, thanks for the answer. But unfortunately I am using 1803. And uninstalling also had no effect. But worth a try :)

            – christopher2007
            Sep 13 '18 at 21:28



















          • hi, thanks for the answer. But unfortunately I am using 1803. And uninstalling also had no effect. But worth a try :)

            – christopher2007
            Sep 13 '18 at 21:28

















          hi, thanks for the answer. But unfortunately I am using 1803. And uninstalling also had no effect. But worth a try :)

          – christopher2007
          Sep 13 '18 at 21:28





          hi, thanks for the answer. But unfortunately I am using 1803. And uninstalling also had no effect. But worth a try :)

          – christopher2007
          Sep 13 '18 at 21:28













          0














          We've had similar problems with VPN/IKEv2 and KB4457142 on version 1709. Removing KB4457142 fixes the problem. Version 1803 with the equalent KB4457128 works fine with VPN/IKEv2






          share|improve this answer
























          • also no effect.

            – christopher2007
            Sep 18 '18 at 10:08
















          0














          We've had similar problems with VPN/IKEv2 and KB4457142 on version 1709. Removing KB4457142 fixes the problem. Version 1803 with the equalent KB4457128 works fine with VPN/IKEv2






          share|improve this answer
























          • also no effect.

            – christopher2007
            Sep 18 '18 at 10:08














          0












          0








          0







          We've had similar problems with VPN/IKEv2 and KB4457142 on version 1709. Removing KB4457142 fixes the problem. Version 1803 with the equalent KB4457128 works fine with VPN/IKEv2






          share|improve this answer













          We've had similar problems with VPN/IKEv2 and KB4457142 on version 1709. Removing KB4457142 fixes the problem. Version 1803 with the equalent KB4457128 works fine with VPN/IKEv2







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Sep 14 '18 at 7:27









          user943958user943958

          1




          1













          • also no effect.

            – christopher2007
            Sep 18 '18 at 10:08



















          • also no effect.

            – christopher2007
            Sep 18 '18 at 10:08

















          also no effect.

          – christopher2007
          Sep 18 '18 at 10:08





          also no effect.

          – christopher2007
          Sep 18 '18 at 10:08


















          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%2f1357544%2fwindows-10-l2tp-ipsec-vpn-with-synology-nas-not-working%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

          Cannot install PyQt5 The Next CEO of Stack OverflowCannot install tcpreplay 3.4.4cannot...

          Kapp-Putsch Acontecimentos | Outros artigos | Menu de navegação

          Why did early computer designers eschew integers? The Next CEO of Stack OverflowWhat register...