Home All Groups Group Topic Archive Search About

Problems locating PDC on win2k3 server

Author
9 Feb 2006 12:31 AM
crfroehlich
I'm running one (and only one) DC on a windows 2003 server, and I'm having a
series of problems.  First, I cannot raise the domain function level to
server 2003, because "the PDC could not be contacted."  My DC ought to be the
PDC as there are no other DCs.  If I run dcdiag, I get some of the following
error messages:
"Starting test: FsmoCheck
         Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1355
         A Primary Domain Controller could not be located.
         The server holding the PDC role is down."

In addition, I'm trying to run Exchange sever 2003 setup on another win2k3
server; and I cannot run ForestPrep.  I receive unknown errors, which I
assume are related to the PDC issue.  Any help with this would be much
appreciated.

Author
9 Feb 2006 5:35 AM
Ace Fekay [MVP]
In news:08768CC2-796B-492B-A597-7BE5B83D093A@microsoft.com,
crfroehlich <crfroehl***@discussions.microsoft.com> stated, which I
commented on below:
Show quoteHide quote
> I'm running one (and only one) DC on a windows 2003 server, and I'm
> having a series of problems.  First, I cannot raise the domain
> function level to server 2003, because "the PDC could not be
> contacted."  My DC ought to be the PDC as there are no other DCs.  If
> I run dcdiag, I get some of the following error messages:
> "Starting test: FsmoCheck
>         Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1355
>         A Primary Domain Controller could not be located.
>         The server holding the PDC role is down."
>
> In addition, I'm trying to run Exchange sever 2003 setup on another
> win2k3 server; and I cannot run ForestPrep.  I receive unknown
> errors, which I assume are related to the PDC issue.  Any help with
> this would be much appreciated.

Make sure you are ONLY using this DC as the DNS address in IP properties. If
you have any ISP DNS servers, it may be contacting them asking them where
YOUR internal domain services are. DNS stores this stuff as SRV service
location records and if you point your machines to anything other than YOUR
interna DNS that hosts the AD zone, numerous issues will occur, promise.

If this machine is dual homed, such as providing NAT for internet access,
that vastly complicates it. There are a series of steps to clean that up.


--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Having difficulty reading or finding responses to your post?
Instead of the website you're using, I suggest to use OEx (Outlook Express
or any other newsreader), and configure a news account, pointing to
news.microsoft.com. This is a direct link to the Microsoft Public
Newsgroups. It is FREE and requires NO ISP's Usenet account. OEx allows you
to easily find, track threads, cross-post, sort by date, poster's name,
watched threads or subject.

Not sure how? It's easy:
How to Configure OEx for Internet News
http://support.microsoft.com/?id=171164

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft MVP - Windows Server Directory Services
Microsoft Certified Trainer
Assimilation Imminent. Resistance is Futile.
Infinite Diversities in Infinite Combinations.

The only thing in life is change. Anything less is a blackhole consuming
unnecessary energy.
===========================
Author
9 Feb 2006 3:29 PM
crfroehlich
By IP properties, do you mean the TCP/IP Properties for the network
connection?  If so, those are correct.  If there are other IP settings, where
would I find those?  I should note, I was replicating my DNS server to a
win2000 DNS server; but I decommissioned that machine.  Could this be part of
the problem?  I see SRV records for -_ldap under pdc; but I don't know what
else I'm looking at.  I don't have that many DNS records just yet.  Would it
be easier delete the zone, uninstall DNS and reinstall it?  The server is
single homed.

Also, I checked the Operations Master properties; and pdc.domain.com shows
up in all the records.  Thanks for your help.

Show quoteHide quote
"Ace Fekay [MVP]" wrote:

> In news:08768CC2-796B-492B-A597-7BE5B83D093A@microsoft.com,
> crfroehlich <crfroehl***@discussions.microsoft.com> stated, which I
> commented on below:
> > I'm running one (and only one) DC on a windows 2003 server, and I'm
> > having a series of problems.  First, I cannot raise the domain
> > function level to server 2003, because "the PDC could not be
> > contacted."  My DC ought to be the PDC as there are no other DCs.  If
> > I run dcdiag, I get some of the following error messages:
> > "Starting test: FsmoCheck
> >         Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1355
> >         A Primary Domain Controller could not be located.
> >         The server holding the PDC role is down."
> >
> > In addition, I'm trying to run Exchange sever 2003 setup on another
> > win2k3 server; and I cannot run ForestPrep.  I receive unknown
> > errors, which I assume are related to the PDC issue.  Any help with
> > this would be much appreciated.
>
> Make sure you are ONLY using this DC as the DNS address in IP properties. If
> you have any ISP DNS servers, it may be contacting them asking them where
> YOUR internal domain services are. DNS stores this stuff as SRV service
> location records and if you point your machines to anything other than YOUR
> interna DNS that hosts the AD zone, numerous issues will occur, promise.
>
> If this machine is dual homed, such as providing NAT for internet access,
> that vastly complicates it. There are a series of steps to clean that up.
>
>
> --
> Ace
>
> This posting is provided "AS-IS" with no warranties or guarantees and
> confers no rights.
>
> Having difficulty reading or finding responses to your post?
> Instead of the website you're using, I suggest to use OEx (Outlook Express
> or any other newsreader), and configure a news account, pointing to
> news.microsoft.com. This is a direct link to the Microsoft Public
> Newsgroups. It is FREE and requires NO ISP's Usenet account. OEx allows you
> to easily find, track threads, cross-post, sort by date, poster's name,
> watched threads or subject.
>
> Not sure how? It's easy:
> How to Configure OEx for Internet News
> http://support.microsoft.com/?id=171164
>
> Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
> Microsoft MVP - Windows Server Directory Services
> Microsoft Certified Trainer
> Assimilation Imminent. Resistance is Futile.
> Infinite Diversities in Infinite Combinations.
>
> The only thing in life is change. Anything less is a blackhole consuming
> unnecessary energy.
> ===========================
>
>
>
Author
9 Feb 2006 9:18 PM
crfroehlich
Oddly enough, we had a power failure this morning; when the server came back
up, the pdc issue seemed to have resolved itself.  Perhaps the server simply
needed to be rebooted?

Show quoteHide quote
"Ace Fekay [MVP]" wrote:

> In news:08768CC2-796B-492B-A597-7BE5B83D093A@microsoft.com,
> crfroehlich <crfroehl***@discussions.microsoft.com> stated, which I
> commented on below:
> > I'm running one (and only one) DC on a windows 2003 server, and I'm
> > having a series of problems.  First, I cannot raise the domain
> > function level to server 2003, because "the PDC could not be
> > contacted."  My DC ought to be the PDC as there are no other DCs.  If
> > I run dcdiag, I get some of the following error messages:
> > "Starting test: FsmoCheck
> >         Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1355
> >         A Primary Domain Controller could not be located.
> >         The server holding the PDC role is down."
> >
> > In addition, I'm trying to run Exchange sever 2003 setup on another
> > win2k3 server; and I cannot run ForestPrep.  I receive unknown
> > errors, which I assume are related to the PDC issue.  Any help with
> > this would be much appreciated.
>
> Make sure you are ONLY using this DC as the DNS address in IP properties. If
> you have any ISP DNS servers, it may be contacting them asking them where
> YOUR internal domain services are. DNS stores this stuff as SRV service
> location records and if you point your machines to anything other than YOUR
> interna DNS that hosts the AD zone, numerous issues will occur, promise.
>
> If this machine is dual homed, such as providing NAT for internet access,
> that vastly complicates it. There are a series of steps to clean that up.
>
>
> --
> Ace
>
> This posting is provided "AS-IS" with no warranties or guarantees and
> confers no rights.
>
> Having difficulty reading or finding responses to your post?
> Instead of the website you're using, I suggest to use OEx (Outlook Express
> or any other newsreader), and configure a news account, pointing to
> news.microsoft.com. This is a direct link to the Microsoft Public
> Newsgroups. It is FREE and requires NO ISP's Usenet account. OEx allows you
> to easily find, track threads, cross-post, sort by date, poster's name,
> watched threads or subject.
>
> Not sure how? It's easy:
> How to Configure OEx for Internet News
> http://support.microsoft.com/?id=171164
>
> Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
> Microsoft MVP - Windows Server Directory Services
> Microsoft Certified Trainer
> Assimilation Imminent. Resistance is Futile.
> Infinite Diversities in Infinite Combinations.
>
> The only thing in life is change. Anything less is a blackhole consuming
> unnecessary energy.
> ===========================
>
>
>
Author
10 Feb 2006 4:51 AM
Ace Fekay [MVP]
In news:2142F073-AE89-4B8C-A54B-9ADC5D80E4BA@microsoft.com,
crfroehlich <crfroehl***@discussions.microsoft.com> stated, which I
commented on below:
> Oddly enough, we had a power failure this morning; when the server
> came back up, the pdc issue seemed to have resolved itself.  Perhaps
> the server simply needed to be rebooted?

Sometimes a good kick will work wonders.

:-)

Ace