VPN Error 649, VPN suddenly not working

[avit]

Hi,

At my work we run a windows server 2003 small business server vpn . Everything worked perfectly until yesterday, suddenly an error 649 "no dial-up permissions. I have checked everything. I have also found some suggestions on the internet but didn't get the perfect solution, people here an idea what this could be?

[CLONEOPS]

I want to know what the VPN protocol you use? As you so sure there are those many points (PPTP, IPsec (AH), IPsec (ESP), L2TP, SSL, etc.) In addition, the router must support VPN pass through support as an option. Without that it is nothing with a VPN behind a NAT router! Go to User Manager for Domains and make sure your user account has the "Grant dialing permissions for user" box checked.

[Kirmiac]

VPN Error 649 can occur if the username is the same as the domain name, if the username is "system", and even if you dialing a Windows NT RAS and your password has expired. You need to ensure that the user is allowed to dial-in. Also check PPTP filtering. For the test, disable PPTP filtering on the server (Net Stop RASPPTPF) and see if you can re-establish a connection without a filter.

[Allan.d]

VPN problem can occur if dial-in properties is incorrect or the domain name was not correct. Open Active Directory Users and Computers and c right - click on administrator, select Properties, change the Dialing tab, ensure its not deny access. Then click OK and test. If the problem persists, please include the domain name in the User Name box. If the problem persists, please try another user account.

[Zenon]

VPN Error 649 is generally caused due to user account issues. You need make sure that you are logged in as administrator and valid by logging on from the domain. You can also try as a user name, adding the domain name as domain\user. Also by default if you have assigned or created template to make sure you delete it and create a new. Please review microsoft policies and recreate RRAS for testing purposes and assign licenses online for the administrator. And please make sure you have enabled scripting for the administrator and please do not remove for testing.

[Hoobastank]

Please make sure to deny remote access permission is checked in the remote access policy configuration. Switching solutions grant remote access permission of the problem. Go to User Properties, select Dial-in. Check Allow access. That should also solve the problem. The user uses his computer username at home instead of domain user name. The customer configured dial-in media incorrectly.