Thank you Kurt for your reply. I will try to answer yours questions. Please
note that this is not a single setup. I have these setup located all over
the country and they all are cutter setups. All similar configuration
(different IP/Domains).
First node (ab999NodeA.ab999.mnopq) installed using default from DC Promo.
Domain name is ab999.mnopq.
Ran DCPromo on ab999NodeB to join existing tree/domain.
Installed DNS on ab999NodeB.
As far as I can tell, all replication is happenning fine.
DNS does resolve properly.
All FSMO roles are on ab999NodeA, never moved.





"Kurt" <lorentzenkurt@nospam.hotmail.com> wrote in message
news:120pcn4l7gbln06@corp.supernews.com...
> Can you tell us a bit more about your setup? You say installed "with all
> the standard defaults". Of course if you installed 2 W2K servers and
> selected all of the defaults during a DCPromo, you would have created two
> entirely independent domains rather than a single domain with 2 DCs.
> So....
>
> What is the domain name (you can use a pseudonym if your security warrants
> it?
> Is the second domain controller able to replicate with the 1st? (DNS,
> group policy, Netlogon share, User and Computer accounts, etc?)
> Does DNS resolve the domain name? (nslookup domain.local)
> Are all of the FSMO roles on the first DC, or did you transfer some to the
> other DC?
>
> ...kurt
>
>
> "Dragon" <baadil_nospam@hotmail.com> wrote in message
> news:upUAWhWQGHA.2012@TK2MSFTNGP14.phx.gbl...
>> Hi,
>>
>> I have the following setup in my lab:
>>
>> 2x Windows 2000 Std Servers running on HP harware
>>
>> Both systems are domain controllers using standard defaults in DCPromo
>> and installing DNS during initial DCPromo. No changes are made to the
>> system except taking default. After DCPromo DNS is installed on the
>> secondary server as well.
>>
>> First server: DNS1 = 2ndServer, DNS2=1stServer
>> Second Server = DNS1 = 1stServer, DNS2=2ndServer
>>
>> Now at times, when I have 2nd server shutdown and restart the 1st server,
>> it is hanging at "Loading Network Configuration" screen. Sometime it may
>> take up to 45 minutes before I see the login. I have tried swapping the
>> DNS entries in the IP properties but I still get the same.
>>
>> My second issue is that I often see clients complaining "unable to find a
>> domain controller" etc. I would think that I might have a network issue
>> but I have the same exact setup at other locations with same issues.
>> Please note that these systems do not connect to any other system or
>> network (no internet either). I have also tried deleting the Dot domain
>> but no success.
>>
>> Any ideas what I am doing wrong here?
>>
>> thanks.
>>
>
>