In thread titled "VPN error 812 and error 629 - testing VPN setup on internal LAN and getting this error", Glasgow suggested "allowed access in AD via the dial-in tab" to solve this issue.
I think it isn't a good solution because doing that prevents NPS to apply Network Access Conditions to the User Connection Request (unless option box "Ignore User Account Dial-in Properties" is selected).
The 812 error seems appearing for several reasons:
- when Server Network Policy and Client Connection Profile don't match on the Authentication Protocol. It is easy to fix;
- when NPS does not update (in memory I guess) value added to "Tunnel Type" Condition in Network Policy. That is more tricky.
Let's give an example for the second situation:
- a new Network Policy is set with "Day and time restrictions", "Operating system", "Windows group" and "Tunnel type" Conditions;
- "Tunnel Type" is valued with "PPTP" only;
When trying to connect VPN client, 812 error may appears.
How to fix that ?
- select additionnal value to "Tunnel type" Condition, like "L2TP" to obtain value "L2TP OR PPTP";
- apply and close the Network Policy;
- connect VPN client, it works !
- revert the Network Policy to the good value for "Tunnel type" Condition, here it is "PPTP" only;
- apply and close the Network Policy;
- connect VPN client, it works and your Network Policy is now well set up !
Hope this workaround will help some of you,
Nacime Amimar & Axel Limousin
ITSI - IT Training School
93500 Pantin, France
- Changed type Tiger LiMicrosoft employee Wednesday, July 20, 2011 3:07 AM