Discussion Locked

Error Changing Password....

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have a strange problem that NO ONE has been able to answer, not even my instructors at school.
Particulars: Windows nt 4.0 network, SP6 on all machines. No policies in place or defined. User profiles are very vanilla.
The platforms are HP machines:
1.) vectra vli8's
P3 500, 128mb ram, 12gb hd

2.) vl400
P3 733, 128 mb ram, 12gb hd

3.)vl
pentium p3 450, 32-128mb ram, 10gb hd

No users can change their password on the vli8 machines, but CAN change it on ANY of the other machines. The error comes up as:
"unable to change password on this account ( C0000BE ). I did what was recommended in technet to no avail. Any Ideas?

7 replies

by mikeanselmi

The only thing I can think of is a SID mismatch. Remove the computer account from the domain and reattach the pc to the domain.

by nettek

I am assuming that the clients are running NT Workstation? This problem originally surfaced when NT Workstations with SP 3 tried to change their password on an NT Server with SP 4. To resolve your problem, try one of the following:
1. Upgrade to Service Pack 4 or later on the clients, or
2. Run Regedit.exe, and navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\LSA
Change the value of "RestrictAnonymous" from 1 to 0.

Hope that helps.

by sstrickl

This was technet's answer...I upgraded all machines to sp6. The key mentioned is not there either. We are not running any kind of policies. I think the problem may lie along the previous answer, I am trying it as soon as I have a minute.

by nettek

Okay, let's try this again. According to Microsoft, error C00000BE specifically means that the workstation cannot find the PDC, which is required in order to change the password.

First, verify that you can ping the PDC by name (not just by IP address). Second, verify that you can issue a NET USE statement to the PDC. For example, "c:\net use f: \\PDCname\ShareName". If you have a problem with either one of these, then it is a name resolution issue. If you are running WINs, try manually adding the IP addresses of the WINs servers to your workstations (as opposed to relying on the DHCP server to provide the WINs addresses). If you are not running WINs, add an LMHOSTS file on the clients that will tell them how to find the PDC.

Ifthat doesn't work, go to User Manager for Domains and try turning off "Users must log on in order to change password".

Hope that helps.

This discussion is closed to new replies.