windows 2000 can't detect windows server 2003 Domain

[ViNC3 via WinServerKB.com]

Hi to all pros out there,

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

 

[Phillip Windell]

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.

Use the correct DNS machine in the TCP/IP specs. It should be only the DC
of the new domain.

If there is a WINS Server it may be confused because the new domain has the
same netbios Name as the old one. You may have to delete out all the WINS
records except for any static ones and let it rebuild. Make sure that the
old NT DC does not use this WINS Server or it will re-enter the entries that
you do not want. You should never allow the old NT DC back on the LAN at
this point because of the name conflict between the two domains.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/ISA2004_AccessRules.html

Troubleshooting Client Authentication on Access Rules in ISA Server 2004
http://download.microsoft.com/download/9/1/8/918ed2d3-71d0-40ed-8e6d-fd6eeb6cfa07/ts_rules.doc

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp

Microsoft ISA Server Partners: Partner Hardware Solutions
http://www.microsoft.com/forefront/edgesecurity/partners/hardwarepartners.mspx
-----------------------------------------------------

 

[ViNC3 via WinServerKB.com]

Hi Phillip,

You mention something about "Use the correct DNS machine in the TCP/IP specs,
it should be only the DC of the new domain"

sorry, but can you please tell how to do it step by step?
and please teach me how to delete the WINS records too.

sorry for the trouble, i am still a noob in the server and stuff >.<

thanks

regards,
Vince