Re: Preparing Network Connections... forever
- From: "Jorge Silva" <jorgesilva_pt@xxxxxxxxxxx>
- Date: Mon, 27 Nov 2006 22:48:17 -0000
Hi
Please post here the results for
ipconfig /all
for both servers.
Remeber both domains need to resolve each other, so make sure that both servers can reach eachother zone and that the new tree can resove the _msdcs domain.
--
*************************************************
I hope that the information above helps you
Good Luck
Jorge Silva
MCSA + Exchange + MSCE
*************************************************
"Gaetan" <me@xxxxxxxxxxxxx> wrote in message news:bqmmm2hb7ksc01av2jvqhutc1u9rh35gh7@xxxxxxxxxx
In a forest with only one domain, I created a new domain tree and let the DCPROMO Wizard install and
configure the DNS service.
I guess the wizard decided to punch-out before everything was properly configured because when I
boot this new DC, it takes a solid 5 minutes before the "preparing network connections..." screen
goes away.
I did try to reboot a couple of times in case the whole process needs it ... alas no success. Then I
added secondary zone transfesr between my new domain and the first domain of the forest to make sure
both sides could resolve addresses ... no luck.
Now when i boot the new DC, I get these events in the Directory Services event log:
===================
Active Directory was unable to establish a connection with the global catalog.
Additional Data
Error value:
1355 The specified domain either does not exist or could not be contacted.
Internal ID:
3200cd1
User Action:
Make sure a global catalog is available in the forest, and is reachable from this domain controller.
You may use the nltest utility to diagnose this problem.
===================
Active Directory could not resolve the following DNS host name of the source domain controller to an
IP address. This error prevents additions, deletions and changes in Active Directory from
replicating between one or more domain controllers in the forest. Security groups, group policy,
users and computers and their passwords will be inconsistent between domain controllers until this
error is resolved, potentially affecting logon authentication and access to network resources.
Source domain controller:
DEVDC
Failing DNS host name:
82d33e8a-faee-41bd-8206-793069703a58._msdcs.vmdev.local
bla bla bla
===================
Out of desperation, I added "82d33e8a-faee-41bd-8206-793069703a58._msdcs.vmdev.local" in the forward
looking zone "client-1.local" of the new DC. Got the same errors as above each time I restart.
Somehow, it appears that the new DC in the new domain is unable to locate the GC of the forest.
Is there something else I need to configure?
Info:
1 forest
Original domain in the forest is "vmdev.local" (PDC is devdc.vmdev.local)
New domain is "client-1.local" (PDC is client-1dc.client-1.local)
Regards!
.
- Follow-Ups:
- Re: Preparing Network Connections... forever
- From: Gaetan
- Re: Preparing Network Connections... forever
- References:
- Preparing Network Connections... forever
- From: Gaetan
- Preparing Network Connections... forever
- Prev by Date: Re: GPO to restrict software installs
- Next by Date: DC of the Parent Domain can't Ping the hostname of the DC Child Do
- Previous by thread: Re: Preparing Network Connections... forever
- Next by thread: Re: Preparing Network Connections... forever
- Index(es):
Relevant Pages
|
