Dear Experts; we have a DC running Win Server 2008 Standard X32, and we installed new Win Server 2008 R2 Enterprise X64 for redunduncy & Replication, when we want to promote the second server to a DC it give us error: shows that we have to prepare the AD for the new DC, and we already did that, but it was useless, every time we want to promote the DC it gives the same Error. i don't know what to do really. i have run Dcdiag.exe and have the following output: C:>dcdiag.exe /s:pm-vsp-dc03 Directory Server Diagnosis Performing initial setup:    * Identified AD Forest.    [PM-S-DC01] LDAP bind failed with error 8341,    A directory service error has occurred..    Got error while checking if the DC is using FRS or DFSR. Error:    A directory service error has occurred.The VerifyReferences, FrsEvent and    DfsrEvent tests might fail because of this error.    Done gathering initial info. Doing initial required tests    Testing server: Shah-AlamPM-VSP-DC03       Starting test: Connectivity          ......................... PM-VSP-DC03 passed test Connectivity Doing primary tests    Testing server: Shah-AlamPM-VSP-DC03       Starting test: Advertising          Warning: PM-VSP-DC03 is not advertising as a time server.          ......................... PM-VSP-DC03 failed test Advertising       Starting test: FrsEvent          The event log File Replication Service on server          pm-vsp-dc03.mediu.edu.my could not be queried, error 0x6ba          "The RPC server is unavailable."          ......................... PM-VSP-DC03 failed test FrsEvent       Starting test: DFSREvent          ......................... PM-VSP-DC03 passed test DFSREvent       Starting test: SysVolCheck          ......................... PM-VSP-DC03 passed test SysVolCheck       Starting test: KccEvent          The event log Directory Service on server pm-vsp-dc03.mediu.edu.my          could not be queried, error 0x6ba "The RPC server is unavailable."          ......................... PM-VSP-DC03 failed test KccEvent       Starting test: KnowsOfRoleHolders          [PM-S-DC01] DsBindWithSpnEx() failed with error -2146893022,          The target principal name is incorrect..          Warning: PM-S-DC01 is the Schema Owner, but is not responding to DS          RPC Bind.          Warning: PM-S-DC01 is the Schema Owner, but is not responding to LDAP          Bind.          Warning: PM-S-DC01 is the PDC Owner, but is not responding to DS RPC          Bind.          Warning: PM-S-DC01 is the PDC Owner, but is not responding to LDAP          Bind.          Warning: PM-S-DC01 is the Rid Owner, but is not responding to DS RPC          Bind.          Warning: PM-S-DC01 is the Rid Owner, but is not responding to LDAP          Bind.          Warning: PM-S-DC01 is the Infrastructure Update Owner, but is not          responding to DS RPC Bind.          Warning: PM-S-DC01 is the Infrastructure Update Owner, but is not          responding to LDAP Bind.          ......................... PM-VSP-DC03 failed test KnowsOfRoleHolders       Starting test: MachineAccount          ......................... PM-VSP-DC03 passed test MachineAccount       Starting test: NCSecDesc          Error NT AUTHORITYENTERPRISE DOMAIN CONTROLLERS doesn't have             Replicating Directory Changes In Filtered Set          access rights for the naming context:          DC=ForestDnsZones,DC=mediu,DC=edu,DC=my          Error NT AUTHORITYENTERPRISE DOMAIN CONTROLLERS doesn't have             Replicating Directory Changes In Filtered Set          access rights for the naming context:          DC=DomainDnsZones,DC=mediu,DC=edu,DC=my          ......................... PM-VSP-DC03 failed test NCSecDesc       Starting test: NetLogons          ......................... PM-VSP-DC03 passed test NetLogons       Starting test: ObjectsReplicated          ......................... PM-VSP-DC03 passed test ObjectsReplicated       Starting test: Replications          [Replications Check,PM-VSP-DC03] A recent replication attempt failed:             From PM-S-DC01 to PM-VSP-DC03             Naming Context: DC=ForestDnsZones,DC=mediu,DC=edu,DC=my             The replication generated an error (1256):             The remote system is not available. For information about network tr oubleshooting, see Windows Help.             The failure occurred at 2011-01-26 18:59:04.             The last success occurred at 2010-11-16 21:52:42.             1702 failures have occurred since the last success.          [Replications Check,PM-VSP-DC03] A recent replication attempt failed:             From PM-S-DC01 to PM-VSP-DC03             Naming Context: DC=DomainDnsZones,DC=mediu,DC=edu,DC=my             The replication generated an error (1256):             The remote system is not available. For information about network tr oubleshooting, see Windows Help.             The failure occurred at 2011-01-26 18:59:04.             The last success occurred at 2010-11-16 21:52:42.             1702 failures have occurred since the last success.          [Replications Check,PM-VSP-DC03] A recent replication attempt failed:             From PM-S-DC01 to PM-VSP-DC03             Naming Context: CN=Schema,CN=Configuration,DC=mediu,DC=edu,DC=my             The replication generated an error (-2146893022):             The target principal name is incorrect.             The failure occurred at 2011-01-26 18:59:04.             The last success occurred at 2010-11-16 21:52:42.             1702 failures have occurred since the last success.          [Replications Check,PM-VSP-DC03] A recent replication attempt failed:             From PM-S-DC01 to PM-VSP-DC03             Naming Context: CN=Configuration,DC=mediu,DC=edu,DC=my             The replication generated an error (-2146893022):             The target principal name is incorrect.             The failure occurred at 2011-01-26 18:59:04.             The last success occurred at 2010-11-16 21:53:07.             1702 failures have occurred since the last success.          [Replications Check,PM-VSP-DC03] A recent replication attempt failed:             From PM-S-DC01 to PM-VSP-DC03             Naming Context: DC=mediu,DC=edu,DC=my             The replication generated an error (-2146893022):             The target principal name is incorrect.             The failure occurred at 2011-01-26 18:59:04.             The last success occurred at 2010-11-16 21:52:42.             1702 failures have occurred since the last success.          ......................... PM-VSP-DC03 failed test Replications       Starting test: RidManager          ......................... PM-VSP-DC03 failed test RidManager       Starting test: Services          ......................... PM-VSP-DC03 passed test Services       Starting test: SystemLog          The event log System on server pm-vsp-dc03.mediu.edu.my could not be          queried, error 0x6ba "The RPC server is unavailable."          ......................... PM-VSP-DC03 failed test SystemLog       Starting test: VerifyReferences          ......................... PM-VSP-DC03 passed test VerifyReferences    Running partition tests on : ForestDnsZones       Starting test: CheckSDRefDom          ......................... ForestDnsZones passed test CheckSDRefDom       Starting test: CrossRefValidation          ......................... ForestDnsZones passed test          CrossRefValidation    Running partition tests on : DomainDnsZones       Starting test: CheckSDRefDom          ......................... DomainDnsZones passed test CheckSDRefDom       Starting test: CrossRefValidation          ......................... DomainDnsZones passed test          CrossRefValidation    Running partition tests on : Schema       Starting test: CheckSDRefDom          ......................... Schema passed test CheckSDRefDom       Starting test: CrossRefValidation          ......................... Schema passed test CrossRefValidation    Running partition tests on : Configuration       Starting test: CheckSDRefDom          ......................... Configuration passed test CheckSDRefDom       Starting test: CrossRefValidation          ......................... Configuration passed test CrossRefValidation    Running partition tests on : mediu       Starting test: CheckSDRefDom          ......................... mediu passed test CheckSDRefDom       Starting test: CrossRefValidation          ......................... mediu passed test CrossRefValidation    Running enterprise tests on : mediu.edu.my       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.          Warning: DcGetDcName(TIME_SERVER) call failed, error 1355          A Time Server could not be located.          The server holding the PDC role is down.          Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error          1355          A Good Time Server could not be located.          ......................... mediu.edu.my failed test LocatorCheck       Starting test: Intersite          ......................... mediu.edu.my passed test Intersite really appreciate the help in advance :)

Software/Hardware used:
,