Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 26 subscribers
  • Views 6710 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

XG has disabled 3DES and SHA1 in L2TP policy, what should I choose for VPN?

ArunGupta

Somewhere along the way, XG has disallowed the use of 3DES and SHA-1 as encryption/authentication choices for L2TP policy. The only methods allowed now are AESnnn and SHA2nnn. Since Windows 10 L2TP VPN does not support these encryption/authentication methods, I am no longer able to connect to the L2TP VPN. I get an error indicating that Windows could not find a matching authentication method. I checked on Microsoft website and they have it documented that the VPN can only use 3DES and SHA-1 and this cannot be changed. Even my Android 7 phone fails to connect with AES and SHA2. I can no longer create L2TP policy with 3DES/SHA-1 enabled. XG refuses to save such policies.

I have a policy already created with 3DES and SHA-1 but Windows 10/Android phone keeps dropping VPN connection within minutes if I use that policy. It used to work fine, but I am not sure which update caused it to stop working.

I need to create a VPN which works both with Windows 10 and Android phone. What should be my choice?

Thanks,

Arun



This thread was automatically locked due to age.