star_topology
In Runtime
- Messages
- 195
Howdy everyone,
I'm having quite a perplexing problem.
In part of our network, we have Windows 98 computers (and old ones at that) logging into a Windows 2000 Server. Up until now, we've had very few problems... at least none like this.
Last week, everything was working fine, but as of today, our Win98 machines are denied logon access to the domain. Most password errors are greeted with the yellow exclamation point saying no domain was able to process blah blah blah. However, we are confronted with the dreaded red X dialog box and "The domain password you supplied is not correct, or access to your logon server has been denied."
Nothing appears in the Event Viewer when a logon is attempted. Because of this, it appears to me that the password isn't even being processed at all. We have begun reformatting one server, but we are attempting to find a way to work around this problem on another part of our network facing the exact same situation.
We've done quite a bit of googling and have found some possible remedies, but none have worked so far. Anyone have any ideas on how to fix this?
Thanks in advance, unless we find a solution with which I will follow-up and post.
I'm having quite a perplexing problem.
In part of our network, we have Windows 98 computers (and old ones at that) logging into a Windows 2000 Server. Up until now, we've had very few problems... at least none like this.
Last week, everything was working fine, but as of today, our Win98 machines are denied logon access to the domain. Most password errors are greeted with the yellow exclamation point saying no domain was able to process blah blah blah. However, we are confronted with the dreaded red X dialog box and "The domain password you supplied is not correct, or access to your logon server has been denied."
Nothing appears in the Event Viewer when a logon is attempted. Because of this, it appears to me that the password isn't even being processed at all. We have begun reformatting one server, but we are attempting to find a way to work around this problem on another part of our network facing the exact same situation.
We've done quite a bit of googling and have found some possible remedies, but none have worked so far. Anyone have any ideas on how to fix this?
Thanks in advance, unless we find a solution with which I will follow-up and post.