N
Nichovath
Hi All,
We have a Domain with 3 DCs. Two are running Windows Server 2012 R2, and one is running Windows Server 2012.
Our Domain/Forest functional levels were at 2003, so on the PDC I've bumped it to 2008 R2. Now when I check for replication on the other two DCs through AD Domains & Trusts, the following error occurs:
This occurs on the two DCs (non-PDC) through DCDIAG:
Running enterprise tests on : domain.local
Starting test: LocatorCheck
Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1355
A Primary Domain Controller could not be located.
The server holding the PDC role is down.
.........................domain.local failed test LocatorCheck
Starting test: Intersite
.........................domain.local passed test Intersite
The PDC is in fact up and running. Running a DCDIAG on it yields all successful.
Other tests
Yet still, a DCDIAG results in the above error, and the domain functional level raise is not replicating.
I can't confirm if this was caused by the domain functional level raise.
Another admin here was however attempting to add a BIND(Linux) DNS as an NS record through the DNS entries. I went through and deleted all of those where applicable for now to try and get it working; still nothing.
Thanks in advance...
Continue reading...
We have a Domain with 3 DCs. Two are running Windows Server 2012 R2, and one is running Windows Server 2012.
Our Domain/Forest functional levels were at 2003, so on the PDC I've bumped it to 2008 R2. Now when I check for replication on the other two DCs through AD Domains & Trusts, the following error occurs:
This occurs on the two DCs (non-PDC) through DCDIAG:
Running enterprise tests on : domain.local
Starting test: LocatorCheck
Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1355
A Primary Domain Controller could not be located.
The server holding the PDC role is down.
.........................domain.local failed test LocatorCheck
Starting test: Intersite
.........................domain.local passed test Intersite
The PDC is in fact up and running. Running a DCDIAG on it yields all successful.
Other tests
- 'Netdom query FSMO' on impacted DCs - shows correct PDC.
- Ping is fine via name or IP
- DCs are all pointing to eachother on DNS primary and loopback secondary. (NIC setup)
- In DNS under Foward Lookup Zones --> _msdcs.domain.local --> PDC --> _tcp --> I see the _ldap listing for the correct PDC.
- Repadmin /syncall - no errors
- Restarted netlogon service on PDC.
- 'dsquery server -hasfsmo pdc' on impacted DCs yields the correct PDC FQDN...
Yet still, a DCDIAG results in the above error, and the domain functional level raise is not replicating.
I can't confirm if this was caused by the domain functional level raise.
Another admin here was however attempting to add a BIND(Linux) DNS as an NS record through the DNS entries. I went through and deleted all of those where applicable for now to try and get it working; still nothing.
Thanks in advance...
Continue reading...