AD user account lockout when making VPN connection from Vista PC

Hi,

We are in the process of upgrading our laptops/desktops to Windows Vista and I have now installed the first Vista laptop (name COMP-PC1). This laptop has an admin account and a roaming profile for my domain account (COMPDOM\myaccount).

Whenever a VPN connection is made from that laptop to our network (using aXsGuard VPN), my domain account gets locked out. I enabled netlogon logging as suggested in many solutions to this problem, and I am 100% sure that it is this one Vista laptop that is causing the problem.

This is what I get in netlogon.log:
07/10 11:40:05 [LOGON] COMPDOM: SamLogon: Network logon of COMP-PC1\myaccount from COMP-PC1 Entered
07/10 11:40:05 [LOGON] COMPDOM: NlPickDomainWithAccount: COMP-PC1\myaccount: Algorithm entered. UPN:0 Sam:1 Exp:0 Cross: 0 Root:1 DC:0
07/10 11:40:05 [LOGON] COMPDOM: SamLogon: Network logon of COMP-PC1\myaccount from COMP-PC1 Returns 0xC000006A

The strange thing is that the user account is COMP-PC1\myaccount, which does not exist as an account on the laptop. This account "myaccount" is an AD user account in domain COMP.

So I am 100% sure that the vista laptop is causing the problem, but how do I proceed to find which software is sending the wrong user account/password?

This laptop was installed using the admin account, and I am 99,99% sure that no services use myaccount. After all setup was done, I logged in with myaccount to get the roaming profile. This logon process maps some network drives using the account that logs in (these drive mappings are not persistent), but I don't think this should be the cause of the problem, as this lockout happens when logged in as admin on the laptop (and user myaccount is not logged in at that moment).


Kind regards,

Patrick Elsen
Patrick ElsenICT Infrastructure ManagerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Alan HardistyCo-OwnerCommented:
The logon process mapping the drives is the cause of your problem as it will have remembered the username / password used (in this case the myaccount one).
For testing purposes - can you stop the drive mapping from occurring when loggin on and if your account does not get locked out - you know where the problem lies.
What you can do to resolve the problem is to delete the mappings from the client (net use * /delete /y)
then manually map the drives and force the username and password:
net use x: \\computer\share /user:domain\username password /persistent:yes - you can leave the persistent if you don't want it and obviously substitute the drive letter, computername, share name, domain, username and password.
Repeat this for all mapped drives and then logoff, logon on again using the logon script and the lockout should stop happening.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Active Directory

From novice to tech pro — start learning today.