@premglitz:Tried that, no love.@metsp:Checked (i.e. I moved all my FSMO roles to DC2-5099 and specified that DC during DCPROMO, but still no luck.@blakmoon91, here is my dcdiag results from DC2-5099. It seems I have found an error:Directory Server Diagnosis Performing initial setup: Trying to find home server. Home Server = DC2-5099. Identified AD Forest. Done gathering initial info.

1. Net Is Not Recognized As An Internal Or External Command Windows 10
2. Unzip Is Not Recognized As An Internal Or External Command Operable Program Or Batch File

Doing initial required tests Testing server: Default-First-Site-NameDC2-5099 Starting test: Connectivity. DC2-5099 passed test Connectivity Doing primary tests Testing server: Default-First-Site-NameDC2-5099 Starting test: Advertising. DC2-5099 passed test Advertising 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. DC2-5099 passed test FrsEvent Starting test: DFSREvent. DC2-5099 passed test DFSREvent Starting test: SysVolCheck. DC2-5099 passed test SysVolCheck Starting test: KccEvent.

DC2-5099 passed test KccEvent Starting test: KnowsOfRoleHolders. DC2-5099 passed test KnowsOfRoleHolders Starting test: MachineAccount. DC2-5099 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=network,DC=local Error NT AUTHORITYENTERPRISE DOMAIN CONTROLLERS doesn't have Replicating Directory Changes In Filtered Set access rights for the naming context: DC=DomainDnsZones,DC=network,DC=local. DC2-5099 failed test NCSecDesc Starting test: NetLogons. DC2-5099 passed test NetLogons Starting test: ObjectsReplicated.

DC2-5099 passed test ObjectsReplicated Starting test: Replications. DC2-5099 passed test Replications Starting test: RidManager. DC2-5099 passed test RidManager Starting test: Services. DC2-5099 passed test Services Starting test: SystemLog A warning event occurred. EventID: 0x0000000C Time Generated: 09:28:13 Event String: Time Provider NtpClient: This machine is configured to use the domain hierarchy to determine its time source, but it is the AD PDC emulator for the domain at the root of the forest, so there is no machine above it in the domain hierarchy to use as a time source.

It is recommended that you either configure a reliable time service in the root domain, or manually configure the AD PDC to synchronize with an external time source. Otherwise, this machine will function as the authoritative time source in the domain hierarchy. If an external time source is not configured or used for this computer, you may choose to disable the NtpClient. DC2-5099 passed test SystemLog Starting test: VerifyReferences.

DC2-5099 passed test VerifyReferences Running partition tests on: ForestDnsZones Starting test: CheckSDRefDom. Sims 4 cc eyes replacement. 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: network Starting test: CheckSDRefDom. Network passed test CheckSDRefDom Starting test: CrossRefValidation. Network passed test CrossRefValidation Running enterprise tests on: network.local Starting test: LocatorCheck. Network.local passed test LocatorCheck Starting test: Intersite. Network.local passed test IntersiteSelect all. @Awinish:Sorry for the late reply. I ran port query between 2 DC's that were replicating (DC2 and DC3) and then between 2 DC's that weren't (DC2 and DC5).I will post the output to the other commands shortly.

Here are the results for PortQry:DC2 to DC5: portqry.exe -n 192.168.10.11 -e 135 -p TCP exits with return code 0x00000000. Portqry.exe -n 192.168.10.11 -e 137 -p UDP exits with return code 0x00000000. Portqry.exe -n 192.168.10.11 -e 138 -p UDP exits with return code 0x00000002. Portqry.exe -n 192.168.10.11 -e 139 -p TCP exits with return code 0x00000000. Portqry.exe -n 192.168.10.11 -e 3268 -p TCP exits with return code 0x00000002. Portqry.exe -n 192.168.10.11 -e 3269 -p TCP exits with return code 0x00000002. Portqry.exe -n 192.168.10.11 -e 389 -p BOTH exits with return code 0x00000001.

Net Is Not Recognized As An Internal Or External Command Windows 10

Portqry.exe -n 192.168.10.11 -e 42 -p TCP exits with return code 0x00000002. Portqry.exe -n 192.168.10.11 -e 445 -p TCP exits with return code 0x00000000. Portqry.exe -n 192.168.10.11 -e 53 -p BOTH exits with return code 0x00000000.

Portqry.exe -n 192.168.10.11 -e 636 -p TCP exits with return code 0x00000002. Portqry.exe -n 192.168.10.11 -e 88 -p BOTH exits with return code 0x00000002. DC2 to DC3: portqry.exe -n 192.168.0.103 -e 135 -p TCP exits with return code 0x00000000. Portqry.exe -n 192.168.0.103 -e 137 -p UDP exits with return code 0x00000000.

Portqry.exe -n 192.168.0.103 -e 138 -p UDP exits with return code 0x00000002. Portqry.exe -n 192.168.0.103 -e 139 -p TCP exits with return code 0x00000000. Portqry.exe -n 192.168.0.103 -e 3268 -p TCP exits with return code 0x00000000. Portqry.exe -n 192.168.0.103 -e 3269 -p TCP exits with return code 0x00000000.

Portqry.exe -n 192.168.0.103 -e 389 -p BOTH exits with return code 0x00000001. Portqry.exe -n 192.168.0.103 -e 42 -p TCP exits with return code 0x00000001. Portqry.exe -n 192.168.0.103 -e 445 -p TCP exits with return code 0x00000000. Portqry.exe -n 192.168.0.103 -e 53 -p BOTH exits with return code 0x00000000. Portqry.exe -n 192.168.0.103 -e 636 -p TCP exits with return code 0x00000000. Portqry.exe -n 192.168.0.103 -e 88 -p BOTH exits with return code 0x00000002.Select all. Here are the results of dcdiag /v for DC2-5099 (192.168.0.102):Directory Server Diagnosis Performing initial setup: Trying to find home server.

Verifying that the local machine DC2-5099, is a Directory Server. Home Server = DC2-5099. Connecting to directory service on server DC2-5099.

Identified AD Forest. Collecting AD specific global data. Collecting site info.

Unzip Is Not Recognized As An Internal Or External Command Operable Program Or Batch File

Calling ldapsearchinitpage(hld,CN=Sites,CN=Configuration,DC=network,DC=local,LDAPSCOPESUBTREE,(objectCategory=ntDSSiteSettings). The previous call succeeded Iterating through the sites Looking at base site object: CN=NTDS Site Settings,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=network,DC=local Getting ISTG and options for the site. Identifying all servers. Calling ldapsearchinitpage(hld,CN=Sites,CN=Configuration,DC=network,DC=local,LDAPSCOPESUBTREE,(objectClass=ntDSDsa). The previous call succeeded.