Windows 98 clients

Can someone give me an explination as to why I can't seem
to join Windows 98 clients to an existing 2003 domain?
I've installed the Active Directory Client extensions
(granted from the 2000 ADV Server disk) but it still
can't find the domain controller to validate the
password. I can ping the domain controller successfully.
Do I need the 2003 client?

No you do not need a 2003 client. One thing to be sure of
is that AD is running in mixed mode. If it is then verify
WINS settings.


>-----Original Message-----
>Can someone give me an explination as to why I can't seem
>to join Windows 98 clients to an existing 2003 domain?
>I've installed the Active Directory Client extensions
>(granted from the 2000 ADV Server disk) but it still
>can't find the domain controller to validate the
>password. I can ping the domain controller successfully.
>Do I need the 2003 client?
>.
>

It doesn't hurt to have the DSClient software installed on the Win 98 clients, it allows the clients to be able to authenticate to any DC that is available. It also allows legacy Win 9X clients to search for AD objects...And several other advantages

But as Stephen stated you will need to ensure that the clients have a WINS server to contact for their NetBios name resolution. Also verify that their DNS settings are correct

Hope this helps.

The mode doesn't make any difference. That only counts for domain
controllers.

In your domain controller security policy, computer config, windows
settings, security settings, local policies, security options disable the
digitally sign communications (always) policy.


"wylie" <(E-Mail Removed)> wrote in message
news:93BAD85D-C8F9-4505-8E20-(E-Mail Removed)...
> It doesn't hurt to have the DSClient software installed on the Win 98
clients, it allows the clients to be able to authenticate to any DC that is
available. It also allows legacy Win 9X clients to search for AD
objects...And several other advantages.
>
> But as Stephen stated you will need to ensure that the clients have a WINS
server to contact for their NetBios name resolution. Also verify that their
DNS settings are correct.
>
> Hope this helps.