PDC_REQUIRED

[Guest]

hi,
yesterday the DC with the PDC roles is dead.
I've seized the roles on another DC and I can see (from Active Directory
Users & Computer/FSMO roles) the new owner of the PDC role.
But I have some problem accesing resources and including machines to the
domain. After some
checks I've some problems with the PDC role. DCDIAG report an error :
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.

The FRS and the SYSVOL looks right, also i checked the DNS configuration and
all looks right.

Any help?

 

[Herb Martin]

hi,
yesterday the DC with the PDC roles is dead.
I've seized the roles on another DC and I can see (from Active Directory
Users & Computer/FSMO roles) the new owner of the PDC role.
But I have some problem accesing resources and including machines to the
domain. After some
checks I've some problems with the PDC role. DCDIAG report an error :
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.

The FRS and the SYSVOL looks right, also i checked the DNS configuration
and
all looks right.

Any help?

Chances are it's a DNS issue. Is the new PDC-emul set to use
STRICTLY the internal DYNAMIC DNS and have you run the
DCDIAG ON the PDC emulator itself?

DCDiag should be run on ALL DCs (individually or together although
personally I prefer doing each separately.)

You might also try DCDiag /fix (after you capture the INITIAL results
to a text file for comparison afterwards.)

Also note, you cannot (now) bring back the "old PDC-emul" except
to (quickly) DCPromo it to non-DC.

 

[Guest]

Hi Herb,

There is only one DC on the AD, Im pretty sure that they are using this one
like the prefered DNS, I configured the DHCP to do it, also I have checked
the same configuration in TCP/IP. I already remove the AD data of the lost
DC, and there is not way to bring it back, I Can't join new computers to the
domain, I can't bring back the old DC.

Thx

hi,
yesterday the DC with the PDC roles is dead.
I've seized the roles on another DC and I can see (from Active Directory
Users & Computer/FSMO roles) the new owner of the PDC role.
But I have some problem accesing resources and including machines to the
domain. After some
checks I've some problems with the PDC role. DCDIAG report an error :
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.

The FRS and the SYSVOL looks right, also i checked the DNS configuration
and
all looks right.

Any help?

Chances are it's a DNS issue. Is the new PDC-emul set to use
STRICTLY the internal DYNAMIC DNS and have you run the
DCDIAG ON the PDC emulator itself?

DCDiag should be run on ALL DCs (individually or together although
personally I prefer doing each separately.)

You might also try DCDiag /fix (after you capture the INITIAL results
to a text file for comparison afterwards.)

Also note, you cannot (now) bring back the "old PDC-emul" except
to (quickly) DCPromo it to non-DC.


--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

 

[Herb Martin]

Hi Herb,

There is only one DC on the AD, Im pretty sure that they are using this
one
like the prefered DNS, I configured the DHCP to do it, also I have checked
the same configuration in TCP/IP.

The DC must also be a DNS client (of itself it it is) the DNS server.

It is unlikely you are using DHCP to set the DCs IP (technically legal
but discouraged.)

I already remove the AD data of the lost
DC, and there is not way to bring it back, I Can't join new computers to
the
domain, I can't bring back the old DC.

Are you saying you only have ONE DC and it has failed?

If that is the case you wasted your time (and mine) by discussing
the loss of the PDC emulator without mentioning it was the ONLY
DC.

IF you have no DCs from this domain and you have no backups you
have lost the domain permanently.

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

Thx

hi,
yesterday the DC with the PDC roles is dead.
I've seized the roles on another DC and I can see (from Active
Directory
Users & Computer/FSMO roles) the new owner of the PDC role.
But I have some problem accesing resources and including machines to
the
domain. After some
checks I've some problems with the PDC role. DCDIAG report an error :
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.

The FRS and the SYSVOL looks right, also i checked the DNS
configuration
and
all looks right.

Any help?

Chances are it's a DNS issue. Is the new PDC-emul set to use
STRICTLY the internal DYNAMIC DNS and have you run the
DCDIAG ON the PDC emulator itself?

DCDiag should be run on ALL DCs (individually or together although
personally I prefer doing each separately.)

You might also try DCDiag /fix (after you capture the INITIAL results
to a text file for comparison afterwards.)

Also note, you cannot (now) bring back the "old PDC-emul" except
to (quickly) DCPromo it to non-DC.


--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

 

[Jorge de Almeida Pinto]

Hi,
After reading this I see a lot of confusion.
From my understanding the DC with the PDC FSMO role died and you
seize the PDC FSMO role to another DC. More information must be
available as this is not enough to help.
Walter, can you share more information on what happened, what you
have done and what the situations/was?
Please provide more info about:
* How many DC did you have or do you have?
* Which DCs host any FSMO roles?
* What are event IDs or any error messages you receive/see?
* The DC that died... this it host any other FSMO roles?

Cheers,
# Jorge de Almeida Pinto #