PDA

View Full Version : L2TP/IPSec VPN? Getting nowhere fast on the Wizard forum so thought I would try here


ADB100
7th June 2007, 05:39 PM
Help.......

I am not getting any help on the Wizard forum so I thought I would post here in an attempt to find someone who can shed some light on what I am experiencing with my HTC Wizard running WM6 and L2TP/IPSec VPN over Wireless.

First off - L2TP/IPSec VPN works flawlessly with the last WM5 ROM from QTEK. Ever since I installed WM6 on my Wizard I have had a problem with L2TP/IPsec VPN.

My current setup is WM6 5.2.1413 (Build 17913) originally provided by mUn but with the Enterprise files from the 5.2.318 ROM. With the 5.2.1413 ROM 'naked' L2TP/IPSec just would not work no matter what I tried. I rebuilt this ROM with one of the Kitchens but removed the Enterprise files (4 directories) and replaced them with the 4 Enterprise directories from the 5.2.318 ROM originally posted by Faria.

I Flashed the Wizard OK and go through the initial setup. Now I connect to my Wireless network and save the profile, I then add a VPN connection on the Wizard that connects to my VPN router. If I attempt to connect it fails. Now if I disable the Wireless and soft reset the Wizard, then as soon as it has started whilst Battery Status is showing something like 12MB of Program Memory, I connect the Wireless and then attempt to connect the VPN it works. From this point on I can disconnect the VPN, reconnect, disconnect the Wireless, reconnect etc and it works every time

If I disconnect the wireless and soft reset again but this time wait until Battery Status is showing 28MB of Program Memory, then connect the wireless and then attempt to connect the VPN it fails and will never work again unless it is soft-reset and everything is started quickly. I have tested this several times now and the behaviour is consistent.


This smells to me like some initialisation issue at bootup that I am somehow managing to get around by attempting to start the VPN whilst the Wizard isn't fully initialised?

Does anyone know what process at boot up is likely to cause this behaviour? And more importantly how to fix it?

Thanks

Andy