Advertisement
I have a domain with 2 DCs (PTI-DC, AND PTI-FILE) running 2012r2 to which I have added a new 2022 dc (PTI-PDC) intended to be the PDC.<\/p>\n
DCDIAG reports the following:
\nTesting server: Default-First-Site-Name\\PTI-DC
\nStarting test: Advertising
\nThe DC PTI-DC is advertising itself as a DC and having a DS.
\nThe DC PTI-DC is advertising as an LDAP server
\nThe DC PTI-DC is advertising as having a writeable directory
\nThe DC PTI-DC is advertising as a Key Distribution Center
\nThe DC PTI-DC is advertising as a time server
\nThe DS PTI-DC is advertising as a GC.
\n… PTI-DC passed test Advertising<\/p>\n
Testing server: Default-First-Site-Name\\PTI-PDC
\nStarting test: Advertising
\nWarning: DsGetDcName returned information for \\PTI-DC.PTI.local, when we were trying to reach PTI-PDC.
\nSERVER IS NOT RESPONDING or IS NOT CONSIDERED SUITABLE.
\n… PTI-PDC failed test Advertising<\/p>\n
Starting test: NetLogons
\n* Network Logons Privileges Check
\nUnable to connect to the NETLOGON share! (\\PTI-PDC\\netlogon)
\n[PTI-PDC] An net use or LsaPolicy operation failed with error 67, The network name cannot be found…
\n… PTI-PDC failed test NetLogons<\/p>\n
Testing server: Default-First-Site-Name\\PTI-FILE
\nStarting test: Advertising
\nWarning: DsGetDcName returned information for \\PTI-DC.PTI.local, when we were trying to reach PTI-FILE.
\nSERVER IS NOT RESPONDING or IS NOT CONSIDERED SUITABLE.
\n… PTI-FILE failed test Advertising<\/p>\n
Starting test: NetLogons
\n* Network Logons Privileges Check
\nUnable to connect to the NETLOGON share! (\\PTI-FILE\\netlogon)
\n[PTI-FILE] An net use or LsaPolicy operation failed with error 67, The network name cannot be found…
\n… PTI-FILE failed test NetLogons<\/p>\n
DCDIAG reports the following for all DNS servers:<\/p>\n
Summary of DNS test results:<\/p>\n
Auth Basc Forw Del Dyn RReg Ext\n _________________________________________________________________\n Domain: PTI.local\n PTI-DC PASS PASS PASS PASS WARN PASS PASS\n PTI-FILE PASS PASS PASS PASS WARN PASS PASS\n PTI-PDC PASS PASS PASS PASS WARN PASS PASS\n\n ......................... PTI.local passed test DNS\n Test omitted by user request: LocatorCheck\n Test omitted by user request: Intersite\n<\/code><\/pre>\nMy goal is to have PTI-PDC as the domain controller, and possible keep the PTI-DC as a backup dc and replacing the file server with a 3 node cluster Dell F200s<\/p>\n
Please help<\/p>","upvoteCount":3,"answerCount":28,"datePublished":"2024-11-25T21:17:47.966Z","author":{"@type":"Person","name":"spiceuser-4real","url":"https://community.spiceworks.com/u/spiceuser-4real"},"suggestedAnswer":[{"@type":"Answer","text":"
I have a domain with 2 DCs (PTI-DC, AND PTI-FILE) running 2012r2 to which I have added a new 2022 dc (PTI-PDC) intended to be the PDC.<\/p>\n
DCDIAG reports the following:
\nTesting server: Default-First-Site-Name\\PTI-DC
\nStarting test: Advertising
\nThe DC PTI-DC is advertising itself as a DC and having a DS.
\nThe DC PTI-DC is advertising as an LDAP server
\nThe DC PTI-DC is advertising as having a writeable directory
\nThe DC PTI-DC is advertising as a Key Distribution Center
\nThe DC PTI-DC is advertising as a time server
\nThe DS PTI-DC is advertising as a GC.
\n… PTI-DC passed test Advertising<\/p>\n
Testing server: Default-First-Site-Name\\PTI-PDC
\nStarting test: Advertising
\nWarning: DsGetDcName returned information for \\PTI-DC.PTI.local, when we were trying to reach PTI-PDC.
\nSERVER IS NOT RESPONDING or IS NOT CONSIDERED SUITABLE.
\n… PTI-PDC failed test Advertising<\/p>\n
Starting test: NetLogons
\n* Network Logons Privileges Check
\nUnable to connect to the NETLOGON share! (\\PTI-PDC\\netlogon)
\n[PTI-PDC] An net use or LsaPolicy operation failed with error 67, The network name cannot be found…
\n… PTI-PDC failed test NetLogons<\/p>\n
Testing server: Default-First-Site-Name\\PTI-FILE
\nStarting test: Advertising
\nWarning: DsGetDcName returned information for \\PTI-DC.PTI.local, when we were trying to reach PTI-FILE.
\nSERVER IS NOT RESPONDING or IS NOT CONSIDERED SUITABLE.
\n… PTI-FILE failed test Advertising<\/p>\n
Starting test: NetLogons
\n* Network Logons Privileges Check
\nUnable to connect to the NETLOGON share! (\\PTI-FILE\\netlogon)
\n[PTI-FILE] An net use or LsaPolicy operation failed with error 67, The network name cannot be found…
\n… PTI-FILE failed test NetLogons<\/p>\n
DCDIAG reports the following for all DNS servers:<\/p>\n
Summary of DNS test results:<\/p>\n
Auth Basc Forw Del Dyn RReg Ext\n _________________________________________________________________\n Domain: PTI.local\n PTI-DC PASS PASS PASS PASS WARN PASS PASS\n PTI-FILE PASS PASS PASS PASS WARN PASS PASS\n PTI-PDC PASS PASS PASS PASS WARN PASS PASS\n\n ......................... PTI.local passed test DNS\n Test omitted by user request: LocatorCheck\n Test omitted by user request: Intersite\n<\/code><\/pre>\nMy goal is to have PTI-PDC as the domain controller, and possible keep the PTI-DC as a backup dc and replacing the file server with a 3 node cluster Dell F200s<\/p>\n
Please help<\/p>","upvoteCount":3,"datePublished":"2024-11-25T21:17:48.022Z","url":"https://community.spiceworks.com/t/server-dcdiag-advertising-and-netlogons-error/1146336/1","author":{"@type":"Person","name":"spiceuser-4real","url":"https://community.spiceworks.com/u/spiceuser-4real"}},{"@type":"Answer","text":"
Couple of things to look at. There’s no such thing as a PDC/BDC anymore, hasn’t been since NT 4.0. All DCs are equal now. The only small difference is one will have the PDC Emulator FSMO role. (This can be moved between DCs at any time). Which ever one holds the PDCe role needs to be set as the authoritative time source for the domain.<\/p>\n
What is the domain and forest functionality level? (DFL and FFL) If your lowest DC is 2012R2 then you can set both of these to 2012R2.<\/p>\n
Check your DNS config on your servers, this is the biggest source of issues. See the following topic on that.<\/p>\n