this one is a DOOZIE. Actually, this is a single server environment so
replication was a problem. I never figured it out. I set the user back
with their old password and everything is fine. From what I can tell,
although the user was issued a new password on the server, his local
machine was using the old password to attempt to access network shares
and exchange. Exchange didn't like the old password and prompted for
the new one so no big deal, but the network shares weren't so
I think the user is the "tinkering" type and maybe screwed up the
password scheme on his desktop. I could log him on to any other
computer without a problem, and any other user could log onto his
computer without a problem. The error was directly related to himself
and his computer, which is a sure sign of tinkering.
Get this, after I reissued his old password and got him up and running
yesterday, he tinkered again and was locked out of resources this
morning. I had to go back in and fix it, and the higher ups weren't
happy with him.
I'm sure that there is a fix for this, but I've never seen this
problem before and probably won't for awhile. It seems much easier to
stick with his old password for now and then reload his system in a
I'm glad I'm not the only one experiencing this and hopefully this
thread will be of assistance down the road. It's really frustrating to
have a problem like this make you look bad, but once my user was
caught tinkering, any blame was definitely shifted off of me.
On Tue, 10 Feb 2004 12:23:07 -0500, "Dave Nickason [SBS MVP]"