S
S Houser
We have a single W2K server/domain controller that was
running great until a couple of weeks ago. Our network
consists of about 14 PC's evenly divided between W2k and
Win98, all using static IP addresses. Started having
issues with both W2k and Win98 clients getting logon
denied messages. I discovered that the Local Group Policy
database on the server was corrupt, so I rebuilt it using
instructions from MSKBA #278316. Now the server boots up
noticably faster, and the W2k clients can log on again
after I re-register their machine names. But the Win98
clients still get "The domain password you supplied is not
correct, or access to your logon server has been denied"
when trying to log onto the domain - unless the server has
been rebooted and is just sitting at the login prompt.
Everyone can login in and access the server/domain unless
I actually log onto the server as Administrator, in which
case the Win98 machines get the above error message. So
I'm thinking this is some kind of Local/Domain policy
issue but I can't make any headway on it. I've tried
deleteing/resetting machine accounts in AD, and registry
mods on the Win98 clients to disable direct hosting and
SMB signing. No luck yet. Any help greatly appreciated.
running great until a couple of weeks ago. Our network
consists of about 14 PC's evenly divided between W2k and
Win98, all using static IP addresses. Started having
issues with both W2k and Win98 clients getting logon
denied messages. I discovered that the Local Group Policy
database on the server was corrupt, so I rebuilt it using
instructions from MSKBA #278316. Now the server boots up
noticably faster, and the W2k clients can log on again
after I re-register their machine names. But the Win98
clients still get "The domain password you supplied is not
correct, or access to your logon server has been denied"
when trying to log onto the domain - unless the server has
been rebooted and is just sitting at the login prompt.
Everyone can login in and access the server/domain unless
I actually log onto the server as Administrator, in which
case the Win98 machines get the above error message. So
I'm thinking this is some kind of Local/Domain policy
issue but I can't make any headway on it. I've tried
deleteing/resetting machine accounts in AD, and registry
mods on the Win98 clients to disable direct hosting and
SMB signing. No luck yet. Any help greatly appreciated.