Have you changed any security policy such as lan manager authentication
level or storage of lm hash? Make sure you can ping the domain controllers
and wins server by name from the W98 computers. Check the Event Viewer on
the domain controllers and wins server for any pertinent problems, and
verify that they are still wins clients. Run nbtstat -RR on the domain
controllers and verify that their records show in the wins database
including the records for domain controller [1CH]. In Domain Controller
Security policy in security options check that "lan manager authentication
level" is NOT set to send ntlmv2 response /refuse lm & ntlm. Restart the
wins service on the wins server. --- Steve
"Mike S" <(E-Mail Removed)> wrote in message
news:O$(E-Mail Removed)...
> Here's the problem:
>
> We are running a Windows 2003 AD Domain. Everything was working fin until
> last this morning. Our clients are a mix of Windows XP and Windows 98. We
> have the updated DSClient installed on all 9x machines. These machines
> have
> been working fine for several months.
>
> Today, the 9x clients can't log in. The user/passwords are 100% correct.
> Windows XP machines work fine. I've also changed the default domain
> controller policy as described here:
> http://blogs.brnets.com/michael/arch...06/14/156.aspx
>
> I've also tried suggestions from here:
> http://64.233.167.104/search?q=cache...ient=firefox-a
>
> I don't know what would have happened that would have caused this to stop
> working. 9x clients at other sites still work fine. I even purged the WINS
> database at the site that's having trouble. I then did a pull replication
> from a server at a site I know was working 100%.