Windows Forum

Ask something
Discussion Locked

password change problems on win98 client

0 helpful
7 replies

by tosh74

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have a win 2003 server with AD. I am having problems with password changes on my win98 clients. The user get's prompted to change the password (as normal) and the user can change their password successfuly. Once the change has been accepted by the server the client is then sent back to the logon screen but cannot logon. In fact NOBODY can logon to the machine unless it has been rebooted. It seems as if the workstation has been denied access to the server after the password change. I had sorted these problems out (various fixes from MS) until I installed SP1 for 2003 server. Can anybody shed some light onto this ? According to MS this problem does not exist. Have setup WINS, SMB signing, disabled encrypt secure channel data (always) on server. Installed DSCLIENT et al on the workstaions.

7 replies

by blackcurrant

Hi

I don't really know how this works, but it seems to me that the Win98 machine is not communicating with the server after the password has been reset.

I had a very similar problem where a user who regularly logs onto a Win98SE machine in a Win2k/SBS2k AD environment was suddenly unable to use their password (as security is not really an issue here, there is no need to change passwords on a regular basis). I ended up having to delete their account and create a brand new one. It took several reboots before the Win98 machine could successfully log the 'new' user onto the system.

There must be a data cache that is not being refreshed after the user has changed their password. Therefore, there must be a communication issue between the Win98 client and your 2003 server.

There are just two things I can think of to check - make sure that DNS is correctly configured on the client, and make sure that a valid computer account exists for the Win98 machine on the server. Maybe try deleting the computer account, removing the Win98 machine from the domain, then connect it up again.

If the issue still persists after this, then check that the client can comminicate properly with the server, and also make sure that every person who uses this computer has a duplicate of their domain account registered as a local account too.

To be honest, I am on a crusade to get all our Win98 machines replaced because there are several little hiccups that keep occurring which cause delays and stop users from working.

One more thing - there is an advisory about SP1 for 2003 causing some applications not to work - have you checked this list of applications?

Good luck

by tosh74

Thanks for that. Seems to be a feature of Server 2003 (maybe uncle Bill is trying to tell me something).

by tosh74

This seems to have sorted itself out. I changed the LM Authentication level to "LM,NTLM - use NTLMv2 if ...." in DC GPO. Also had problems with MSBROWSE record in WINS. Workstations with shares and XP clients were registering themselves as the master browse. So I set a scheduled task to get the DC to register itself as the MSBROWSE. I then tried a password change and it worked juts fine. The logon continued after the password change

by blackcurrant

Well, thanks.

However, I do not understand this. The only time browse issues arise is when the browse master goes offline. Normally, what happens (and I'm sorry if this is old hat to you), is that when you fire up a network or the master browser crashes an election takes place to see which computer will be the browse master. This can take up to 15 minutes. Normally, the latest OS, or a domain controller will win. However, they have to be able to communicate with the rest of the network to do this.

There is a setting in the TCP/IP properties in Win98 clients that can be toggled so that a Win98 machine never forwards itself for election. However, this is normally turned off by default when it is joined to a domain.

Thanks again.

This discussion is closed to new replies.