Random Account Lockout /Security Settings not Saving

From: Dave Grams (dgrams_at_vollrathco.com)
Date: 07/14/03 

Date: Mon, 14 Jul 2003 14:00:04 -0700

2 Issues Here:

#1) Users are calling into our helpdesk that thier
network accounts just get locked out for no particular
reason. They try to print or access a shared network
drive and find out that their access is denied.
Or when dial-up users call through a VPN to get their
email, our system locks them out.. (randomly.)
The clients that are being used are Win95, Win98, WinME,
Win2000, WinXP.
It has happened on all formats that I can think of -
Maybe not Win2000.
I checked the security log and have not been able to put
2 and 2 together as of yet.
Our one WinME user seems to be the only repeat offender,
on almost daily basis, but all other OS's just get
knocked off with no particular rhyme or reason.
I did a few google searches, but have not come up with
any answers except some like: "upgrade all your clients
to Win2000".
Well.. that isn't going to happen.

#2) I go into our Domain Controller (Windows2000 Server)
and try to modify the domain secutiry.
(Trying to keep #1 from happening....)
I can do things like change the 'wrong password' settings
from 0 to 999, etc etc... and the new policies
never takes effect.
I've seen suggestions of using the policy refreshing
program... (can't remember the name of the program off-
hand...) That has done nothing. I've rebooted the
server, hoping that the new security would take effect...
Nothing....

I do have Microsoft's almighty solution to almost every
article on Windows2000 applied as well... "Upgrade to the
latest W2k service pack"

any ideas for me to try on either?

Relevant Pages

  • Re: sbsrexe.exe service shuts down computer
    ... SBS Server is hard wired to run only as the first domain controller in the ... I have found out the reason with the following log. ...
    (microsoft.public.windows.server.sbs)
  • Re: Promoting SQL Server to a Domain Controller?
    ... We would be using this as the secondary domain controller. ... No other reason) ... What do you have for a DHCP, DNS, and WINS server? ... > running SQL Standard to a Domain controller using dcpromo? ...
    (microsoft.public.sqlserver.server)
  • Re: How to install w2k3 CAL?
    ... Any particular reason that would be the case? ... is a brand new server. ... no domain controller or AD. ...
    (microsoft.public.windows.server.general)
  • Re: Event ID 5719 No windows NT or windows 2000 domain controller is available ...
    ... That event means that the server could not find a domain controller for whatever ... reason at that time. ... successful logon attempts in the security log would be more indicative of a user ...
    (microsoft.public.win2000.security)
  • Re: Should DCs with DNS point to self first?
    ... > when you have all locally, by doing so IMO you're wasting server ... > good reason to do so IMO. ... there are far more issues associated with pointing a DC at itself for primary DNS than pointing at something else. ...
    (microsoft.public.windows.server.active_directory)