Changing Network Passwords on 98 clients

Do you have a BDC? Sometimes the BDC authenticates the password change and the PDC doesn't recognize the change until the machines are synchronized.

Also, which client are you using, Windows Logon or Microsoft Networking? If you use the WindowsLogon, change the password on the PDC but not on the local .pwl file (the Windows Logon), you'll have to use the original password to unlock the .pwl file which then contains the new password for the NT domain. If this is the problem, you need to change the Windows Password too.

In the settings for passwords on the Server there is a settings box that does not allow a password change on the workstation. this could be the reason why you need to change on the server. I would change it on the server to require a change at next logon for the user then I would get rid of the windows logon by deleting the .pwl file for the local machine password. This will accomplish two things, too allow passwords to only be server authenticated and then also to have one less logon for the user. Let Me Know!

I can't really verify it here cause all our servers are now windows 2000.
Check your account policy and make sure that "User must logon to change password" is disabled.
Then try to change password from Windows 98.

The real question should be What REG Setting do I need to add to the PDC to cause an Update to occure more oftin.

If you post that question you will the answer for us all.

I have the same problem. However, after a password change I sync the Domain within the Server manager utility.

As a matterof fact I will post the question - I need the answer also....

I don't know how to help you since you seem to be rejecting valid answers without any explanation. THE PROBLEM IS DOMAIN SYNCHRONIZATION.

You need to describe your network: how big it is, how many BDC's you have and how many users you have.
--- to the last poster and to you ---

Here's a registry key you need to look at:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters

SOmeone may have changed your ReplicationGovernor from 100% to reduce traffic.

The ReplicationGovernor defines the size of the data transferred on each call to the PDC and the frequency of the calls. When you adjusting the ReplicationGovernor:

It reduces the size of the buffer used on each call from the BDC to the PDC,
so that a single call does not occupy the WAN link for too long.

It causes NetLogon to hibernate between calls, so other applications can access the WAN link.

Edit:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters

From the Edit menu, Add Value as a type REG_DWORD. ReplicationGovernor is a percentage (0 - 100) of the 128KB buffer size and that same percentage of WAN usage. The deafult is 100%.

If you set ReplicationGovernor to 50, synchronization will use a 64KB buffer (128 x 0.50) and will only have an call on the net for a maximum of 50 percent of the time.

If you set ReplicationGovernor too low, synchronization may never complete.

This question was closed by the author