VPN not working in latest image

Technical Support
, , , ,
1

@bertin is building his own image to include VPN support.

  • VPN support was working in WEC7 V2.2b2.
  • VPN does not work in WEC7 V2.3
3

Receive the “a network error has occured, or the server has closed the VPN Connection error” message, in a dialog box, upon initial connection

After the initial error message, if we try and redial the vpn connection we just receive an “Opening port” message and nothing else…

4 
188257 PID:400002 TID:445000a Exception 'Raised Exception' (0x6ba): Thread-Id=0445000a(pth=a2888000), Proc-Id=00400002(pprc=86402c10) 'NK.EXE', VM-active=0153002a(pprc=a281f138) 'udevice.exe'
 188258 PID:400002 TID:445000a PC=efe44834(k.coredll.dll+0x00054834) RA=800a16c8(kernel.dll+0x000306c8) SP=b22af0a4, BVA=00000000
 188258 PID:400002 TID:445000a L2TP: (_IPsecPolicySetEx) - * ERROR * OPEN FWP FILTER ENGINE FAILED. STS[23]
 188259 PID:400002 TID:3a10032 L2TP: * NOTICE * Recv WorkItem started
 188260 PID:400002 TID:445000a Unknown: DEBUGCHK failed in file d:\bt\2643\private\winceos\comm\ndismods\wan\l2tpv6\l2tp_ipsec_if.c at line 283 
 188260 PID:400002 TID:445000a DEBUG_BREAK @ef5d9758 Ignored.
 188260 PID:400002 TID:445000a L2TP: * ERROR * SET IPSEC POLICY FAILED. STS[23]
 188262 PID:400002 TID:20a003a PppNdisIssueRequestWorker Status PENDING 259
 188296 PID:400002 TID:6c5008e PPP: -PppNdisDoSyncRequest - Type=0 Oid=OID_TAPI_MAKE_CALL (7030115) Status=c0000001
 188296 PID:400002 TID:6c5008e !NdisTapiLineMakeCall: NdisRequest returned 0xC0000001
 188297 PID:400002 TID:6c5008e PPP: ERROR from NdisTapiLineMakeCall c0000001
 188300 PID:65f007a TID:667007a RASCS_Disconnected: Ecode=619
 188318 PID:400002 TID:667007a PPP: +PppNdisIssueRequest - Type=1 Oid= (7030103)
 188319 PID:400002 TID:667007a PppNdisIssueRequest Type:1
 188319 PID:400002 TID:667007a PppNdisIssueRequest CALLBACK MODE
 188321 PID:400002 TID:20c003e PppNdisIssueRequestWorker Status PENDING 259
5

Here is the link about the registry entry that you must delete before you can setup vpn to an l2tp ipsec server behind nat. I am not sure why your windows 10 desktop failed to connect, but it could be similar.

6

I reverted BSP v 2.2 and OSDesign v2.2. Again I added the VPN catalog items and did a clean sysgen. The VPN didn’t seem to work with v2.2 either. This is using the development board

Since v2.2b2 seemed to work, I will try and add our modem drivers and settings needed to create the image for v2.2 on our instrument and see if the VPN works with the cell modem.

7

I created an based on your v 2.2 BSP and OSDesign v 2.2 with (Bootloader v2.3, not sure if it is relevant) and have had no success with VPN…so I am assuming that V2.2 VPN is broken as well.

Is there any progress on your end?

8

vpn not working in 2.3 log

9

one needs to add the following registry keys for vpn to work in version 2.3 (BSP/OSDesign)

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\BFE]
"LoadAsync"=dword:00000001

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\BFE\DependsOn]
"AFD"="Drivers\\BuiltIn\\AFD"

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\IKEEXT]
"LoadAsync"=dword:00000001

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\IKEEXT\DependsOn]
"BFE"="Drivers\\BuiltIn\\BFE"
"CmService"="Drivers\\BuiltIn\\CmService"
10

The problem was created by the new BusEnum2.dll (the new bus enumerator driver under the HKLM\Drivers\BuiltIn key) being enabled (to load the drivers asynchronously ) and not having the above info in the registry to indicate the dependencies needed.

Thanks for Germano and Andy for the help.