Do you get an error mesage on the XP client? Do you have a VPN client installed on your machine (this will break native IPSec), or did you have one installed before?
Basically, for Windows XP and PSK, the following settings need to be done: - Networking: Type of VPN = L2TP IPSec VPN - Security: *Disable* "Require data encryption" - Security: set PSK in "IPSec Settings"
during our testing at various clients, we found that the most common problem is a disabled native ipsec service. If you have or had installed an IPSec client, your IPSec service had been disabled during their install routine.
In order to activate it again, do a right click on 'My Computer' and select 'Manage'.
Now the 'Computer Management' Window opens. Expand 'Services and Applications' in the left pane and select 'Services'. You will now see all Windows services on the right pane.
Search for 'IPSEC Services' and see if it is disabled. If yes, change the startup state to 'Automatic' again and start the service.
Hi everybody, yesterday i got L2TP over IPsec working using the native XP-Client. Nonetheless at the moment it works only in a non-NATed environment what is not acceptable for my setup. Anyway if there is interest so far i can post a brief how-to with my configuration. Another point is that the predefined connection-type MS L2TP client on the ASL uses a PSK but i want to use X.509-certificates for authentication. In the handbook i read that this predefined connection type uses a standard-policy. To create my own connection type i need to know what concrete policy settings i have to use. Does anybody know? Still working on this issue, Jan
You are right that ASL uses PSK for the "MS Windows L2TP over IPSec" connection. In order to create a certificate-based L2TP connection, use the normal "Roadwarrior" connection, pick "MS_DEFAULT" as policy and enable "L2TP Encapsulation".
Hi Stephan! Now i got it working with NAT too! It's tricky because that NAT-T patch doesnt show up regularly on windowsupdate.com ... I had to go to the catalog and do a manual search for the ID Q818043 to find it at all. Seems to me that Microsoft tries to hide this patch... Actually it is working now and i will try to setup certificates!
I am using ASL 5.004 and in my webconfig there is no MS_DEFAULT-policy! I chose 3DES instead, will it work too or what is MS-DEFAULT? I know that PFS has to be disabled but what algorithms do i have to choose? Thanks in advance!
Concerning MS_DEFAULT: there is a bug in the backup converter for importing ASLv4 backups. The MS_DEFAULT policy gets erased by the import. You can either add it manually afterwards (see my previous post) or wait for the next Up2Date, which contains a fix for this issue.
