Discussion Locked

Win95 clients on NT4 domain

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

We have a number of Win95 PCs in the NT4 domain. At certain times after a user account is unlocked by admin or enforced password change is made, when the use logs on an error message is displayed
"A network error has occurred". Clicking OK returns to the login prompt. Rebooting does sometimes work, but the only consistent resolution is to log in using a different username. I've searched everything I can and found no reference to this problem.
Keeping a log of errors leads me to believe it's possible due to slow replication between PDC/BDC although I've been unable to confirm this.

8 replies

by oskiller

Synchronization is generally the problem. How large is your domain and how many user accounts? If you do not have a large number of accounts, you can do what I do. After changing the password, use Server Manager, select the PDC and synchronize the entire domain. Advise the user to wait about 2 minutes and everything should be golden.

by paul

Relatively small domain (only a couple of hundred workstations/user accounts) with single PDC and BDC. I'm almost certain that it is a replication problem.

by mckaytech

Interesting problem and other than doing packet traces, I'm sure exactly how you would track it down.

But one thing you may want to try is a Resource Kit utility called "setprfdc". You could run it on the workstation to point to the PDC for authentication. If login then works reliably, that would support your replication theory. It might also be useful to check the environment variables for the login server - in our system, we occasionally get some bizarreness where the authenticating server is many miles (and router hops) from the one that should get used.

paul

by paul

The problem is too uncommon to warrant trying that - only 3 occurrences this month. All servers/workstations are in one building - pretty small network.

by paul

The problem is too uncommon to warrant trying that - only 3 occurrences this month. All servers/workstations are in one building - pretty small network.

by deltree

I share your frustration as this issue sometimes pops up with our W95 users during a password change attempt. Two things that I do to minimize this behavior:
First, force a net accounts /sync between BDC & PDC after unlocking accnt.
Note; (if there is more than one BDC on your LAN) It would be advisable to synchronize entire domain, since it is unpredictable which BDC will respond to the user password request. This will eliminate any inconsistency on your DC's.
Second, delete the users .pwlfile. Then have the user login and change password.

I always thought the first step was enough until the 'network error' popped its ugly head again. The second step (in addition to the first) seems to clear up the problem in my environment.

by paul

I think synchronisation is the problem, I'd also considered .pwl files (since it happens on 95 workstations only). I'll try forcing synchronisation after changing passwords.

This discussion is closed to new replies.