windows 2000 can't detect windows server 2003 Domain

[Guest ViNC3 via WinServerKB.com]

Hi to all pros out there,

 

i have read through the article you gave, but in the article, it doesn't

shows how windows 2000 clear cache.

 

i will try to clarify the problem i am facing,

previously this company have a PDC (windows NT 4.0) with domain name

(WORLDGROUP) with a few Server (windows 2000) connected to the domain network

as member of the domain. Now they want to replace the old NT 4.0 machine to

new machine with (windows server 2003)

 

so firstly, i install the windows server 2003 with domain name (WORLDGROUPC)

then link it to the network. after that, i have migrated from the NT 4.0

(WORLDGROUP) to WIN2003 (WORLDGROUPC)

 

then after that, they said they want to use WORLDGROUP as the domain name, so

i have rename the Domain Name from WORLDGROUPC to WORLDGROUP by using

Microsoft Domain Renaming Tool.

 

After that, by using one of the serverABC with windows 2000 that connected to

the domain. i disjoin the ServerABC from domain WORLDGROUP and simply join a

workgroup, then i disconnect the old NT (WORLDGROUP) machine from the network

and connect the new Win2003 (WORLDGROUP) *after renaming* machine to the

network.

After that, i disjoin the serverABC windows 2000 from workgroup, and try to

join back to WORLDGROUP, but this time, is the new machine win2003 with the

same Domain Name.

 

The serverABC just wouldn't join, it keep on showing the domain Name

WORLDGROUP couldn't not be found. (it seem like the serverABC win2000 still

have some cache memory that referring back to the old (winNT) WORLDGROUP

instead of the new (win2003)WORLDGROUP.

 

i have tried to use XP machine to join the new WORLDGROUP win2003, and

everything works fine, only win2000 seem to kept on referring back to the old

(winNT) WORLDGROUP.

 

it seem kinda confusing, but this is what really happened in this company

right now >.<

 

really appreciated to any help provided

thanks in advance

 

regards,

Vince

 

--

Message posted via WinServerKB.com

http://www.winserverkb.com/Uwe/Forums.aspx/windows-server/200802/1