we get the following from dcdiagC:\>dcdiag /a Domain Controller Diagnosis Performing initial setup: Done gathering initial info. Doing initial required tests Testing server: Default-First-Site-Name\FILESERVER Starting test: Connectivity The host 958ca3d9-7cb6-4637-89d2-2831d56edd61._msdcs.berkshire.loc could not be resolved to an IP address. Check the DNS server, DHCP, server name, etc Although the Guid DNS name (958ca3d9-7cb6-4637-89d2-2831d56edd61._msdcs.berkshire.loc) couldn't be resolved, the server name (fileserver.berkshire.loc) resolved to the IP address (192.168.0.100) and was pingable. Check that the IP address is registered correctly with the DNS server. ......................... FILESERVER failed test Connectivity Testing server: Default-First-Site-Name\BFUFSD Starting test: Connectivity ......................... BFUFSD passed test Connectivity Testing server: Default-First-Site-Name\BFCPDC01 Starting test: Connectivity ......................... BFCPDC01 passed test Connectivity Testing server: Default-First-Site-Name\BFUFSDDHCP1 Starting test: Connectivity ......................... BFUFSDDHCP1 passed test Connectivity Doing primary tests Testing server: Default-First-Site-Name\FILESERVER Skipping all tests, because server FILESERVER is not responding to directory service requests Testing server: Default-First-Site-Name\BFUFSD Starting test: Replications ......................... BFUFSD passed test Replications Starting test: NCSecDesc ......................... BFUFSD passed test NCSecDesc Starting test: NetLogons ......................... BFUFSD passed test NetLogons Starting test: Advertising Warning: BFUFSD is not advertising as a time server. ......................... BFUFSD failed test Advertising Starting test: KnowsOfRoleHolders [FILESERVER] DsBindWithSpnEx() failed with error 1722, The RPC server is unavailable.. Warning: FILESERVER is the Schema Owner, but is not responding to DS RPC Bind. [FILESERVER] LDAP search failed with error 58, The specified server cannot perform the requested operation.. Warning: FILESERVER is the Schema Owner, but is not responding to LDAP Bind. Warning: FILESERVER is the Domain Owner, but is not responding to DS RPC Bind. Warning: FILESERVER is the Domain Owner, but is not responding to LDAP Bind. Warning: FILESERVER is the PDC Owner, but is not responding to DS RPC Bind. Warning: FILESERVER is the PDC Owner, but is not responding to LDAP Bind. Warning: FILESERVER is the Rid Owner, but is not responding to DS RPC Bind. Warning: FILESERVER is the Rid Owner, but is not responding to LDAP Bind. Warning: FILESERVER is the Infrastructure Update Owner, but is not responding to DS RPC Bind. Warning: FILESERVER is the Infrastructure Update Owner, but is not responding to LDAP Bind. ......................... BFUFSD failed test KnowsOfRoleHolders Starting test: RidManager ......................... BFUFSD failed test RidManager Starting test: MachineAccount ......................... BFUFSD passed test MachineAccount Starting test: Services ......................... BFUFSD passed test Services Starting test: ObjectsReplicated ......................... BFUFSD passed test ObjectsReplicated Starting test: frssysvol ......................... BFUFSD passed test frssysvol Starting test: frsevent There are warning or error events within the last 24 hours after the SYSVOL has been shared. Failing SYSVOL replication problems may cause Group Policy problems. ......................... BFUFSD failed test frsevent Starting test: kccevent ......................... BFUFSD passed test kccevent Starting test: systemlog ......................... BFUFSD passed test systemlog Starting test: VerifyReferences ......................... BFUFSD passed test VerifyReferences Testing server: Default-First-Site-Name\BFCPDC01 Starting test: Replications ......................... BFCPDC01 passed test Replications Starting test: NCSecDesc ......................... BFCPDC01 passed test NCSecDesc Starting test: NetLogons ......................... BFCPDC01 passed test NetLogons Starting test: Advertising ......................... BFCPDC01 passed test Advertising Starting test: KnowsOfRoleHolders Warning: FILESERVER is the Schema Owner, but is not responding to DS RPC Bind. Warning: FILESERVER is the Schema Owner, but is not responding to LDAP Bind. Warning: FILESERVER is the Domain Owner, but is not responding to DS RPC Bind. Warning: FILESERVER is the Domain Owner, but is not responding to LDAP Bind. Warning: FILESERVER is the PDC Owner, but is not responding to DS RPC Bind. Warning: FILESERVER is the PDC Owner, but is not responding to LDAP Bind. Warning: FILESERVER is the Rid Owner, but is not responding to DS RPC Bind. Warning: FILESERVER is the Rid Owner, but is not responding to LDAP Bind. Warning: FILESERVER is the Infrastructure Update Owner, but is not responding to DS RPC Bind. Warning: FILESERVER is the Infrastructure Update Owner, but is not responding to LDAP Bind. ......................... BFCPDC01 failed test KnowsOfRoleHolders Starting test: RidManager ......................... BFCPDC01 failed test RidManager Starting test: MachineAccount ......................... BFCPDC01 passed test MachineAccount Starting test: Services ......................... BFCPDC01 passed test Services Starting test: ObjectsReplicated ......................... BFCPDC01 passed test ObjectsReplicated Starting test: frssysvol ......................... BFCPDC01 passed test frssysvol Starting test: frsevent There are warning or error events within the last 24 hours after the SYSVOL has been shared. Failing SYSVOL replication problems may cause Group Policy problems. ......................... BFCPDC01 failed test frsevent Starting test: kccevent ......................... BFCPDC01 passed test kccevent Starting test: systemlog ......................... BFCPDC01 passed test systemlog Starting test: VerifyReferences ......................... BFCPDC01 passed test VerifyReferences Testing server: Default-First-Site-Name\BFUFSDDHCP1 Starting test: Replications ......................... BFUFSDDHCP1 passed test Replications Starting test: NCSecDesc ......................... BFUFSDDHCP1 passed test NCSecDesc Starting test: NetLogons ......................... BFUFSDDHCP1 passed test NetLogons Starting test: Advertising ......................... BFUFSDDHCP1 passed test Advertising Starting test: KnowsOfRoleHolders Warning: FILESERVER is the Schema Owner, but is not responding to DS RPC Bind. Warning: FILESERVER is the Schema Owner, but is not responding to LDAP Bind. Warning: FILESERVER is the Domain Owner, but is not responding to DS RPC Bind. Warning: FILESERVER is the Domain Owner, but is not responding to LDAP Bind. Warning: FILESERVER is the PDC Owner, but is not responding to DS RPC Bind. Warning: FILESERVER is the PDC Owner, but is not responding to LDAP Bind. Warning: FILESERVER is the Rid Owner, but is not responding to DS RPC Bind. Warning: FILESERVER is the Rid Owner, but is not responding to LDAP Bind. Warning: FILESERVER is the Infrastructure Update Owner, but is not responding to DS RPC Bind. Warning: FILESERVER is the Infrastructure Update Owner, but is not responding to LDAP Bind. ......................... BFUFSDDHCP1 failed test KnowsOfRoleHolders Starting test: RidManager ......................... BFUFSDDHCP1 failed test RidManager Starting test: MachineAccount ......................... BFUFSDDHCP1 passed test MachineAccount Starting test: Services ......................... BFUFSDDHCP1 passed test Services Starting test: ObjectsReplicated ......................... BFUFSDDHCP1 passed test ObjectsReplicated Starting test: frssysvol ......................... BFUFSDDHCP1 passed test frssysvol Starting test: frsevent There are warning or error events within the last 24 hours after the SYSVOL has been shared. Failing SYSVOL replication problems may cause Group Policy problems. ......................... BFUFSDDHCP1 failed test frsevent Starting test: kccevent ......................... BFUFSDDHCP1 passed test kccevent Starting test: systemlog ......................... BFUFSDDHCP1 passed test systemlog Starting test: VerifyReferences ......................... BFUFSDDHCP1 passed test VerifyReferences Running partition tests on : ForestDnsZones Starting test: CrossRefValidation For the partition (DC=ForestDnsZones,DC=berkshire,DC=loc) we encountered the following error retrieving the cross-ref's (CN=0349caa2-4107-4f5c-b7b3-337e53c9fb66,CN=Partitions,CN=Configuration,DC=berkshire,DC=loc) information: LDAP Error 0x0 (0). ......................... ForestDnsZones failed test CrossRefValidation Starting test: CheckSDRefDom For the partition (DC=ForestDnsZones,DC=berkshire,DC=loc) we encountered the following error retrieving the cross-ref's (CN=0349caa2-4107-4f5c-b7b3-337e53c9fb66,CN=Partitions,CN=Configuration,DC=berkshire,DC=loc) information: LDAP Error 0x0 (0). ......................... ForestDnsZones failed test CheckSDRefDom Running partition tests on : DomainDnsZones Starting test: CrossRefValidation For the partition (DC=DomainDnsZones,DC=berkshire,DC=loc) we encountered the following error retrieving the cross-ref's (CN=54ce9f09-8b52-4fc5-96b0-e161c59ba224,CN=Partitions,CN=Configuration,DC=berkshire,DC=loc) information: LDAP Error 0x0 (0). ......................... DomainDnsZones failed test CrossRefValidation Starting test: CheckSDRefDom For the partition (DC=DomainDnsZones,DC=berkshire,DC=loc) we encountered the following error retrieving the cross-ref's (CN=54ce9f09-8b52-4fc5-96b0-e161c59ba224,CN=Partitions,CN=Configuration,DC=berkshire,DC=loc) information: LDAP Error 0x0 (0). ......................... DomainDnsZones failed test CheckSDRefDom Running partition tests on : Schema Starting test: CrossRefValidation For the partition (CN=Schema,CN=Configuration,DC=berkshire,DC=loc) we encountered the following error retrieving the cross-ref's (CN=Enterprise Schema,CN=Partitions,CN=Configuration,DC=berkshire,DC=loc) information: LDAP Error 0x0 (0). ......................... Schema failed test CrossRefValidation Starting test: CheckSDRefDom ......................... Schema passed test CheckSDRefDom Running partition tests on : Configuration Starting test: CrossRefValidation For the partition (CN=Configuration,DC=berkshire,DC=loc) we encountered the following error retrieving the cross-ref's (CN=Enterprise Configuration,CN=Partitions,CN=Configuration,DC=berkshire,DC=loc) information: LDAP Error 0x0 (0). ......................... Configuration failed test CrossRefValidation Starting test: CheckSDRefDom ......................... Configuration passed test CheckSDRefDom Running partition tests on : berkshire Starting test: CrossRefValidation For the partition (DC=berkshire,DC=loc) we encountered the following error retrieving the cross-ref's (CN=BERKSHIRE,CN=Partitions,CN=Configuration,DC=berkshire,DC=loc) information: LDAP Error 0x0 (0). ......................... berkshire failed test CrossRefValidation Starting test: CheckSDRefDom ......................... berkshire passed test CheckSDRefDom Running enterprise tests on : berkshire.loc Starting test: Intersite ......................... berkshire.loc passed test Intersite 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. ......................... berkshire.loc failed test FsmoCheck

Hi Is there any stale domain controls in domain. If there Please do the metadata cleanup...Here you go..http://support.microsoft.com/kb/216498http://www.petri.co.il/delete_failed_dcs_from_ad.htmAnd please try the below linkhttp://support.microsoft.com/kb/839880please let us know the updates...Regards Rajesh J S

We don't have any stale domain controllers but have had issues in the past with this one. We have 3 others one being the primary all running windows 2003. I would like to just remove the funtion off this server. we have 2 in one computer center to handle campus and remote sites and 2 in the school. we had a problem today were the 2 for campus(one being the primary) were shut down due to ac issues in our sererve room. The school should have functioned fine since they have the other dc's and there own exchange server. problem was school could not get into there exchange server until the capmus servers came back up

Hi, Thanks for your post. The output of the dcdiag indicates that the Guid DNS name (958ca3d9-7cb6-4637-89d2-2831d56edd61._msdcs.berkshire.loc) is not registered correctly. If you want to demote the domain controller FILESERVER, you can refer to the following article: Demote a domain controller http://technet.microsoft.com/en-us/library/cc740017(WS.10).aspx As for the Exchange issue, please ensure that there is one GC in school. In addition, it would be helpful if you can provide more information such as the exact error message, etc about the issue. I look forward to your response. Joson Zhou TechNet Subscriber Support in forumThis posting is provided "AS IS" with no warranties, and confers no rights.

Hi, How’s everything going? I have not heard back from you in a few days and wanted to check on the status of the issue. If you need further assistance, please feel free to respond back. Thanks. Joson Zhou TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb @ microsoft.comThis posting is provided "AS IS" with no warranties, and confers no rights.

I removed active directory from the server and so far everything has been fine. I won't know for sure until we test severing the link between the school and campus

Hi, Thanks for your update. If the issue occurs again, please do not hesitate to let me know. Joson Zhou TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb @ microsoft.comThis posting is provided "AS IS" with no warranties, and confers no rights.