Fianally the answer although not pretty.

From: DougH (DougH_at_discussions.microsoft.com)
Date: 12/16/04


Date: Thu, 16 Dec 2004 12:45:02 -0800

Actually after changing their password on any machine they WON'T be able to
authenticate. Here's the result of looking at the case with Microsoft. They
are rewriting their article since they are not clear and it does insinuate
that DSC is the resolution to most of the connectivity problems with 2K and
above. See below for my workaround for this issue.

"After discussing the NoLMHash issue with the developer of the DSClient; it
has been determined that Q299656 is unclear on the authentication process.
The DSClient allows Windows 9x clients to use NTLMv2 to setup the secure
channel to the Domain Controller so the client can pass its password in
LMHash format. The DSClient does not change the way the 9x client
authenticates in terms of LMHash or NTHash; thus, 9x clients will always use
LMHash. Enabling NoLMHash on a DC will prevent 9x clients from logging onto
the domain after their password is changed since the LMHash will no longer be
generated and stored on the server.

We apologize for the inconvenience and will submit a change request to have
the document adjusted accordingly."

If you enable NoLMHash storage:

1.) Upgrade to Windows 2K and higher all the machines that you can.
2.) Identify the accounts that will be logging into the Windows 98 machines
with the DSC client.
3.) For those minimal accounts that need the LM hash set their accounts to
Never Expire, and User Can't Change Password. (Notice: This is a security
risk)
4.) If you need to change a password(s) you will need to do the following:
Disable NoLMHash, reboot your DC's and then change the password(s) on the
account(s). The LM Hash is stored. Enable NoLMHash again.

I recommend for security reseasons that you set your Windows 98
LMCompatabilty level to NTLM or NTLMv2. (see article Q239869). This will
encapsulate the LM hash when passed.

v/r
Doug Hoglan

"Val" wrote:

>
>
> >
> >Yes, I know it say that but this is vindicated by "Users
> on Windows
> >95-based computers or Windows 98-based computers will not
> be able to
> >authenticate to servers by using their domain account
> unless they have the
> >Directory Services Client installed on their computers."
> in the same
> >article. They have DSC installed, and the latest and
> greatest version at
> >that.
> >
>
> They are able to authenticate to servers by using their
> domain account w/DSC, but aren't able to change their
> domain passwords. No contradiction.
>
> --
>
> Val
>
>



Relevant Pages

  • Re: NT4 Client in W2K3 AD migrated / SID
    ... Adding new accounts is no problems. ... But the next time I check the ACL ... >to suggest that you pick one problematic Windows NT ... First I migrated the clients with ADMT 2.0, ...
    (microsoft.public.windows.server.migration)
  • Re: Native Mode and Win9x/NT Clients Authentication
    ... in a native Windows 2000 environment (one in which there are no ... Kerberos was created by the Massachusetts Institute ... Windows 2000 machines and downlevel clients, then both Kerberos and NTLM are ... > will authenticate using Kerberos. ...
    (microsoft.public.win2000.security)
  • Re: New post: Integrated Windows Authentication for remote users
    ... All clients connect and authenticate using MSIE using W2k or better. ... > Microsoft MVP (Windows, Security) ... >> priveliges denied on the web server or on the firewall to this web ...
    (microsoft.public.inetserver.iis.security)
  • Re: New user on 98 machine cannot log on to 2003 domain
    ... > no Windows 9x machine users would be able to login to the network. ... users who had accounts before the domain controllers were ... Users with accounts created after the upgrade ... > cannot login to the domain from 9x clients. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Native Mode and Win9x/NT Clients Authentication
    ... Windows 9x or NT machine, ... I assume that this is for a Windows 2000 AD in Native mode! ... > will authenticate using Kerberos. ... How will Windows 9x/NT clients ...
    (microsoft.public.win2000.security)

Loading