Re: Preparing Network Connections... forever

Tech-Archive recommends: Fix windows errors by optimizing your registry



Gaetan,

I hope that I am not stating the obvious with this: what is the IP Address
of the internal DNS Server in the TCP/IP configuration settings on your new
Domain Controller? A simply ipconfig /all will tell you this. It must be
only an internal DNS Server. Anything else will give you this problem
(preparing network connections). If this Domain Controller is a also the
DNS Server and your Domain Controller has a static IP Address of, say,
192.168.25.30 then we should see this as the IP Address of the internal DNS
Server. Also, have you checked the spelling of the DNS Zone? That
sometimes leads to a problem.

--
Cary W. Shultz
Roanoke, VA 24012

"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!


.



Relevant Pages

  • RPC Endpoint Mapper Error
    ... We are adding our first Windows 2003 Domain Controller to a Windows ... I checked DNS entries with articles from Microsoft on ... PASS - All the DNS entries for DC are registered on DNS server ... List of NetBt transports currently bound to the Redir ...
    (microsoft.public.win2000.active_directory)
  • Re: the system cannot log you on now because the domain <domain>is not available
    ... What I would suggest trying, at least temporarily, is to open Domain Controller ... The other main concern is that dns is configured correctly for the whole domain. ... controllers running dns with the AD domain zone and NEVER an ISP dns server anywhere ... > event log showed teh failed attempts at locating the DC. ...
    (microsoft.public.windows.server.networking)
  • Re: Domain Controller not resolving name
    ... Make sure the domain controller is also a DNS server. ... IP running DNS, WINS, and DHCP. ...
    (microsoft.public.windowsxp.general)
  • Re: DHCP box and Windows 2003 Server Domain Controller documentati
    ... Changing the configuration of the Domain Controller will take some ... We installed the DNS services in our Domain Controller (Windows ... DNS server should use forwarders to your ISP's DNS servers ... And you should really use DHCP for this - DHCP running on your DC, ...
    (microsoft.public.windows.server.general)
  • [LONG - PLS HELP] Issues on DNS
    ... Active Directory successfully replicated using the NetBIOS ... or fully qualified computer name of the source domain controller. ... DNS Server: ... The DNS server was unable to open zone mydomain.local in the Active ...
    (microsoft.public.windows.server.dns)