Windows Forum

Ask something
Discussion Locked

Password Change Issue

0 helpful
7 replies

by joshg 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have a 3 site W2K AD domain setup running T1 lines between them. None of the Windows 98 users can change their passwords regardless of location. They can log into the network fine and are prompted for a password change but then they get the "No Domain Controller" box and only the Windows PWD gets changed.

The users can access shares on the 3 servers as well as Exchange 2000 on the main server. DNS is setup and workstations can PING all three DC's.

Thoughts?

7 replies

by maxwell edison

Microsoft has developed extensions for the Windows? 95, Windows 98, and Windows NT? 4.0 operating systems that allow those client platforms to take advantage of features provided by the Windows 2000 Active Directory service. These client extensions were developed for those who wish to deploy Windows 2000 Server in environments with Windows 95, Windows 98, and Windows NT 4 based client workstations.

Windows 9x and Windows NT 4 based clients lack many of the features of Windows 2000 Professional that are related to Active Directory. The Active Directory client extension is an upgrade or patch for Windows 95, Windows 98, and Windows NT 4.0, which enables the following Active Directory features:

Note: Active Directory Client extension provides necessary APIs to change the password to any Windows 2000 based domain controller.

See link to whole article, more explanation and additional links:

http://www.microsoft.com/windows2000/server/evaluation/news/bulletins/adextension.asp
REMOVE SPACES from the pasted URL

by joseph moore

Something else to try (and I don't know if it will take care of your problem, but it couldn't hurt!) is to modify the LMHOSTS file on the Win9x machines. You can define a domain controller and the NetBIOS domain name of your Win2K domain in the LMHOSTS file. Often times, doing that will take care of authentication problems.
Please read Technet article Q180094 for details and instructions:
http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q180094
(please remove any spaces)

hope this helps

by tsrl

configure wins server & in the client pc add the wins address..

in the wins add the DC 's ip static mappings..

hope this will solve your problem...

also configure wins in each location & they should replicate between each other.

u can easily configure wins in the existing servers ....

This discussion is closed to new replies.