General discussion

Locked

Accessing a domain controller

By Eminent87 ·
Hi all,

Here's the situation. The owner of the firm username is just his first name (don't ask me why, it was what he wanted). Although it's not the preferred way but it has been working. Up until another user brought in his laptop that has the same username (his first name) as the owner of the firm. This causes a conflict because same username but different password. Although the laptop is not part of the domain (on it's own workgroup), it thinks that the owner of the firm is trying to log on and automatically locks the account up. Is there a way to prevent the account from locking up?

I've noticed on regular windows 2000 file server (one that's not a domain controller), the account does not lock up. There is about 7 or so errors (event 681 and 529) in the security log but that's about it. Is there a way to change it so that the user can get access to a shared drive on the domain controller with his home laptop without causing the account lock up? Thanks in advance!

This conversation is currently closed to new comments.

5 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

by nsolop In reply to Accessing a domain contro ...

Hi,

Try this out. Made the person that uses the laptop to logon locally instead of login to the domain.
Provide this user one domain account with the proper priviledges so when he needs to access a share folder on the server the system is going to ask for a validation and he can use "domain\username" format as the username and the password.
I have no idea if you have another way to solve this.

Regards from Argentina.

Nicolas.

PS: Sorry about my english!.

Collapse -

by Eminent87 In reply to

Hi Nicolas,

Thanks for your reply. The currently configuration is exactly what you're describing. The laptop is not part of the domain. He is logging on from his laptop (windows xp) locally. On a regular server it will ask for authentication and he'll enter in his domain account and everything works fine. The problem with the domain controller is that it'll lock up the account before it even let the user authenticate.

Collapse -

by Eminent87 In reply to

Hi Nicolas,

Thanks for your reply. The currently configuration is exactly what you're describing. The laptop is not part of the domain. He is logging on from his laptop (windows xp) locally. On a regular server it will ask for authentication and he'll enter in his domain account and everything works fine. The problem with the domain controller is that it'll lock up the account before it even let the user authenticate.

Collapse -

by Eminent87 In reply to Accessing a domain contro ...

Okay... figured out what my problem was. Security policy is enfored on the domain controllers to lock out users account after 4 invalid logon. This security policy is not define for any other groups except for the domain controllers. I guess I could take out this policy on the domain controller but it is a security risk. I also tried changing the user local account to something other than his first name but for some reason it still thinks it is joe.

Collapse -

by Eminent87 In reply to Accessing a domain contro ...

This question was closed by the author

Back to Windows Forum
5 total posts (Page 1 of 1)  

Related Discussions

Related Forums