Thursday, June 3, 2010

Error 126, 1068, 70020 unable to VPN

I had an employee with the following problem.  They were unable to VPN and were receiving the errors in the Title.  They were also unable to connect to some wireless AP at customer's site.   Here is what I did.  One i stopped Eset from Scanning the C:\windows\system32 directory.   This allowed the Windows Remote Management Access service to start.   I then looked at HKEY_LOCAL_MACHINE\System\Services\RASMAN\PPP\EAP and noticed that Symantec had entry in 13,25, but not 26.   I read somewhere to delete all entries except these 3 because they are windows default entries.  Since Symnatec (Symantec was installed on this computer, but removed) had entries in I decided to delete 13 and 25.  I deleted them and then rebooted hoping they would self populate, but they did not.

I then exported these registry entries from another Vista computer and then imported them.  The problem was now fixed.