Back up to the Incoming L2TP Category

L2TP Client: Windows

From AAISP Support Site
Revision as of 23:16, 30 September 2016 by David-T (talk | contribs) (Add Windows 10 notes)
Jump to navigation Jump to search

Windows 7

Connecting with Windows 7 was almost as easy except that the default connection settings don't work. You have to edit the connection properties and on the Security tab change 'Type of VPN:' to 'Layer 2 Tunneling Protocol with IPsec (L2TP/IPSec)' otherwise it only tries PPTP, and change 'Data encryption:' to 'Optional encryption (connect even if no encryption)' as it doesn't like A+A's certificate (because RevK declines to use a root certification authority recognised by Microsoft, or is it that Microsoft declines to recognise the root certification authority chosen by RevK). I guess the alternative would probably be to add the root certificate to the machine in question. Anyway, with those two changes it works fine.

Watch out if you are using IPv6. It seems that Win7 negotiates a non-routable IPv6 address with the LNS. You have to discard this address and manually configure one of your routed IPv6 addresses. ipconfig /release6 is your friend here.

Windows 10

Windows 10 seems very keen on using IPsec with L2TP. To turn this off, in an Administrator Command Prompt do:

   SC STOP RASMAN    ; you may have to wait a bit for this to stop
   SC QUERY RASMAN   ; ensure it is STOPPED
   REG ADD HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Rasman\Parameters /v ProhibitIpSec /t REG_DWORD /d 1 /f

Also, once the connection has been created:

  1. Network and Sharing Centre
  2. Change adapter settings
  3. Find the L2TP connection
  4. Right click and choose Properties
  5. Go to the Security Tab
  6. In the 'Authentication' section
  7. Select 'Allow these protocols'
  8. Ensure 'Challenge Handshake Authentication Protocol (CHAP)' is enabled.