LogisticsOne
asked on
Active Directory changes not updating
We are running Windows Small Business Server 2003 SP2 and a new user that I created in AD can't log on. It looks like my user was created correctly, but AD is not updating something.
When I try and log on I get the message "The system could not log you on. Make sure your User name and domain are correct, then type your password again. Letters in passwords must be typed using the correct case" as if they didn't exist.
I created the new user by copying a user that had been disabled, but I know I unchecked the box during the copy for User is Disabled.
Then I deleted the new user and copied from an existing user that was not disabled and got the same message as if the account didn't exist.
Then I took a user account that was disabled, re-enabled it and set a new password and tried to log in with that, but it says "Your account has been disabled. Please see your system administrator"
Any ideas as to what might be going on?
When I try and log on I get the message "The system could not log you on. Make sure your User name and domain are correct, then type your password again. Letters in passwords must be typed using the correct case" as if they didn't exist.
I created the new user by copying a user that had been disabled, but I know I unchecked the box during the copy for User is Disabled.
Then I deleted the new user and copied from an existing user that was not disabled and got the same message as if the account didn't exist.
Then I took a user account that was disabled, re-enabled it and set a new password and tried to log in with that, but it says "Your account has been disabled. Please see your system administrator"
Any ideas as to what might be going on?
A dcdiag is alway a good place to start.
ASKER
Just did the dcdiag. Received the following info:
-------------------------- -------
Doing primary tests
Testing server: Default-First-Site-Name\PR ISRVR
Starting test: Replications
[Replications Check,PRISRVR] A recent replication attempt failed:
From BKUPSRVR to PRISRVR
Naming Context: DC=XXXXXXXXXXX,DC=local
The replication generated an error (8614):
The Active Directory cannot replicate with this server because the t
ime since the last replication with this server has exceeded the tombstone lifet
ime.
The failure occurred at 2011-03-03 16:21:18.
The last success occurred at 2010-08-17 11:14:04.
327500 failures have occurred since the last success.
REPLICATION-RECEIVED LATENCY WARNING
PRISRVR: Current time is 2011-03-03 16:23:02.
DC=XXXXXXXXXX,DC=local
Last replication recieved from BKUPSRVR at 2009-01-01 11:14:04.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
-------------------------- ---------- ------
Now the weird thing is that we disabled a user last friday and that user was successfully disabled on both the primary and backup Doman controllers. We have also created users within the past month and had no problems (and both DC have the same user information, except for this most recently added user), so I don't know if the above error is the true problem, it's a red herring, or it's indicative of a bigger issue that has all of a sudden cropped up.
--------------------------
Doing primary tests
Testing server: Default-First-Site-Name\PR
Starting test: Replications
[Replications Check,PRISRVR] A recent replication attempt failed:
From BKUPSRVR to PRISRVR
Naming Context: DC=XXXXXXXXXXX,DC=local
The replication generated an error (8614):
The Active Directory cannot replicate with this server because the t
ime since the last replication with this server has exceeded the tombstone lifet
ime.
The failure occurred at 2011-03-03 16:21:18.
The last success occurred at 2010-08-17 11:14:04.
327500 failures have occurred since the last success.
REPLICATION-RECEIVED LATENCY WARNING
PRISRVR: Current time is 2011-03-03 16:23:02.
DC=XXXXXXXXXX,DC=local
Last replication recieved from BKUPSRVR at 2009-01-01 11:14:04.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
--------------------------
Now the weird thing is that we disabled a user last friday and that user was successfully disabled on both the primary and backup Doman controllers. We have also created users within the past month and had no problems (and both DC have the same user information, except for this most recently added user), so I don't know if the above error is the true problem, it's a red herring, or it's indicative of a bigger issue that has all of a sudden cropped up.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The question is somewhat misleading, our real problem is we have our main SBS and a backup domain controller on another server and they stopped communicating.
For this one, we ended up calling Microsoft and I wasn't in on the repair but the technician demoted our backup DC, did something to it and then added it back in. Our guy who actually worked on it with the tech apparently logged the tech into his machine and went home so I don't know the details and he doesn't either, but essentially we paid Microsoft $300 to pretty much do what snusgubben recommended.
For this one, we ended up calling Microsoft and I wasn't in on the repair but the technician demoted our backup DC, did something to it and then added it back in. Our guy who actually worked on it with the tech apparently logged the tech into his machine and went home so I don't know the details and he doesn't either, but essentially we paid Microsoft $300 to pretty much do what snusgubben recommended.