nt4 PDC upgrd to W2k AD - Password changing NG

[Guest]

have done the Upgrade of the NT4 PDC to W2K

W2K AD server is all patched, is a DNS server, Time is sync'

Problem when users are prompted to change their password's the system returns saying it "the system cannot change your password now because the domain FUBAR is not available
...

Ive done some Technet'ing and tryed working the problem..still N

I have NOT upgraded my BDC's yet still NT4 BDC'

anyone have some ideas for me

thank
bil
PS sorry for cross posting Not quite sure which forum this should be under

 

[Chriss3]

Hello Bill.

First you can post the same post in multiple newsgroups.

Can you resolve the FQDN of your DC and Domain from your clients.

ex: DC-01.domain.com
ex: domain.com

--
Regards
Christoffer Andersson

No email replies please - reply in the newsgroup

have done the Upgrade of the NT4 PDC to W2K

W2K AD server is all patched, is a DNS server, Time is sync'd

Problem when users are prompted to change their password's the system

returns saying it "the system cannot change your password now because the
domain FUBAR is not available"

 

[Guest]

PS
IF I login on to either the W2K-AD-DC of a BDC I can change the password of an accoun
ctl-alt-del > change password > enter old, enter new....> O
work

but NG from clien

bil

 

[Chriss3]

Have you tried this when the client only points to the DNS on your Windows
Server with the zone for Active Directory?

 

[Guest]

Ive got my terminal setup to point DNS to the w2k-dc/pdc emulatio
set primary suffix to snd.com so my machine looks like bmellott.snd.co

still NG trying to change passwor

bill

 

[Cary Shultz [A.D. MVP]]

Chriss,

Hope that you do not mind if I step in for a quick second!

Bill,

I would make sure that what ever DHCP 'Server' you are using is issuing the
correct options along with the IP Address lease. By options I mean Option
003, Option 006 and Option 015. If these are downlevel clients ( you did
not specify what OS your clients are running ) then you would need to
include Option 044 and Option 046 ( WINS related ). All of your clients
should point to your Internal WIN2000 DNS Server. Let's not forget that
Domain Controllers are DNS Clients as well!

I might also install the Support Tools ( from the Service Pack CD or from
the MS Web Site - always try to run the Support Tools from the same level SP
that you are running on your servers! In a pinch, you can install them from
the WIN2000 Server CD as well.... ) and run a couple of things: dcdiag /c /v
and netdiag /v as well as netdom query fsmo.

You might want to also ensure that your DNS Forward Lookup Zone is accurate
( it has the four sub-folders: _msdcs, _sites, _udp and _tcp ) and that you
have a Reverse Lookup Zone. You might also want to make sure that you have
set up your Sites correctly ( this last one has nothing to do with your
problem - just good to make sure that it is there and set up! ).

Let us know how that works.

Cary