Re: Migrated BDC cannot locate PDC to complete AD install
From: Al Mulnick (amulnick_No_SPAM_at_ncDOTrr.com)
Date: 01/17/05
- Next message: Ann: "Having problem setting the password for an ADAM user using C#"
- Previous message: John Negus: "Re: Problems setting stie options"
- In reply to: Scott: "Re: Migrated BDC cannot locate PDC to complete AD install"
- Next in thread: Scott: "Re: Migrated BDC cannot locate PDC to complete AD install"
- Reply: Scott: "Re: Migrated BDC cannot locate PDC to complete AD install"
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 16 Jan 2005 19:05:22 -0500
Have you tried Netdiag and analyzed the results? Sorry not to have
mentioned that before.
On the already working domain controller, dcdiag is additionally useful
(netdiag and dcdiag there). On the server that won't promote, netdiag is
the tool.
You also want to make sure that they share the same name servers. The
promoted DC should be using itself (most likely anyway) and the new server
should also be using the new DC (I'm assuming DNS is running on the new
domain controller. The important thing is that they use the same name
servers (DNS and WINS) until successful promotion.
Al
"Scott" <Scott@discussions.microsoft.com> wrote in message
news:475A1AF3-8FEC-44E3-A4DD-8448695DEDFC@microsoft.com...
>I guess that is the Million dollar question..what about the DNS that may be
> configured incorrectly? I can ping the servers from the clients by pinging
> the DNS Domain name, and netbios name.
>
> "Al Mulnick" wrote:
>
>> In that case, have you checked DNS?
>>
>>
>>
>> "Scott" <Scott@discussions.microsoft.com> wrote in message
>> news:6A5C5B3A-066E-49A4-8F7A-6530132A27B4@microsoft.com...
>> > Al,
>> >
>> > Sorry I wasn't very clear. I did already upgrade the PDC to AD by doing
>> > an
>> > in-place upgrade on the PDC and then creating the AD via the AD wizard.
>> > This
>> > refers to the BDC that had not yet been upgraded to 2003. I did the
>> > upgrade
>> > on the BDC, by performing an in-place upgrade as well.
>> >
>> > "Al Mulnick" wrote:
>> >
>> >> You're supposed to upgrade the PDC vs. the BDC. W2K3 can't exist as a
>> >> BDC.
>> >> Can you double check which is the PDC? (in W2K3, it's PDCe).
>> >> What you want to do is check the domainmgr tools in NT4 to see who's
>> >> listed
>> >> as the PDC. Then verify that W2K3 sees the same by checking the roles
>> >> of
>> >> the W2K3 machine with AD tools. They likely don't see each other the
>> >> same
>> >> way.
>> >>
>> >> "I upgraded a NT 4.0 BDC to 2003." How'd you do that exactly?
>> >>
>> >> Al
>> >>
>> >>
>> >> "Scott" <Scott@discussions.microsoft.com> wrote in message
>> >> news:2DC1B271-438D-460B-8800-11CCBEA4E348@microsoft.com...
>> >> >I upgraded a NT 4.0 BDC to 2003. The AD wizard cannot find the Domain
>> >> > Controller for the domain. All the clients (XP) are able to
>> >> > authenticate
>> >> > to
>> >> > the Domain Controller, and have been able to for a few weeks. Why
>> >> > can
>> >> > this
>> >> > BDC not see the domain controller? I can ping the DC using the DNS
>> >> > name,
>> >> > and
>> >> > IP Address.
>> >> >
>> >>
>> >>
>> >>
>>
>>
>>
- Next message: Ann: "Having problem setting the password for an ADAM user using C#"
- Previous message: John Negus: "Re: Problems setting stie options"
- In reply to: Scott: "Re: Migrated BDC cannot locate PDC to complete AD install"
- Next in thread: Scott: "Re: Migrated BDC cannot locate PDC to complete AD install"
- Reply: Scott: "Re: Migrated BDC cannot locate PDC to complete AD install"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
