Hi All

Domain name: abc.com
DC1 - Windows Server 2003 R2 (Physical Server) - 192.168.1.1
DC2 - Windows Server 2012 (Virtual Machine) - 192.168.1.2

Somehow DC1 doesn't replicated to DC2.

-------------------------------------------------------------

netdom query fsmo's result:
Schema master                DC1.abc.COM
Domain naming master    DC1.abc.COM
PDC                                  DC1.abc.COM
RID pool manager            DC1.abc.COM
Infrastructure master       DC1.abc.COM
The command completed successfully.

-------------------------------------------------------------

I run dcdiag in DC1:

Domain Controller Diagnosis

Performing initial setup:
   Done gathering initial info.

Doing initial required tests

   Testing server: Default-First-Site\DC1
      Starting test: Connectivity
         The host bd9e6e75-ec75-4c6b-be1b-ebef58146bbe._msdcs.abc.COM could not b
e resolved to an
         IP address.  Check the DNS server, DHCP, server name, etc
         Although the Guid DNS name
         (bd9e6e75-ec75-4c6b-be1b-ebef58146bbe._msdcs.abc.COM) couldn't be
         resolved, the server name (DC1.abc.COM) resolved to the IP address
         (192.168.1.1) and was pingable.  Check that the IP address is
         registered correctly with the DNS server.
         ......................... DC1 failed test Connectivity

Doing primary tests

   Testing server: Default-First-Site\DC1
      Skipping all tests, because server DC1 is
      not responding to directory service requests

   Running partition tests on : TAPI3Directory
      Starting test: CrossRefValidation
         ......................... TAPI3Directory passed test CrossRefValidation

      Starting test: CheckSDRefDom
         ......................... TAPI3Directory passed test CheckSDRefDom

   Running partition tests on : ForestDnsZones
      Starting test: CrossRefValidation
         ......................... ForestDnsZones passed test CrossRefValidation

      Starting test: CheckSDRefDom
         ......................... ForestDnsZones passed test CheckSDRefDom

   Running partition tests on : DomainDnsZones
      Starting test: CrossRefValidation
         ......................... DomainDnsZones passed test CrossRefValidation

      Starting test: CheckSDRefDom
         ......................... DomainDnsZones passed test CheckSDRefDom

   Running partition tests on : Schema
      Starting test: CrossRefValidation
         ......................... Schema passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Schema passed test CheckSDRefDom

   Running partition tests on : Configuration
      Starting test: CrossRefValidation
         ......................... Configuration passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Configuration passed test CheckSDRefDom

   Running partition tests on : abc
      Starting test: CrossRefValidation
         ......................... abc passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... abc passed test CheckSDRefDom

   Running enterprise tests on : abc.COM
      Starting test: Intersite
         ......................... abc.COM passed test Intersite
      Starting test: FsmoCheck
         ......................... abc.COM passed test FsmoCheck

-------------------------------------------------------------------------

But funny thing is I able to ping DC1 name from DC2 and workstations:

C:\Users\User>ping dc1

Pinging dc1.abc.com [192.168.1.1] with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time<1ms TTL=128
Reply from 192.168.1.1: bytes=32 time<1ms TTL=128
Reply from 192.168.1.1: bytes=32 time<1ms TTL=128
Reply from 192.168.1.1: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

---------------------------------------------------------------------------

I also run repadmin on DC1,
Result:

C:\>repadmin /showrepl /all /verbose

repadmin running command /showrepl against server localhost

Default-First-Site\DC1
DC Options: IS_GC
Site Options: (none)
DC object GUID: bd9e6e75-ec75-4c6b-be1b-ebef58146bbe
DC invocationID: bd9e6e75-ec75-4c6b-be1b-ebef58146bbe

==== INBOUND NEIGHBORS ======================================

DC=ABC,DC=COM
    Default-First-Site\DC2 via RPC
        DC object GUID: 2bdd0be7-3dfa-4158-b8bd-c54124226e6c
        Address: 2bdd0be7-3dfa-4158-b8bd-c54124226e6c._msdcs.ABC.COM
        DC invocationID: 7b99d5b5-1757-4533-9976-907907e99eff
        SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
        USNs: 2190434/OU, 2190434/PU
        Last attempt @ 2014-05-21 15:14:40 failed, result 1753 (0x6d9):
            There are no more endpoints available from the endpoint mapper.
        1400 consecutive failure(s).
        Last success @ 2014-05-20 15:38:26.

CN=Configuration,DC=ABC,DC=COM
    Default-First-Site\DC2 via RPC
        DC object GUID: 2bdd0be7-3dfa-4158-b8bd-c54124226e6c
        Address: 2bdd0be7-3dfa-4158-b8bd-c54124226e6c._msdcs.ABC.COM
        DC invocationID: 7b99d5b5-1757-4533-9976-907907e99eff
        SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
        USNs: 2180668/OU, 2180668/PU
        Last attempt @ 2014-05-21 14:54:49 failed, result 1753 (0x6d9):
            There are no more endpoints available from the endpoint mapper.
        118 consecutive failure(s).
        Last success @ 2014-05-17 00:54:43.

CN=Schema,CN=Configuration,DC=ABC,DC=COM
    Default-First-Site\DC2 via RPC
        DC object GUID: 2bdd0be7-3dfa-4158-b8bd-c54124226e6c
        Address: 2bdd0be7-3dfa-4158-b8bd-c54124226e6c._msdcs.ABC.COM
        DC invocationID: 7b99d5b5-1757-4533-9976-907907e99eff
        SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
        USNs: 2110088/OU, 2110088/PU
        Last attempt @ 2014-05-21 14:55:15 failed, result 1753 (0x6d9):
            There are no more endpoints available from the endpoint mapper.
        110 consecutive failure(s).
        Last success @ 2014-05-17 00:54:43.

DC=DomainDnsZones,DC=ABC,DC=COM
    Default-First-Site\DC2 via RPC
        DC object GUID: 2bdd0be7-3dfa-4158-b8bd-c54124226e6c
        Address: 2bdd0be7-3dfa-4158-b8bd-c54124226e6c._msdcs.ABC.COM
        DC invocationID: 7b99d5b5-1757-4533-9976-907907e99eff
        SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
        USNs: 2190524/OU, 2190524/PU
        Last attempt @ 2014-05-21 14:54:24 failed, result 1256 (0x4e8):
            The remote system is not available. For information about network tr
oubleshooting, see Windows Help.
        32 consecutive failure(s).
        Last success @ 2014-05-20 15:38:27.

DC=ForestDnsZones,DC=ABC,DC=COM
    Default-First-Site\DC2 via RPC
        DC object GUID: 2bdd0be7-3dfa-4158-b8bd-c54124226e6c
        Address: 2bdd0be7-3dfa-4158-b8bd-c54124226e6c._msdcs.ABC.COM
        DC invocationID: 7b99d5b5-1757-4533-9976-907907e99eff
        SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
        USNs: 2106507/OU, 2106507/PU
        Last attempt @ 2014-05-21 14:54:24 failed, result 1256 (0x4e8):
            The remote system is not available. For information about network tr
oubleshooting, see Windows Help.
        507 consecutive failure(s).
        Last success @ 2014-04-30 16:48:21.

==== OUTBOUND NEIGHBORS FOR CHANGE NOTIFICATIONS ============

CN=Configuration,DC=ABC,DC=COM
    Default-First-Site\DC2 via RPC
        DC object GUID: 2bdd0be7-3dfa-4158-b8bd-c54124226e6c
        Address: 2bdd0be7-3dfa-4158-b8bd-c54124226e6c._msdcs.ABC.COM
        WRITEABLE
        Last attempt @ (never) was successful.

CN=Schema,CN=Configuration,DC=ABC,DC=COM
    Default-First-Site\DC2 via RPC
        DC object GUID: 2bdd0be7-3dfa-4158-b8bd-c54124226e6c
        Address: 2bdd0be7-3dfa-4158-b8bd-c54124226e6c._msdcs.ABC.COM
        WRITEABLE
        Last attempt @ 2014-05-17 00:55:01 was successful.

DC=DomainDnsZones,DC=ABC,DC=COM
    Default-First-Site\DC2 via RPC
        DC object GUID: 2bdd0be7-3dfa-4158-b8bd-c54124226e6c
        Address: 2bdd0be7-3dfa-4158-b8bd-c54124226e6c._msdcs.ABC.COM
        WRITEABLE
        Last attempt @ (never) was successful.

DC=ForestDnsZones,DC=ABC,DC=COM
    Default-First-Site\DC2 via RPC
        DC object GUID: 2bdd0be7-3dfa-4158-b8bd-c54124226e6c
        Address: 2bdd0be7-3dfa-4158-b8bd-c54124226e6c._msdcs.ABC.COM
        WRITEABLE
        Last attempt @ (never) was successful.

==== KCC CONNECTION OBJECTS ============================================
Connection --
    Connection name : 2e2755c0-c2b1-484b-a0b2-489926271fd4
    Server DNS name : DC1.ABC.COM
    Server DN  name : CN=NTDS Settings,CN=DC1,CN=Servers,CN=Default-First-Sit
e,CN=Sites,CN=Configuration,DC=ABC,DC=COM
        Source: Default-First-Site\DC2
******* 1382 CONSECUTIVE FAILURES since 2014-05-20 15:38:27
Last error: 1256 (0x4e8):
            The remote system is not available. For information about network tr
oubleshooting, see Windows Help.
        TransportType: intrasite RPC
        options:  isGenerated
        ReplicatesNC: DC=ABC,DC=COM
        Reason:  StaleServersTopology
                Replica link has been added.
        ReplicatesNC: DC=DomainDnsZones,DC=ABC,DC=COM
        Reason:  StaleServersTopology
                Replica link has been added.
        ReplicatesNC: CN=Schema,CN=Configuration,DC=ABC,DC=COM
        Reason:  StaleServersTopology
                Replica link has been added.
        ReplicatesNC: DC=ForestDnsZones,DC=ABC,DC=COM
        Reason:  StaleServersTopology
                Replica link has been added.
        ReplicatesNC: CN=Configuration,DC=ABC,DC=COM
        Reason:  StaleServersTopology
                Replica link has been added.
        enabledConnection:         whenChanged: 20140520094554.0Z
        whenCreated: 20131005064554.0Z
        Schedule:
        day: 0123456789ab0123456789ab
        Sun: 111111111111111111111111
        Mon: 111111111111111111111111
        Tue: 111111111111111111111111
        Wed: 111111111111111111111111
        Thu: 111111111111111111111111
        Fri: 111111111111111111111111
        Sat: 111111111111111111111111
1 connections found.

Partition Replication Schedule Loading:

      00      01      02      03      04      05      06      07      08      09
      10      11

 0 1 2 3 0 1 2 3 0 1 2 3 0 1 2 3 0 1 2 3 0 1 2 3 0 1 2 3 0 1 2 3 0 1 2 3 0 1 2 3
 0 1 2 3 0 1 2 3
        Sun: 0500000005000000050000000500000005000000050000000500000005000000050
00000050000000500000005000000
        Sun: 0500000005000000050000000500000005000000050000000500000005000000050
00000050000000500000005000000
        Mon: 0500000005000000050000000500000005000000050000000500000005000000050
00000050000000500000005000000
        Mon: 0500000005000000050000000500000005000000050000000500000005000000050
00000050000000500000005000000
        Tue: 0500000005000000050000000500000005000000050000000500000005000000050
00000050000000500000005000000
        Tue: 0500000005000000050000000500000005000000050000000500000005000000050
00000050000000500000005000000
        Wed: 0500000005000000050000000500000005000000050000000500000005000000050
00000050000000500000005000000
        Wed: 0500000005000000050000000500000005000000050000000500000005000000050
00000050000000500000005000000
        Thu: 0500000005000000050000000500000005000000050000000500000005000000050
00000050000000500000005000000
        Thu: 0500000005000000050000000500000005000000050000000500000005000000050
00000050000000500000005000000
        Fri: 0500000005000000050000000500000005000000050000000500000005000000050
00000050000000500000005000000
        Fri: 0500000005000000050000000500000005000000050000000500000005000000050
00000050000000500000005000000
        Sat: 0500000005000000050000000500000005000000050000000500000005000000050
00000050000000500000005000000
        Sat: 0500000005000000050000000500000005000000050000000500000005000000050
00000050000000500000005000000

Any suggestion, thanks.

Run in DC2:

PS C:\> Get-BPAModel Microsoft/Windows/DirectoryServices |Invoke-BPAModel


ModelId           : Microsoft/Windows/DirectoryServices
SubModelId        :
Success           : True
ScanTime          : 5/21/2014 5:05:32 PM
ScanTimeUtcOffset : 08:00:00
Detail            : {DC2, DC2}


PS C:\> Get-BPAModel Microsoft/Windows/DNSServer |Invoke-BPAModel


ModelId           : Microsoft/Windows/DNSServer
SubModelId        :
Success           : True
ScanTime          : 5/21/2014 5:09:13 PM
ScanTimeUtcOffset : 08:00:00
Detail            : {DC2, DC2}

Netdiag /q result on DC1:

Per interface results:

    Adapter : Local Area Connection 2

        Host Name. . . . . . . . . : DC1
        IP Address . . . . . . . . : 192.168.1.1
        Subnet Mask. . . . . . . . : 255.255.255.0
        Default Gateway. . . . . . : 192.168.1.100
        Dns Servers. . . . . . . . : 192.168.1.2
                                     192.168.1.1



        WINS service test. . . . . : Skipped


Global results:
    [WARNING] You don't have a single interface with the <00> 'WorkStation Service', <03> 'Messenger Service', <20> 'WINS' names defined.


DNS test . . . . . . . . . . . . . : Failed
       [WARNING] The DNS entries for this DC cannot be verified right now on DNS server 192.168.1.2, ERROR_TIMEOUT.
    [WARNING] The DNS entries for this DC are not registered correctly on DNS server '192.168.1.1'. Please wait for 30 minutes for DNS server replication.
    [FATAL] No DNS servers have the DNS records for this DC registered.

IP Security test . . . . . . . . . : Skipped

Hi,

This issue occurs when the destination DC fails to bind to the source DC using RPC. 
Check whether the required RPC ports are opened in the firewall for AD replication between the DC1 and DC2. 

Checkout the below link on Troubleshooting AD Replication,
http://technet.microsoft.com/en-us/library/replication-error-1256-the-remote-system-is-not-available(v=ws.10).aspx#BKMK_Cause

Regards,
Gopi
JiJi Technologies

• Edited by Gopi-JiJiTechnologies Wednesday, May 21, 2014 9:36 AM

Greetings!

You have error 1753 in your log. Verify if RPC service is started in your services. Also if you have any third party firewall tools, try to disable them and then initiate the replication. More information on below link:

• Troubleshooting AD Replication error 1753

Regards.

Helpful things for the forum

Please post the following:
ipconfig /all from both DC's
nslookup of partner DC's from each DC
portQryUI with the "Domains and Trusts" query option from each DC pointing to the partner DC

You most likely have a multi-homed DC, bad dns config, missing DNS record or a FW issue

portQryUI
http://www.microsoft.com/en-us/download/details.aspx?id=24009

Hi Mahdi

RPC service is running for both.
firewall is disabled for both.

Hi Paul

Info from DC1:

C:\>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : DC1
   Primary Dns Suffix  . . . . . . . : abc.COM
   Node Type . . . . . . . . . . . . : Unknown
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : abc.COM

Ethernet adapter Local Area Connection 2:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Broadcom BCM5708C NetXtreme II GigE (NDIS
 VBD Client)
   Physical Address. . . . . . . . . : 00-1A-64-0A-C0-4E
   DHCP Enabled. . . . . . . . . . . : No
   IP Address. . . . . . . . . . . . : 192.168.1.1
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.1.100
   DNS Servers . . . . . . . . . . . : 192.168.1.2
                                       192.168.1.1


C:\>nslookup
DNS request timed out.
    timeout was 2 seconds.
*** Can't find server name for address 192.168.1.2: Timed out
Default Server:  UnKnown
Address:  192.168.1.2

Hi Paul

Info from DC1:

Starting portqry.exe -n 192.168.1.2 -e 135 -p TCP ...


Querying target system called:

 192.168.1.2

Attempting to resolve IP address to a name...


IP address resolved to dc2.abc.com

querying...

TCP port 135 (epmap service): LISTENING

Using ephemeral source port
Querying Endpoint Mapper Database...
Server's response:

UUID: d95afe70-a6d5-4259-822e-2c84da1ddb0d
ncacn_ip_tcp:192.168.1.2[49152]

UUID: b2507c30-b126-494a-92ac-ee32b6eeb039
ncalrpc:[OLE563182CEF478C3A14653D062D772]

UUID: b2507c30-b126-494a-92ac-ee32b6eeb039
ncalrpc:[LRPC-fd920cc2d92f99660e]

UUID: 76f226c3-ec14-4325-8a99-6a46348418af
ncalrpc:[WMsgKRpc013EEBBB3]

UUID: 76f226c3-ec14-4325-8a99-6a46348418af
ncalrpc:[WMsgKRpc094591E2]

UUID: 12e65dd8-887f-41ef-91bf-8d816c42c2e7 Secure Desktop LRPC interface
ncalrpc:[WMsgKRpc094591E2]

UUID: 906b0ce0-c70b-1067-b317-00dd010662da
ncalrpc:[LRPC-718e5b08ea729d2926]

UUID: 906b0ce0-c70b-1067-b317-00dd010662da
ncalrpc:[LRPC-718e5b08ea729d2926]

UUID: 906b0ce0-c70b-1067-b317-00dd010662da
ncalrpc:[LRPC-718e5b08ea729d2926]

UUID: f763c91c-2ab1-47fa-868f-7de7efd42194 VM Allow-List Provider RPC
ncalrpc:[OLEED37CE9CBAC28EC99D9933545A44]

UUID: f763c91c-2ab1-47fa-868f-7de7efd42194 VM Allow-List Provider RPC
ncalrpc:[RdvVmAllowListRpc]

UUID: 50abc2a4-574d-40b3-9d66-ee4fd5fba076
ncacn_ip_tcp:192.168.1.2[56001]

UUID: 367abb81-9844-35f1-ad32-98f038001003
ncacn_ip_tcp:192.168.1.2[55992]

UUID: 6bffd098-a112-3610-9833-46c3f874532d
ncalrpc:[OLE8547DF8F5A8A2691524B9BE9E7E1]

UUID: 6bffd098-a112-3610-9833-46c3f874532d
ncacn_ip_tcp:192.168.1.2[55982]

UUID: 5b821720-f63b-11d0-aad2-00c04fc324db
ncalrpc:[OLE8547DF8F5A8A2691524B9BE9E7E1]

UUID: 5b821720-f63b-11d0-aad2-00c04fc324db
ncacn_ip_tcp:192.168.1.2[55982]

UUID: f5cc59b4-4264-101a-8c59-08002b2f8426 NtFrs Service
ncalrpc:[OLE4F01D4F32CF4FF20E30658C178A4]

UUID: f5cc59b4-4264-101a-8c59-08002b2f8426 NtFrs Service
ncacn_ip_tcp:192.168.1.2[55965]

UUID: f5cc59b4-4264-101a-8c59-08002b2f8426 NtFrs Service
ncalrpc:[LRPC-6465a69e9cd02a03ea]

UUID: d049b186-814f-11d1-9a3c-00c04fc9b232 NtFrs API
ncalrpc:[OLE4F01D4F32CF4FF20E30658C178A4]

UUID: d049b186-814f-11d1-9a3c-00c04fc9b232 NtFrs API
ncacn_ip_tcp:192.168.1.2[55965]

UUID: d049b186-814f-11d1-9a3c-00c04fc9b232 NtFrs API
ncalrpc:[LRPC-6465a69e9cd02a03ea]

UUID: a00c021c-2be2-11d2-b678-0000f87a8f8e PERFMON SERVICE
ncalrpc:[OLE4F01D4F32CF4FF20E30658C178A4]

UUID: a00c021c-2be2-11d2-b678-0000f87a8f8e PERFMON SERVICE
ncacn_ip_tcp:192.168.1.2[55965]

UUID: a00c021c-2be2-11d2-b678-0000f87a8f8e PERFMON SERVICE
ncalrpc:[LRPC-6465a69e9cd02a03ea]

UUID: 0b6edbfa-4a24-4fc6-8a23-942b1eca65d1 Spooler function endpoint
ncalrpc:[spoolss]

UUID: ae33069b-a2a8-46ee-a235-ddfd339be281 Spooler base remote object endpoint
ncalrpc:[spoolss]

UUID: 4a452661-8290-4b36-8fbe-7f4093a94978 Spooler function endpoint
ncalrpc:[spoolss]

UUID: f2c9b409-c1c9-4100-8639-d8ab1486694a Witness Client Upcall Server
ncalrpc:[DNSResolver]

UUID: f2c9b409-c1c9-4100-8639-d8ab1486694a Witness Client Upcall Server
ncalrpc:[LRPC-e04435e83bae933e86]

UUID: eb081a0d-10ee-478a-a1dd-50995283e7a8 Witness Client Test Interface
ncalrpc:[DNSResolver]

UUID: eb081a0d-10ee-478a-a1dd-50995283e7a8 Witness Client Test Interface
ncalrpc:[LRPC-e04435e83bae933e86]

UUID: 7f1343fe-50a9-4927-a778-0c5859517bac DfsDs service
ncalrpc:[DNSResolver]

UUID: 7f1343fe-50a9-4927-a778-0c5859517bac DfsDs service
ncalrpc:[LRPC-e04435e83bae933e86]

UUID: 7f1343fe-50a9-4927-a778-0c5859517bac DfsDs service
ncacn_np:\\\\DC2[\\PIPE\\wkssvc]

UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncacn_np:\\\\DC2[\\pipe\\lsass]

UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncalrpc:[audit]

UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncalrpc:[securityevent]

UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncalrpc:[LSARPC_ENDPOINT]

UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncalrpc:[lsacap]

UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncalrpc:[LSA_EAS_ENDPOINT]

UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncalrpc:[lsapolicylookup]

UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncalrpc:[lsasspirpc]

UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncalrpc:[protected_storage]

UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncalrpc:[SidKey Local End Point]

UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncalrpc:[samss lpc]

UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncalrpc:[OLED28048DC13D14B9EE9E902CF0222]

UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncacn_np:\\\\DC2[\\pipe\\lsass]

UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncalrpc:[audit]

UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncalrpc:[securityevent]

UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncalrpc:[LSARPC_ENDPOINT]

UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncalrpc:[lsacap]

UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncalrpc:[LSA_EAS_ENDPOINT]

UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncalrpc:[lsapolicylookup]

UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncalrpc:[lsasspirpc]

UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncalrpc:[protected_storage]

UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncalrpc:[SidKey Local End Point]

UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncalrpc:[samss lpc]

UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncalrpc:[OLED28048DC13D14B9EE9E902CF0222]

UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncacn_ip_tcp:192.168.1.2[49156]

UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncalrpc:[NTDS_LPC]

UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncacn_http:192.168.1.2[49157]

UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncacn_np:\\\\DC2[\\pipe\\b8d41bc7af954a5b]

UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncacn_np:\\\\DC2[\\pipe\\lsass]

UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncalrpc:[audit]

UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncalrpc:[securityevent]

UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncalrpc:[LSARPC_ENDPOINT]

UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncalrpc:[lsacap]

UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncalrpc:[LSA_EAS_ENDPOINT]

UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncalrpc:[lsapolicylookup]

UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncalrpc:[lsasspirpc]

UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncalrpc:[protected_storage]

UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncalrpc:[SidKey Local End Point]

UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncalrpc:[samss lpc]

UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncalrpc:[OLED28048DC13D14B9EE9E902CF0222]

UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncacn_ip_tcp:192.168.1.2[49156]

UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncalrpc:[NTDS_LPC]

UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncacn_http:192.168.1.2[49157]

UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncacn_np:\\\\DC2[\\pipe\\b8d41bc7af954a5b]

UUID: 12345778-1234-abcd-ef00-0123456789ab
ncacn_np:\\\\DC2[\\pipe\\lsass]

UUID: 12345778-1234-abcd-ef00-0123456789ab
ncalrpc:[audit]

UUID: 12345778-1234-abcd-ef00-0123456789ab
ncalrpc:[securityevent]

UUID: 12345778-1234-abcd-ef00-0123456789ab
ncalrpc:[LSARPC_ENDPOINT]

UUID: 12345778-1234-abcd-ef00-0123456789ab
ncalrpc:[lsacap]

UUID: 12345778-1234-abcd-ef00-0123456789ab
ncalrpc:[LSA_EAS_ENDPOINT]

UUID: 12345778-1234-abcd-ef00-0123456789ab
ncalrpc:[lsapolicylookup]

UUID: 12345778-1234-abcd-ef00-0123456789ab
ncalrpc:[lsasspirpc]

UUID: 12345778-1234-abcd-ef00-0123456789ab
ncalrpc:[protected_storage]

UUID: 12345778-1234-abcd-ef00-0123456789ab
ncalrpc:[SidKey Local End Point]

UUID: 12345778-1234-abcd-ef00-0123456789ab
ncalrpc:[samss lpc]

UUID: 12345778-1234-abcd-ef00-0123456789ab
ncalrpc:[OLED28048DC13D14B9EE9E902CF0222]

UUID: 12345778-1234-abcd-ef00-0123456789ab
ncacn_ip_tcp:192.168.1.2[49156]

UUID: 12345778-1234-abcd-ef00-0123456789ab
ncalrpc:[NTDS_LPC]

UUID: 12345778-1234-abcd-ef00-0123456789ab
ncacn_http:192.168.1.2[49157]

UUID: 12345778-1234-abcd-ef00-0123456789ab
ncacn_np:\\\\DC2[\\pipe\\b8d41bc7af954a5b]

UUID: 12345778-1234-abcd-ef00-0123456789ac
ncacn_np:\\\\DC2[\\pipe\\lsass]

UUID: 12345778-1234-abcd-ef00-0123456789ac
ncalrpc:[audit]

UUID: 12345778-1234-abcd-ef00-0123456789ac
ncalrpc:[securityevent]

UUID: 12345778-1234-abcd-ef00-0123456789ac
ncalrpc:[LSARPC_ENDPOINT]

UUID: 12345778-1234-abcd-ef00-0123456789ac
ncalrpc:[lsacap]

UUID: 12345778-1234-abcd-ef00-0123456789ac
ncalrpc:[LSA_EAS_ENDPOINT]

UUID: 12345778-1234-abcd-ef00-0123456789ac
ncalrpc:[lsapolicylookup]

UUID: 12345778-1234-abcd-ef00-0123456789ac
ncalrpc:[lsasspirpc]

UUID: 12345778-1234-abcd-ef00-0123456789ac
ncalrpc:[protected_storage]

UUID: 12345778-1234-abcd-ef00-0123456789ac
ncalrpc:[SidKey Local End Point]

UUID: 12345778-1234-abcd-ef00-0123456789ac
ncalrpc:[samss lpc]

UUID: 12345778-1234-abcd-ef00-0123456789ac
ncalrpc:[OLED28048DC13D14B9EE9E902CF0222]

UUID: 12345778-1234-abcd-ef00-0123456789ac
ncacn_ip_tcp:192.168.1.2[49156]

UUID: 12345778-1234-abcd-ef00-0123456789ac
ncalrpc:[NTDS_LPC]

UUID: 12345778-1234-abcd-ef00-0123456789ac
ncacn_http:192.168.1.2[49157]

UUID: 12345778-1234-abcd-ef00-0123456789ac
ncacn_np:\\\\DC2[\\pipe\\b8d41bc7af954a5b]

UUID: 12345778-1234-abcd-ef00-0123456789ac
ncacn_ip_tcp:192.168.1.2[49158]

UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncacn_np:\\\\DC2[\\pipe\\lsass]

UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncalrpc:[audit]

UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncalrpc:[securityevent]

UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncalrpc:[LSARPC_ENDPOINT]

UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncalrpc:[lsacap]

UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncalrpc:[LSA_EAS_ENDPOINT]

UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncalrpc:[lsapolicylookup]

UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncalrpc:[lsasspirpc]

UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncalrpc:[protected_storage]

UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncalrpc:[SidKey Local End Point]

UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncalrpc:[samss lpc]

UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncalrpc:[OLED28048DC13D14B9EE9E902CF0222]

UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncacn_ip_tcp:192.168.1.2[49156]

UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncalrpc:[NTDS_LPC]

UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncacn_http:192.168.1.2[49157]

UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncacn_np:\\\\DC2[\\pipe\\b8d41bc7af954a5b]

UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncacn_ip_tcp:192.168.1.2[49158]

UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncalrpc:[NETLOGON_LRPC]

UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncacn_np:\\\\DC2[\\pipe\\lsass]

UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncalrpc:[audit]

UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncalrpc:[securityevent]

UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncalrpc:[LSARPC_ENDPOINT]

UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncalrpc:[lsacap]

UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncalrpc:[LSA_EAS_ENDPOINT]

UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncalrpc:[lsapolicylookup]

UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncalrpc:[lsasspirpc]

UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncalrpc:[protected_storage]

UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncalrpc:[SidKey Local End Point]

UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncalrpc:[samss lpc]

UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncalrpc:[OLED28048DC13D14B9EE9E902CF0222]

UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncacn_ip_tcp:192.168.1.2[49156]

UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncalrpc:[NTDS_LPC]

UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncacn_http:192.168.1.2[49157]

UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncacn_np:\\\\DC2[\\pipe\\b8d41bc7af954a5b]

UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncacn_ip_tcp:192.168.1.2[49158]

UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncalrpc:[NETLOGON_LRPC]

UUID: 12345678-1234-abcd-ef00-01234567cffb
ncacn_np:\\\\DC2[\\pipe\\lsass]

UUID: 12345678-1234-abcd-ef00-01234567cffb
ncalrpc:[audit]

UUID: 12345678-1234-abcd-ef00-01234567cffb
ncalrpc:[securityevent]

UUID: 12345678-1234-abcd-ef00-01234567cffb
ncalrpc:[LSARPC_ENDPOINT]

UUID: 12345678-1234-abcd-ef00-01234567cffb
ncalrpc:[lsacap]

UUID: 12345678-1234-abcd-ef00-01234567cffb
ncalrpc:[LSA_EAS_ENDPOINT]

UUID: 12345678-1234-abcd-ef00-01234567cffb
ncalrpc:[lsapolicylookup]

UUID: 12345678-1234-abcd-ef00-01234567cffb
ncalrpc:[lsasspirpc]

UUID: 12345678-1234-abcd-ef00-01234567cffb
ncalrpc:[protected_storage]

UUID: 12345678-1234-abcd-ef00-01234567cffb
ncalrpc:[SidKey Local End Point]

UUID: 12345678-1234-abcd-ef00-01234567cffb
ncalrpc:[samss lpc]

UUID: 12345678-1234-abcd-ef00-01234567cffb
ncalrpc:[OLED28048DC13D14B9EE9E902CF0222]

UUID: 12345678-1234-abcd-ef00-01234567cffb
ncacn_ip_tcp:192.168.1.2[49156]

UUID: 12345678-1234-abcd-ef00-01234567cffb
ncalrpc:[NTDS_LPC]

UUID: 12345678-1234-abcd-ef00-01234567cffb
ncacn_http:192.168.1.2[49157]

UUID: 12345678-1234-abcd-ef00-01234567cffb
ncacn_np:\\\\DC2[\\pipe\\b8d41bc7af954a5b]

UUID: 12345678-1234-abcd-ef00-01234567cffb
ncacn_ip_tcp:192.168.1.2[49158]

UUID: 12345678-1234-abcd-ef00-01234567cffb
ncalrpc:[NETLOGON_LRPC]

UUID: dd490425-5325-4565-b774-7e27d6c09c24 Base Firewall Engine API
ncalrpc:[LRPC-4270f9981254faa91d]

UUID: 7f9d11bf-7fb9-436b-a812-b2d50c5d4c03 Fw APIs
ncalrpc:[LRPC-4270f9981254faa91d]

UUID: 7f9d11bf-7fb9-436b-a812-b2d50c5d4c03 Fw APIs
ncalrpc:[LRPC-d35d2bd87814618631]

UUID: f47433c3-3e9d-4157-aad4-83aa1f5c2d4c Fw APIs
ncalrpc:[LRPC-4270f9981254faa91d]

UUID: f47433c3-3e9d-4157-aad4-83aa1f5c2d4c Fw APIs
ncalrpc:[LRPC-d35d2bd87814618631]

UUID: 2fb92682-6599-42dc-ae13-bd2ca89bd11c Fw APIs
ncalrpc:[LRPC-4270f9981254faa91d]

UUID: 2fb92682-6599-42dc-ae13-bd2ca89bd11c Fw APIs
ncalrpc:[LRPC-d35d2bd87814618631]

UUID: 7ea70bcf-48af-4f6a-8968-6a440754d5fa NSI server endpoint
ncalrpc:[OLEA9AB9FCCA745604305A49AF0A69C]

UUID: 7ea70bcf-48af-4f6a-8968-6a440754d5fa NSI server endpoint
ncalrpc:[LRPC-a135c3326e5cbba3aa]

UUID: 3473dd4d-2e88-4006-9cba-22570909dd10 WinHttp Auto-Proxy Service
ncalrpc:[OLEA9AB9FCCA745604305A49AF0A69C]

UUID: 3473dd4d-2e88-4006-9cba-22570909dd10 WinHttp Auto-Proxy Service
ncalrpc:[LRPC-a135c3326e5cbba3aa]

UUID: 3473dd4d-2e88-4006-9cba-22570909dd10 WinHttp Auto-Proxy Service
ncalrpc:[W32TIME_ALT]

UUID: 3473dd4d-2e88-4006-9cba-22570909dd10 WinHttp Auto-Proxy Service
ncacn_np:\\\\DC2[\\PIPE\\W32TIME_ALT]

UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncalrpc:[IUserProfile2]

UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncalrpc:[IUserProfile2]

UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncalrpc:[OLEF68E3C474DF50EBF13CB4B050548]

UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncalrpc:[senssvc]

UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncalrpc:[IUserProfile2]

UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncalrpc:[OLEF68E3C474DF50EBF13CB4B050548]

UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncalrpc:[senssvc]

UUID: 2eb08e3e-639f-4fba-97b1-14f878961076 Group Policy RPC Interface
ncalrpc:[LRPC-182e6d1994fef1b6b4]

UUID: 0a74ef1c-41a4-4e06-83ae-dc74fb1cdd53
ncalrpc:[IUserProfile2]

UUID: 0a74ef1c-41a4-4e06-83ae-dc74fb1cdd53
ncalrpc:[OLEF68E3C474DF50EBF13CB4B050548]

UUID: 0a74ef1c-41a4-4e06-83ae-dc74fb1cdd53
ncalrpc:[senssvc]

UUID: 1ff70682-0a51-30e8-076d-740be8cee98b
ncalrpc:[IUserProfile2]

UUID: 1ff70682-0a51-30e8-076d-740be8cee98b
ncalrpc:[OLEF68E3C474DF50EBF13CB4B050548]

UUID: 1ff70682-0a51-30e8-076d-740be8cee98b
ncalrpc:[senssvc]

UUID: 1ff70682-0a51-30e8-076d-740be8cee98b
ncacn_np:\\\\DC2[\\PIPE\\atsvc]

UUID: 378e52b0-c0a9-11cf-822d-00aa0051e40f
ncalrpc:[IUserProfile2]

UUID: 378e52b0-c0a9-11cf-822d-00aa0051e40f
ncalrpc:[OLEF68E3C474DF50EBF13CB4B050548]

UUID: 378e52b0-c0a9-11cf-822d-00aa0051e40f
ncalrpc:[senssvc]

UUID: 378e52b0-c0a9-11cf-822d-00aa0051e40f
ncacn_np:\\\\DC2[\\PIPE\\atsvc]

UUID: 86d35949-83c9-4044-b424-db363231fd0c
ncalrpc:[IUserProfile2]

UUID: 86d35949-83c9-4044-b424-db363231fd0c
ncalrpc:[OLEF68E3C474DF50EBF13CB4B050548]

UUID: 86d35949-83c9-4044-b424-db363231fd0c
ncalrpc:[senssvc]

UUID: 86d35949-83c9-4044-b424-db363231fd0c
ncacn_np:\\\\DC2[\\PIPE\\atsvc]

UUID: 86d35949-83c9-4044-b424-db363231fd0c
ncacn_ip_tcp:192.168.1.2[49154]

UUID: 3a9ef155-691d-4449-8d05-09ad57031823
ncalrpc:[IUserProfile2]

UUID: 3a9ef155-691d-4449-8d05-09ad57031823
ncalrpc:[OLEF68E3C474DF50EBF13CB4B050548]

UUID: 3a9ef155-691d-4449-8d05-09ad57031823
ncalrpc:[senssvc]

UUID: 3a9ef155-691d-4449-8d05-09ad57031823
ncacn_np:\\\\DC2[\\PIPE\\atsvc]

UUID: 3a9ef155-691d-4449-8d05-09ad57031823
ncacn_ip_tcp:192.168.1.2[49154]

UUID: 98716d03-89ac-44c7-bb8c-285824e51c4a XactSrv service
ncalrpc:[IUserProfile2]

UUID: 98716d03-89ac-44c7-bb8c-285824e51c4a XactSrv service
ncalrpc:[OLEF68E3C474DF50EBF13CB4B050548]

UUID: 98716d03-89ac-44c7-bb8c-285824e51c4a XactSrv service
ncalrpc:[senssvc]

UUID: 98716d03-89ac-44c7-bb8c-285824e51c4a XactSrv service
ncacn_np:\\\\DC2[\\PIPE\\atsvc]

UUID: 98716d03-89ac-44c7-bb8c-285824e51c4a XactSrv service
ncacn_ip_tcp:192.168.1.2[49154]

UUID: 1a0d010f-1c33-432c-b0f5-8cf4e8053099 IdSegSrv service
ncalrpc:[IUserProfile2]

UUID: 1a0d010f-1c33-432c-b0f5-8cf4e8053099 IdSegSrv service
ncalrpc:[OLEF68E3C474DF50EBF13CB4B050548]

UUID: 1a0d010f-1c33-432c-b0f5-8cf4e8053099 IdSegSrv service
ncalrpc:[senssvc]

UUID: 1a0d010f-1c33-432c-b0f5-8cf4e8053099 IdSegSrv service
ncacn_np:\\\\DC2[\\PIPE\\atsvc]

UUID: 1a0d010f-1c33-432c-b0f5-8cf4e8053099 IdSegSrv service
ncacn_ip_tcp:192.168.1.2[49154]

UUID: 552d076a-cb29-4e44-8b6a-d15e59e2c0af IP Transition Configuration endpoint
ncalrpc:[IUserProfile2]

UUID: 552d076a-cb29-4e44-8b6a-d15e59e2c0af IP Transition Configuration endpoint
ncalrpc:[OLEF68E3C474DF50EBF13CB4B050548]

UUID: 552d076a-cb29-4e44-8b6a-d15e59e2c0af IP Transition Configuration endpoint
ncalrpc:[senssvc]

UUID: 552d076a-cb29-4e44-8b6a-d15e59e2c0af IP Transition Configuration endpoint
ncacn_np:\\\\DC2[\\PIPE\\atsvc]

UUID: 552d076a-cb29-4e44-8b6a-d15e59e2c0af IP Transition Configuration endpoint
ncacn_ip_tcp:192.168.1.2[49154]

UUID: 552d076a-cb29-4e44-8b6a-d15e59e2c0af IP Transition Configuration endpoint
ncacn_np:\\\\DC2[\\PIPE\\srvsvc]

UUID: 2e6035b2-e8f1-41a7-a044-656b439c4c34 Proxy Manager provider server endpoint
ncalrpc:[IUserProfile2]

UUID: 2e6035b2-e8f1-41a7-a044-656b439c4c34 Proxy Manager provider server endpoint
ncalrpc:[OLEF68E3C474DF50EBF13CB4B050548]

UUID: 2e6035b2-e8f1-41a7-a044-656b439c4c34 Proxy Manager provider server endpoint
ncalrpc:[senssvc]

UUID: 2e6035b2-e8f1-41a7-a044-656b439c4c34 Proxy Manager provider server endpoint
ncacn_np:\\\\DC2[\\PIPE\\atsvc]

UUID: 2e6035b2-e8f1-41a7-a044-656b439c4c34 Proxy Manager provider server endpoint
ncacn_ip_tcp:192.168.1.2[49154]

UUID: 2e6035b2-e8f1-41a7-a044-656b439c4c34 Proxy Manager provider server endpoint
ncacn_np:\\\\DC2[\\PIPE\\srvsvc]

UUID: c36be077-e14b-4fe9-8abc-e856ef4f048b Proxy Manager client server endpoint
ncalrpc:[IUserProfile2]

UUID: c36be077-e14b-4fe9-8abc-e856ef4f048b Proxy Manager client server endpoint
ncalrpc:[OLEF68E3C474DF50EBF13CB4B050548]

UUID: c36be077-e14b-4fe9-8abc-e856ef4f048b Proxy Manager client server endpoint
ncalrpc:[senssvc]

UUID: c36be077-e14b-4fe9-8abc-e856ef4f048b Proxy Manager client server endpoint
ncacn_np:\\\\DC2[\\PIPE\\atsvc]

UUID: c36be077-e14b-4fe9-8abc-e856ef4f048b Proxy Manager client server endpoint
ncacn_ip_tcp:192.168.1.2[49154]

UUID: c36be077-e14b-4fe9-8abc-e856ef4f048b Proxy Manager client server endpoint
ncacn_np:\\\\DC2[\\PIPE\\srvsvc]

UUID: c49a5a70-8a7f-4e70-ba16-1e8f1f193ef1 Adh APIs
ncalrpc:[IUserProfile2]

UUID: c49a5a70-8a7f-4e70-ba16-1e8f1f193ef1 Adh APIs
ncalrpc:[OLEF68E3C474DF50EBF13CB4B050548]

UUID: c49a5a70-8a7f-4e70-ba16-1e8f1f193ef1 Adh APIs
ncalrpc:[senssvc]

UUID: c49a5a70-8a7f-4e70-ba16-1e8f1f193ef1 Adh APIs
ncacn_np:\\\\DC2[\\PIPE\\atsvc]

UUID: c49a5a70-8a7f-4e70-ba16-1e8f1f193ef1 Adh APIs
ncacn_ip_tcp:192.168.1.2[49154]

UUID: c49a5a70-8a7f-4e70-ba16-1e8f1f193ef1 Adh APIs
ncacn_np:\\\\DC2[\\PIPE\\srvsvc]

UUID: 30b044a5-a225-43f0-b3a4-e060df91f9c1
ncalrpc:[IUserProfile2]

UUID: 30b044a5-a225-43f0-b3a4-e060df91f9c1
ncalrpc:[OLEF68E3C474DF50EBF13CB4B050548]

UUID: 30b044a5-a225-43f0-b3a4-e060df91f9c1
ncalrpc:[senssvc]

UUID: 30b044a5-a225-43f0-b3a4-e060df91f9c1
ncacn_np:\\\\DC2[\\PIPE\\atsvc]

UUID: 30b044a5-a225-43f0-b3a4-e060df91f9c1
ncacn_ip_tcp:192.168.1.2[49154]

UUID: 30b044a5-a225-43f0-b3a4-e060df91f9c1
ncacn_np:\\\\DC2[\\PIPE\\srvsvc]

UUID: 30b044a5-a225-43f0-b3a4-e060df91f9c1
ncalrpc:[LRPC-d52bb987e6751941da]

UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncalrpc:[IUserProfile2]

UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncalrpc:[OLEF68E3C474DF50EBF13CB4B050548]

UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncalrpc:[senssvc]

UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncacn_np:\\\\DC2[\\PIPE\\atsvc]

UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncacn_ip_tcp:192.168.1.2[49154]

UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncacn_np:\\\\DC2[\\PIPE\\srvsvc]

UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncalrpc:[LRPC-d52bb987e6751941da]

UUID: f6beaff7-1e19-4fbb-9f8f-b89e2018337c Event log TCPIP
ncalrpc:[eventlog]

UUID: f6beaff7-1e19-4fbb-9f8f-b89e2018337c Event log TCPIP
ncacn_np:\\\\DC2[\\pipe\\eventlog]

UUID: f6beaff7-1e19-4fbb-9f8f-b89e2018337c Event log TCPIP
ncacn_ip_tcp:192.168.1.2[49153]

UUID: 30adc50c-5cbc-46ce-9a0e-91914789e23c NRP server endpoint
ncalrpc:[eventlog]

UUID: 30adc50c-5cbc-46ce-9a0e-91914789e23c NRP server endpoint
ncacn_np:\\\\DC2[\\pipe\\eventlog]

UUID: 30adc50c-5cbc-46ce-9a0e-91914789e23c NRP server endpoint
ncacn_ip_tcp:192.168.1.2[49153]

UUID: 30adc50c-5cbc-46ce-9a0e-91914789e23c NRP server endpoint
ncalrpc:[LRPC-78d564bf393b9716a5]

UUID: 3c4728c5-f0ab-448b-bda1-6ce01eb0a6d5 DHCP Client LRPC Endpoint
ncalrpc:[eventlog]

UUID: 3c4728c5-f0ab-448b-bda1-6ce01eb0a6d5 DHCP Client LRPC Endpoint
ncacn_np:\\\\DC2[\\pipe\\eventlog]

UUID: 3c4728c5-f0ab-448b-bda1-6ce01eb0a6d5 DHCP Client LRPC Endpoint
ncacn_ip_tcp:192.168.1.2[49153]

UUID: 3c4728c5-f0ab-448b-bda1-6ce01eb0a6d5 DHCP Client LRPC Endpoint
ncalrpc:[LRPC-78d564bf393b9716a5]

UUID: 3c4728c5-f0ab-448b-bda1-6ce01eb0a6d5 DHCP Client LRPC Endpoint
ncalrpc:[dhcpcsvc]

UUID: 3c4728c5-f0ab-448b-bda1-6ce01eb0a6d6 DHCPv6 Client LRPC Endpoint
ncalrpc:[eventlog]

UUID: 3c4728c5-f0ab-448b-bda1-6ce01eb0a6d6 DHCPv6 Client LRPC Endpoint
ncacn_np:\\\\DC2[\\pipe\\eventlog]

UUID: 3c4728c5-f0ab-448b-bda1-6ce01eb0a6d6 DHCPv6 Client LRPC Endpoint
ncacn_ip_tcp:192.168.1.2[49153]

UUID: 3c4728c5-f0ab-448b-bda1-6ce01eb0a6d6 DHCPv6 Client LRPC Endpoint
ncalrpc:[LRPC-78d564bf393b9716a5]

UUID: 3c4728c5-f0ab-448b-bda1-6ce01eb0a6d6 DHCPv6 Client LRPC Endpoint
ncalrpc:[dhcpcsvc]

UUID: 3c4728c5-f0ab-448b-bda1-6ce01eb0a6d6 DHCPv6 Client LRPC Endpoint
ncalrpc:[dhcpcsvc6]

UUID: 4bec6bb8-b5c2-4b6f-b2c1-5da5cf92d0d9
ncalrpc:[umpo]

UUID: 4bec6bb8-b5c2-4b6f-b2c1-5da5cf92d0d9
ncalrpc:[actkernel]

UUID: 085b0334-e454-4d91-9b8c-4134f9e793f3
ncalrpc:[umpo]

UUID: 085b0334-e454-4d91-9b8c-4134f9e793f3
ncalrpc:[actkernel]

UUID: 8782d3b9-ebbd-4644-a3d8-e8725381919b
ncalrpc:[umpo]

UUID: 8782d3b9-ebbd-4644-a3d8-e8725381919b
ncalrpc:[actkernel]

UUID: 3b338d89-6cfa-44b8-847e-531531bc9992
ncalrpc:[umpo]

UUID: 3b338d89-6cfa-44b8-847e-531531bc9992
ncalrpc:[actkernel]

UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncalrpc:[umpo]

UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncalrpc:[actkernel]

UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncalrpc:[LRPC-5e4b119e2215d21906]

UUID: 2d98a740-581d-41b9-aa0d-a88b9d5ce938
ncalrpc:[umpo]

UUID: 2d98a740-581d-41b9-aa0d-a88b9d5ce938
ncalrpc:[actkernel]

UUID: 2d98a740-581d-41b9-aa0d-a88b9d5ce938
ncalrpc:[LRPC-5e4b119e2215d21906]

UUID: 2d98a740-581d-41b9-aa0d-a88b9d5ce938
ncalrpc:[LSMApi]

UUID: 2d98a740-581d-41b9-aa0d-a88b9d5ce938
ncacn_np:\\\\DC2[\\pipe\\LSM_API_service]

UUID: 8bfc3be1-6def-4e2d-af74-7c47cd0ade4a
ncalrpc:[umpo]

UUID: 8bfc3be1-6def-4e2d-af74-7c47cd0ade4a
ncalrpc:[actkernel]

UUID: 8bfc3be1-6def-4e2d-af74-7c47cd0ade4a
ncalrpc:[LRPC-5e4b119e2215d21906]

UUID: 8bfc3be1-6def-4e2d-af74-7c47cd0ade4a
ncalrpc:[LSMApi]

UUID: 8bfc3be1-6def-4e2d-af74-7c47cd0ade4a
ncacn_np:\\\\DC2[\\pipe\\LSM_API_service]

UUID: 1b37ca91-76b1-4f5e-a3c7-2abfc61f2bb0
ncalrpc:[umpo]

UUID: 1b37ca91-76b1-4f5e-a3c7-2abfc61f2bb0
ncalrpc:[actkernel]

UUID: 1b37ca91-76b1-4f5e-a3c7-2abfc61f2bb0
ncalrpc:[LRPC-5e4b119e2215d21906]

UUID: 1b37ca91-76b1-4f5e-a3c7-2abfc61f2bb0
ncalrpc:[LSMApi]

UUID: 1b37ca91-76b1-4f5e-a3c7-2abfc61f2bb0
ncacn_np:\\\\DC2[\\pipe\\LSM_API_service]

UUID: c605f9fb-f0a3-4e2a-a073-73560f8d9e3e
ncalrpc:[umpo]

UUID: c605f9fb-f0a3-4e2a-a073-73560f8d9e3e
ncalrpc:[actkernel]

UUID: c605f9fb-f0a3-4e2a-a073-73560f8d9e3e
ncalrpc:[LRPC-5e4b119e2215d21906]

UUID: c605f9fb-f0a3-4e2a-a073-73560f8d9e3e
ncalrpc:[LSMApi]

UUID: c605f9fb-f0a3-4e2a-a073-73560f8d9e3e
ncacn_np:\\\\DC2[\\pipe\\LSM_API_service]

UUID: 0d3e2735-cea0-4ecc-a9e2-41a2d81aed4e
ncalrpc:[umpo]

UUID: 0d3e2735-cea0-4ecc-a9e2-41a2d81aed4e
ncalrpc:[actkernel]

UUID: 0d3e2735-cea0-4ecc-a9e2-41a2d81aed4e
ncalrpc:[LRPC-5e4b119e2215d21906]

UUID: 0d3e2735-cea0-4ecc-a9e2-41a2d81aed4e
ncalrpc:[LSMApi]

UUID: 0d3e2735-cea0-4ecc-a9e2-41a2d81aed4e
ncacn_np:\\\\DC2[\\pipe\\LSM_API_service]

UUID: 76f226c3-ec14-4325-8a99-6a46348418af
ncalrpc:[WMsgKRpc04A550]

UUID: 76f226c3-ec14-4325-8a99-6a46348418af
ncacn_np:\\\\DC2[\\PIPE\\InitShutdown]

UUID: 76f226c3-ec14-4325-8a99-6a46348418af
ncalrpc:[WindowsShutdown]

UUID: d95afe70-a6d5-4259-822e-2c84da1ddb0d
ncalrpc:[WMsgKRpc04A550]

UUID: d95afe70-a6d5-4259-822e-2c84da1ddb0d
ncacn_np:\\\\DC2[\\PIPE\\InitShutdown]

UUID: d95afe70-a6d5-4259-822e-2c84da1ddb0d
ncalrpc:[WindowsShutdown]

Total endpoints found: 317



==== End of RPC Endpoint Mapper query response ====
portqry.exe -n 192.168.1.2 -e 135 -p TCP exits with return code 0x00000000.
=============================================

 Starting portqry.exe -n 192.168.1.2 -e 389 -p BOTH ...


Querying target system called:

 192.168.1.2

Attempting to resolve IP address to a name...


IP address resolved to DC2.ABC.COM

querying...

TCP port 389 (ldap service): FILTERED

UDP port 389 (unknown service): LISTENING or FILTERED

Using ephemeral source port
Sending LDAP query to UDP port 389...

LDAP query to port 389 failed
Server did not respond to LDAP query

portqry.exe -n 192.168.1.2 -e 389 -p BOTH exits with return code 0x00000001.
=============================================

 Starting portqry.exe -n 192.168.1.2 -e 636 -p TCP ...


Querying target system called:

 192.168.1.2

Attempting to resolve IP address to a name...


IP address resolved to DC2.ABC.COM

querying...

TCP port 636 (ldaps service): FILTERED
portqry.exe -n 192

this two DC's are on the same network? or one of them is on a remote site?

The virtual machine is residing on another physical server?

virtual machine is running hyper-v, vmware or what?

Hi Paul

Info from DC2:

C:\>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : DC2
   Primary Dns Suffix  . . . . . . . : ABC.COM
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : ABC.COM

Ethernet adapter Ethernet:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft Hyper-V Network Adapter
   Physical Address. . . . . . . . . : 00-15-5D-01-C8-00
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::a911:c56a:a958:77e5%12(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.1.2(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.1.100
   DHCPv6 IAID . . . . . . . . . . . : 251663709
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-19-CB-04-C0-00-15-5D-01-C8-00

   DNS Servers . . . . . . . . . . . : ::1
                                       192.168.1.1
                                       192.168.1.2
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{E3013F70-29BF-44C0-A913-CF3C735A71C4}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes


C:\>nslookup
Default Server:  UnKnown
Address:  ::1

Hi Paul

Info from DC2:

=============================================

 Starting portqry.exe -n 192.168.1.1 -e 135 -p TCP ...


Querying target system called:

 192.168.1.1

Attempting to resolve IP address to a name...


IP address resolved to DC1.ABC.COM

querying...

TCP port 135 (epmap service): LISTENING

Using ephemeral source port
Querying Endpoint Mapper Database...
Server's response:

UUID: 3473dd4d-2e88-4006-9cba-22570909dd10 WinHttp Auto-Proxy Service
ncacn_np:192.168.1.1[\\PIPE\\W32TIME_ALT]

UUID: 2f5f6521-cb55-1059-b446-00df0bce31db Unimodem LRPC Endpoint
ncacn_np:192.168.1.1[\\pipe\\tapsrv]

UUID: 6bffd098-a112-3610-9833-46c3f874532d
ncacn_ip_tcp:192.168.1.1[1085]

UUID: 5b821720-f63b-11d0-aad2-00c04fc324db
ncacn_ip_tcp:192.168.1.1[1085]

UUID: 50abc2a4-574d-40b3-9d66-ee4fd5fba076
ncacn_ip_tcp:192.168.1.1[1082]

UUID: 3d267954-eeb7-11d1-b94e-00c04fa3080d
ncacn_np:192.168.1.1[\\pipe\\HydraLsPipe]

UUID: 3d267954-eeb7-11d1-b94e-00c04fa3080d
ncacn_ip_tcp:192.168.1.1[1052]

UUID: 12d4b7c8-77d5-11d1-8c24-00c04fa3080d
ncacn_np:192.168.1.1[\\pipe\\HydraLsPipe]

UUID: 12d4b7c8-77d5-11d1-8c24-00c04fa3080d
ncacn_ip_tcp:192.168.1.1[1052]

UUID: 493c451c-155c-11d3-a314-00c04fb16103
ncacn_np:192.168.1.1[\\pipe\\HydraLsPipe]

UUID: 493c451c-155c-11d3-a314-00c04fb16103
ncacn_ip_tcp:192.168.1.1[1052]

UUID: f5cc59b4-4264-101a-8c59-08002b2f8426 NtFrs Service
ncacn_ip_tcp:192.168.1.1[1039]

UUID: d049b186-814f-11d1-9a3c-00c04fc9b232 NtFrs API
ncacn_ip_tcp:192.168.1.1[1039]

UUID: a00c021c-2be2-11d2-b678-0000f87a8f8e PERFMON SERVICE
ncacn_ip_tcp:192.168.1.1[1039]

UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncacn_np:192.168.1.1[\\PIPE\\lsass]

UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncacn_np:192.168.1.1[\\PIPE\\protected_storage]

UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncacn_ip_tcp:192.168.1.1[1026]

UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncacn_http:192.168.1.1[1027]

UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncacn_np:192.168.1.1[\\PIPE\\lsass]

UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncacn_np:192.168.1.1[\\PIPE\\protected_storage]

UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncacn_ip_tcp:192.168.1.1[1026]

UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncacn_http:192.168.1.1[1027]

UUID: 12345778-1234-abcd-ef00-0123456789ab
ncacn_np:192.168.1.1[\\PIPE\\lsass]

UUID: 12345778-1234-abcd-ef00-0123456789ab
ncacn_np:192.168.1.1[\\PIPE\\protected_storage]

UUID: 12345778-1234-abcd-ef00-0123456789ab
ncacn_ip_tcp:192.168.1.1[1026]

UUID: 12345778-1234-abcd-ef00-0123456789ab
ncacn_http:192.168.1.1[1027]

UUID: 12345778-1234-abcd-ef00-0123456789ac
ncacn_np:192.168.1.1[\\PIPE\\lsass]

UUID: 12345778-1234-abcd-ef00-0123456789ac
ncacn_np:192.168.1.1[\\PIPE\\protected_storage]

UUID: 12345778-1234-abcd-ef00-0123456789ac
ncacn_ip_tcp:192.168.1.1[1026]

UUID: 12345778-1234-abcd-ef00-0123456789ac
ncacn_http:192.168.1.1[1027]

UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
ncacn_np:192.168.1.1[\\PIPE\\lsass]

UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
ncacn_np:192.168.1.1[\\PIPE\\protected_storage]

UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
ncacn_ip_tcp:192.168.1.1[1026]

UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
ncacn_http:192.168.1.1[1027]

UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
ncacn_np:192.168.1.1[\\PIPE\\lsass]

UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
ncacn_np:192.168.1.1[\\PIPE\\protected_storage]

UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
ncacn_ip_tcp:192.168.1.1[1026]

UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
ncacn_http:192.168.1.1[1027]

UUID: 12345678-1234-abcd-ef00-01234567cffb
ncacn_np:192.168.1.1[\\PIPE\\lsass]

UUID: 12345678-1234-abcd-ef00-01234567cffb
ncacn_np:192.168.1.1[\\PIPE\\protected_storage]

UUID: 12345678-1234-abcd-ef00-01234567cffb
ncacn_ip_tcp:192.168.1.1[1026]

UUID: 12345678-1234-abcd-ef00-01234567cffb
ncacn_http:192.168.1.1[1027]

UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
ncacn_np:192.168.1.1[\\PIPE\\lsass]

UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
ncacn_np:192.168.1.1[\\PIPE\\protected_storage]

UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
ncacn_ip_tcp:192.168.1.1[1026]

UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
ncacn_http:192.168.1.1[1027]

UUID: 1ff70682-0a51-30e8-076d-740be8cee98b
ncacn_np:192.168.1.1[\\PIPE\\atsvc]

UUID: 378e52b0-c0a9-11cf-822d-00aa0051e40f
ncacn_np:192.168.1.1[\\PIPE\\atsvc]

UUID: 0a74ef1c-41a4-4e06-83ae-dc74fb1cdd53
ncacn_np:192.168.1.1[\\PIPE\\atsvc]

UUID: d674a233-5829-49dd-90f0-60cf9ceb7129 ICF+ FW API
ncacn_np:192.168.1.1[\\PIPE\\atsvc]

UUID: d674a233-5829-49dd-90f0-60cf9ceb7129 ICF+ FW API
ncacn_np:192.168.1.1[\\PIPE\\wkssvc]

UUID: d674a233-5829-49dd-90f0-60cf9ceb7129 ICF+ FW API
ncacn_np:192.168.1.1[\\PIPE\\srvsvc]

UUID: d674a233-5829-49dd-90f0-60cf9ceb7129 ICF+ FW API
ncacn_np:192.168.1.1[\\pipe\\keysvc]

Total endpoints found: 53



==== End of RPC Endpoint Mapper query response ====
portqry.exe -n 192.168.1.1 -e 135 -p TCP exits with return code 0x00000000.
=============================================

 Starting portqry.exe -n 192.168.1.1 -e 389 -p BOTH ...


Querying target system called:

 192.168.1.1

Attempting to resolve IP address to a name...


IP address resolved to DC1.ABC.COM

querying...

TCP port 389 (ldap service): LISTENING

Using ephemeral source port
Sending LDAP query to TCP port 389...

LDAP query response:


currentdate: 05/23/2014 03:17:51 (unadjusted GMT)
subschemaSubentry: CN=Aggregate,CN=Schema,CN=Configuration,DC=ABC,DC=COM
dsServiceName: CN=NTDS Settings,CN=DC1,CN=Servers,CN=Default-First-Site,CN=Sites,CN=Configuration,DC=ABC,DC=COM
namingContexts: DC=ABC,DC=COM
defaultNamingContext: DC=ABC,DC=COM
schemaNamingContext: CN=Schema,CN=Configuration,DC=ABC,DC=COM
configurationNamingContext: CN=Configuration,DC=ABC,DC=COM
rootDomainNamingContext: DC=ABC,DC=COM
supportedControl: 1.2.840.113556.1.4.319
supportedLDAPVersion: 3
supportedLDAPPolicies: MaxPoolThreads
highestCommittedUSN: 4425076
supportedSASLMechanisms: GSSAPI
dnsHostName: DC1.ABC.COM
ldapServiceName: ABC.COM:DC1$@ABC.COM
serverName: CN=DC1,CN=Servers,CN=Default-First-Site,CN=Sites,CN=Configuration,DC=ABC,DC=COM
supportedCapabilities: 1.2.840.113556.1.4.800
isSynchronized: TRUE
isGlobalCatalogReady: TRUE
domainFunctionality: 2
forestFunctionality: 2
domainControllerFunctionality: 2


======== End of LDAP query response ========

UDP port 389 (unknown service): LISTENING or FILTERED

Using ephemeral source port
Sending LDAP query to UDP port 389...

LDAP query response:


currentdate: 05/23/2014 03:17:55 (unadjusted GMT)
subschemaSubentry: CN=Aggregate,CN=Schema,CN=Configuration,DC=ABC,DC=COM
dsServiceName: CN=NTDS Settings,CN=DC1,CN=Servers,CN=Default-First-Site,CN=Sites,CN=Configuration,DC=ABC,DC=COM
namingContexts: DC=ABC,DC=COM
defaultNamingContext: DC=ABC,DC=COM
schemaNamingContext: CN=Schema,CN=Configuration,DC=ABC,DC=COM
configurationNamingContext: CN=Configuration,DC=ABC,DC=COM
rootDomainNamingContext: DC=ABC,DC=COM
supportedControl: 1.2.840.113556.1.4.319
supportedLDAPVersion: 3
supportedLDAPPolicies: MaxPoolThreads
highestCommittedUSN: 4425076
supportedSASLMechanisms: GSSAPI
dnsHostName: DC1.ABC.COM
ldapServiceName: ABC.COM:DC1$@ABC.COM
serverName: CN=DC1,CN=Servers,CN=Default-First-Site,CN=Sites,CN=Configuration,DC=ABC,DC=COM
supportedCapabilities: 1.2.840.113556.1.4.800
isSynchronized: TRUE
isGlobalCatalogReady: TRUE
domainFunctionality: 2
forestFunctionality: 2
domainControllerFunctionality: 2


======== End of LDAP query response ========

UDP port 389 is LISTENING

portqry.exe -n 192.168.1.1 -e 389 -p BOTH exits with return code 0x00000000.
=============================================

 Starting portqry.exe -n 192.168.1.1 -e 636 -p TCP ...


Querying target system called:

 192.168.1.1

Attempting to resolve IP address to a name...


IP address resolved to DC1.ABC.COM

querying...

TCP port 636 (ldaps service): LISTENING
portqry.exe -n 192.168.1.1 -e 636 -p TCP exits with return code 0x00000000.
=============================================

 Starting portqry.exe -n 192.168.1.1 -e 3268 -p TCP ...


Querying target system called:

 192.168.1.1

Attempting to resolve IP address to a name...


IP address resolved to DC1.ABC.COM

querying...

TCP port 3268 (msft-gc service): LISTENING

Using ephemeral source port
Sending LDAP query to TCP port 3268...

LDAP query response:


currentdate: 05/23/2014 03:17:55 (unadjusted GMT)
subschemaSubentry: CN=Aggregate,CN=Schema,CN=Configuration,DC=ABC,DC=COM
dsServiceName: CN=NTDS Settings,CN=DC1,CN=Servers,CN=Default-First-Site,CN=Sites,CN=Configuration,DC=ABC,DC=COM
namingContexts: DC=ABC,DC=COM
defaultNamingContext: DC=ABC,DC=COM
schemaNamingContext: CN=Schema,CN=Configuration,DC=ABC,DC=COM
configurationNamingContext: CN=Configuration,DC=ABC,DC=COM
rootDomainNamingContext: DC=ABC,DC=COM
supportedControl: 1.2.840.113556.1.4.319
supportedLDAPVersion: 3
supportedLDAPPolicies: MaxPoolThreads
highestCommittedUSN: 4425076
supportedSASLMechanisms: GSSAPI
dnsHostName: DC1.ABC.COM
ldapServiceName: ABC.COM:DC1$@ABC.COM
serverName: CN=DC1,CN=Servers,CN=Default-First-Site,CN=Sites,CN=Configuration,DC=ABC,DC=COM
supportedCapabilities: 1.2.840.113556.1.4.800
isSynchronized: TRUE
isGlobalCatalogReady: TRUE
domainFunctionality: 2
forestFunctionality: 2
domainControllerFunctionality: 2


======== End of LDAP query response ========
portqry.exe -n 192.168.1.1 -e 3268 -p TCP exits with return code 0x00000000.
=============================================

 Starting portqry.exe -n 192.168.1.1 -e 3269 -p TCP ...


Querying target system called:

 192.168.1.1

Attempting to resolve IP address to a name...


IP address resolved to DC1.ABC.COM

querying...

TCP port 3269 (msft-gc-ssl service): LISTENING
portqry.exe -n 192.168.1.1 -e 3269 -p TCP exits with return code 0x00000000.
=============================================

 Starting portqry.exe -n 192.168.1.1 -e 53 -p BOTH ...


Querying target system called:

 192.168.1.1

Attempting to resolve IP address to a name...


IP address resolved to DC1.ABC.COM

querying...

TCP port 53 (domain service): LISTENING

UDP port 53 (domain service): LISTENING
portqry.exe -n 192.168.1.1 -e 53 -p BOTH exits with return code 0x00000000.
=============================================

 Starting portqry.exe -n 192.168.1.1 -e 88 -p BOTH ...


Querying target system called:

 192.168.1.1

Attempting to resolve IP address to a name...


IP address resolved to DC1.ABC.COM

querying...

TCP port 88 (kerberos service): LISTENING

UDP port 88 (kerberos service): LISTENING or FILTERED
portqry.exe -n 192.168.1.1 -e 88 -p BOTH exits with return code 0x00000002.
=============================================

 Starting portqry.exe -n 192.168.1.1 -e 445 -p TCP ...


Querying target system called:

 192.168.1.1

Attempting to resolve IP address to a name...


IP address resolved to DC1.ABC.COM

querying...

TCP port 445 (microsoft-ds service): LISTENING
portqry.exe -n 192.168.1.1 -e 445 -p TCP exits with return code 0x00000000.
=============================================

 Starting portqry.exe -n 192.168.1.1 -e 137 -p UDP ...


Querying target system called:

 192.168.1.1

Attempting to resolve IP address to a name...


IP address resolved to DC1.ABC.COM

querying...

UDP port 137 (netbios-ns service): LISTENING or FILTERED

Using ephemeral source port
Attempting NETBIOS adapter status query to UDP port 137...

Server's response: MAC address 001a640ac04e
UDP port: LISTENING
portqry.exe -n 192.168.1.1 -e 137 -p UDP exits with return code 0x00000000.
=============================================

 Starting portqry.exe -n 192.168.1.1 -e 138 -p UDP ...


Querying target system called:

 192.168.1.1

Attempting to resolve IP address to a name...


IP address resolved to DC1.ABC.COM

querying...

UDP port 138 (netbios-dgm service): LISTENING or FILTERED
portqry.exe -n 192.168.1.1 -e 138 -p UDP exits with return code 0x00000002.
=============================================

 Starting portqry.exe -n 192.168.1.1 -e 139 -p TCP ...


Querying target system called:

 192.168.1.1

Attempting to resolve IP address to a name...


IP address resolved to DC1.ABC.COM

querying...

TCP port 139 (netbios-ssn service): LISTENING
portqry.exe -n 192.168.1.1 -e 139 -p TCP exits with return code 0x00000000.
=============================================

 Starting portqry.exe -n 192.168.1.1 -e 42 -p TCP ...


Querying target system called:

 192.168.1.1

Attempting to resolve IP address to a name...


IP address resolved to DC1.ABC.COM

querying...

TCP port 42 (nameserver service): FILTERED
portqry.exe -n 192.168.1.1 -e 42 -p TCP exits with return code 0x00000002.

Hi cguan

Two DC are on the same network.

DC2 (VM) is residing on anther physical server, using Hyper-V.

Hi Norman,

Do you have any progress by now?

I suggest you point to the physical Domain Controller (192.168.1.1) as preferred DNS server on both DCs, and please use real IP address instead of loopback address.

More information for you:

Best practices for DNS client settings in Windows 2000 Server and in Windows Server 2003

http://support.microsoft.com/kb/825036/en-us

The loopback IP address should not be the first server in the list???

http://social.technet.microsoft.com/Forums/windowsserver/en-US/dd139193-7007-4b58-9ce5-adc26cadf121/the-loopback-ip-address-should-not-be-the-first-server-in-the-list?forum=winserverDS

Troubleshooting AD Replication error 1753: There are no more endpoints available from the endpoint mapper

http://support.microsoft.com/kb/2089874/ar

Best Regards,

Amy

Hi Amy

Loopback ip address is 127.0.0.1, is it? i not using loopback ip.

I will set both DC to use 192.168.1.1 as Preferred DNS Server.

May i know the best way to trigger manual replication?

Hi,

You can use Sites and Services to initiate replication. And you can also use the "repadmin /syncall" command.

Here's a step by step:

http://technet.microsoft.com/en-us/library/cc816926(v=ws.10).aspx

Thats for 2008, but I believe that should work on the Windows 2003 server as well.

On the 2012 domain controller, the easiest path might be entering "sites.msc" in the run box.

In addition to what was already mentioned,

1. restart the netlogon service on the domain controllers (that should register or re-register the SRV records)

Hi All

Sorry for the delay.

In Active Directory Sites and Services, right-click on DC1's NTDS Settings, selects "Replicate configuration to the selected DC"

Error message:
"The following error occurred during the attempt to synchronize naming content CN=Configuration,DC=ABC,DC=COM from Domain Controller DC2 to Domain Controller DC1:
There are no more endpoints available from the endpoint mapper.

This operation will not continue."

Any suggestion?

Hi All
C:\>nslookup abc.com
Server: dc1.abc.com
Address:  192.168.1.1

Name:    abc.com
Addresses:  192.168.1.1
                    192.168.1.2


C:\>nslookup abc.com dc1
Server:  dc1.abc.com
Address:  192.168.1.1

Name:    abc.com
Addresses:  192.168.1.188
                    192.168.1.201


C:\>nslookup abc.com dc2
DNS request timed out.
    timeout was 2 seconds.
Server:  UnKnown
Address:  192.168.1.2

DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** Request to UnKnown timed-out

i have no problem with DC1; but i have problem with DC2.

check out this thread:

http://social.technet.microsoft.com/Forums/windowsserver/en-US/6d038165-e6ec-4683-8da1-5a4fecdd288b/ports-required-to-replicate-dcs

from thread above:

• UDP Port 88 for Kerberos authentication
• UDP and TCP Port 135 for domain controllers-to-domain controller and client to domain controller operations.
• TCP Port 139 and UDP 138 for File Replication Service between domain controllers.
• UDP Port 389 for LDAP to handle normal queries from client computers to the domain controllers.
• TCP and UDP Port 445 for File Replication Service
• TCP and UDP Port 464 for Kerberos Password Change
• TCP Port 3268 and 3269 for Global Catalog from client to domain controller.
• TCP and UDP Port 53 for DNS from client to domain controller and domain controller to domain controller.

please download portqry, and try to query those ports needed for replication make sure it's listening and not being block by the firewall or any anti virus software.

Hi cguan

i have checked DC2 (Virtual Machine) - 192.168.1.2:

UDP port 88 (kerberos service): LISTENING or FILTERED
UDP port 135 (epmap service): NOT LISTENING
UDP port 138 (netbios-dgm service): LISTENING or FILTERED
UDP port 445 (microsoft-ds service): NOT LISTENING
UDP port 464 (kpasswd service): LISTENING or FILTERED
UDP port 53 (domain service): LISTENING
portqry.exe -n 192.168.1.2 -e 88,135,138,445,464,53 -p UDP exits with return code 0x00000000.

TCP port 138 (unknown service): NOT LISTENING
TCP port 445 (microsoft-ds service): LISTENING
TCP port 464 (kpasswd service): LISTENING
TCP port 53 (domain service): LISTENING
portqry.exe -n 192.168.1.2 -e 88,135,138,445,464,53 -p TCP exits with return code 0x00000000.

I didn't install Antivirus yet.
I have also checked the firewall for ports that are "NOT LISTENING" , they are allowed in firewall.
How to make them "LISTENING"?

DC1(Physical Server) - 192.168.1.1:

UDP port 88 (kerberos service): LISTENING or FILTERED
UDP port 135 (epmap service): NOT LISTENING
UDP port 389 is LISTENING
UDP port 445 (microsoft-ds service): LISTENING or FILTERED
UDP port 464 (kpasswd service): LISTENING or FILTERED
UDP port 53 (domain service): LISTENING
portqry.exe -n 192.168.1.1 -e 88,135,138,389,445,464,53 -p UDP exits with return code 0x00000000.

TCP port 135 (epmap service): LISTENING
TCP port 139 (netbios-ssn service): LISTENING
TCP port 445 (microsoft-ds service): LISTENING
TCP port 464 (kpasswd service): LISTENING
TCP port 3268 (msft-gc service): LISTENING
TCP port 3269 (msft-gc-ssl service): LISTENING
TCP port 53 (domain service): LISTENING
portqry.exe -n 192.168.1.1 -e 135,139,445,464,3268,3269,53 -p TCP exits with return code 0x00000000.

From your output the specified ports that are needed for replication is being filtered or not listening.

you need to check why it's being filtered.

I had checked on my environment, these ports below are listening on all my DC's.

 88,135,139,138,445,464,3268,3269,53 

You need to check on your side, why those ports are blocked.

If one of them, is block or filtered. Then you will not be able to replicate successfully.

I don't know your physical network infrastructure, software installed on your PC. So you need to do something on your part on why those ports are being blocked.

Good luck!!!

anything special on your network?

Like IPSec,  to block ports? or VLANs?

Hi cguan

I dont have IPSec or VLAN.

Hi cguan

I dont have IPSec or VLAN.

type: netstat -ano on your two DC's check also if those ports needed for replication are listening or not.

or check out this link:

AD Replication Status Tool is Live

http://blogs.technet.com/b/askds/archive/2012/08/23/ad-replication-status-tool-is-live.aspx

it might help with more details on your issue.

after running netstat -ano and the ports needed for replication is filtered.

type this command:

netstat -a -b to check which services are using on those ports

or download TCPView from Sysinternal

http://technet.microsoft.com/en-us/sysinternals/bb897437.aspx

Hi cguan

Port 88,135,139,138,445,464,3268,3269,53 - both UDP & TCP ports are listening?

Both servers' firewall are off.