Re: DOMAINPREP problem

From: Dave Clark (dave.clark_at_ddess.org)
Date: 03/16/04 

Date: Tue, 16 Mar 2004 04:36:00 -0800

Getting closer to the issue. It appears that after we
had a firewall crash, our VPN were restored, but we have
not had a successful replication with our FOREST root DNS
server (seems port 53 and 445 are blocked down the VPN).
So we will be working on resolving that, getting a good
replication again, and see if that will help eliminate
that problem.

So it seems the issue MAY be that it was not able to
contact the Schema Master for this same reason.

Fingers Crossed.

>-----Original Message-----
>Ran the netdiag (after downloading it from MS). No
>errors appear in the rather large file that is created.
>All passes appear.
>
>I also downloaded the dcdiag, but the program is
erroring
>on me before even running. Will have to figure out why
>the program is not liking to run.
>
>>-----Original Message-----
>>Dave:
>>
>>Run netdiag on the server that you are attempting to do
>this on. Netdiag /v
>>/l /debug. Review the output, ensure no errors.
>>
>>Then, run dcdiag on your domain controllers, ensure no
>errors either.
>>
>>Tim
>>
>>--
>>Timothy McMichael
>>timmcmic@online.microsoft.com
>>
>>This posting is provided "AS IS" with no warranties,
and
>confers no rights.
>>"Dave Clark" <dave.clark@ddess.org> wrote in message
>>news:d88c01c40a9d$3452a070$a101280a@phx.gbl...
>>> I am trying to extend my CHILD DOMAIN schema for
>Exchange
>>> 2000. The forest has already been preped.
>>>
>>> When I run the SETUP /DOMAINPREP when it comes to the
>>> action screen and DOMAINPREP is selected from the drop
>>> down box, i get the following message:
>>>
>>> The component "Microsoft Exchange Domain Preparation"
>>> cannot be assigned the action "DomainPrep" because:
>>> -Setup is unable to access the Windows 2000 Active
>>> Directory
>>> -Failed to contact the Schema Master server for this
>>> Active Directory forest.
>>>
>>> Now, I am logged in as a DOMAIN ADMIN user. Can use
>all
>>> the normal AD administration tools for AD, so it seems
>>> that #1 is not what the issue is. Also, I can PING
the
>>> FOREST SM without an issue with it FQDN.
>>>
>>> What else could be causing this error?
>>>
>>> Thanks!
>>>
>>
>>
>>.
>>
>.
>

Relevant Pages