Veeam is happy to provide a free NFR license (1 year, 2 sockets) to all certified IT Pros. The license allows for the non-production use of Veeam Availability Suite v9.5 in your home lab, without any feature limitations. It works for both VMware and Hyper-V environments
Course Of The Month
9 days, 4 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
VPN 619 Error -Selective Users - WIN2k8 R2
Posted on 2013-10-31
Hello All,
Bizzarre issue.. A few users including myself this morning is unable to connect to the VPN, although a handful of other users can.
Myself and the other ones having issues were all able to connect last night to the VPN with no issues, but this morning we are recieving the following error :
Windows could not connect using the user name and password provided. Error 619
Troubleshooting steps :
1. Verified my credentials are valid
2. verified I can VPN with the Administrator account as well as a handful of other accounts
3. Verified no changes have been made on policy or the affected USERS in AD
4. I recreated the PPC PPTP VPN connection
5. I have rebooted the VPN server
6. I verified DIAL IN settings in AD are configured properly
7. Verified users is a member of the Remote Access group per policy
I am stumped as to what is going on ? Help.. suggestions?
Bizzarre issue.. A few users including myself this morning is unable to connect to the VPN, although a handful of other users can.
Myself and the other ones having issues were all able to connect last night to the VPN with no issues, but this morning we are recieving the following error :
Windows could not connect using the user name and password provided. Error 619
Troubleshooting steps :
1. Verified my credentials are valid
2. verified I can VPN with the Administrator account as well as a handful of other accounts
3. Verified no changes have been made on policy or the affected USERS in AD
4. I recreated the PPC PPTP VPN connection
5. I have rebooted the VPN server
6. I verified DIAL IN settings in AD are configured properly
7. Verified users is a member of the Remote Access group per policy
I am stumped as to what is going on ? Help.. suggestions?
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
-
4
4 Comments
Here are a couple of the warnings and errors on the event log ont he VPN server :
Error 1 :
The connection was prevented because of a policy configured on your RAS/VPN server. Specifically, the authentication method used by the server to verify your username and password may not match the authentication method configured in your connection profile.
Warning :
CoId={97F45876-21AC-46C0-9
Error 1 :
The connection was prevented because of a policy configured on your RAS/VPN server. Specifically, the authentication method used by the server to verify your username and password may not match the authentication method configured in your connection profile.
Warning :
CoId={97F45876-21AC-46C0-9
I am looking at the logs some more and came across the users that is being denied access comes up with the following error :
Event ID 6273 :
Reason Code : 8
Reason : The specified user account does not exist.
Event ID 6273 :
Reason Code : 8
Reason : The specified user account does not exist.
Ok, so I think the issue may be with a server that one of the IT had resurrected from the dead yestesrday..
It doesnt make sense "specified user account does not exist" when AD shows my username on there, but I am betting this server that was ressurected probably had its on AD and somehow this VPN server is trying to authenticate against that AD...
standby.. as I unplug that server and retest the VPN.
It doesnt make sense "specified user account does not exist" when AD shows my username on there, but I am betting this server that was ressurected probably had its on AD and somehow this VPN server is trying to authenticate against that AD...
standby.. as I unplug that server and retest the VPN.
Update : Yup.. looks like the old server they had resurrected was the culprit. It is acting as an AD as well on the same domain??? Anyhow.. issue resolved..
Question : Why did my VPN server look to authenticate the users from the "old" server rather than the current AD that its been authenticating from this whole time?
Question : Why did my VPN server look to authenticate the users from the "old" server rather than the current AD that its been authenticating from this whole time?
Featured Post
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
New Windows 7 Installations take days for Windows-Updates to show up and install. This can easily be fixed. I have finally decided to write an article because this seems to get asked several times a day lately.
This Article and the Links apply to…
This article explains how to install and use the NTBackup utility that comes with Windows Server.
This tutorial will give a an overview on how to deploy remote agents in Backup Exec 2012 to new servers.
Click on the Backup Exec button in the upper left corner. From here, are global settings for the application such as connecting to a remote Back…
This tutorial will walk an individual through the steps necessary to enable the VMware\Hyper-V licensed feature of Backup Exec 2012. In addition, how to add a VMware server and configure a backup job.
The first step is to acquire the necessary licen…
Suggested Courses
Earn Certification
HTML5 Specialist - Certification
Free withPremium
Course of the Month9 days, 4 hours left to enroll
Earn Certification
MCSA Configuring Windows 7 Exam 70-680
$49.00$44.10
615 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.