none
Replication between Windows server 2003 R2 and Windows Server 2008 R2_x64

    Question

  •  

    I'm trying to replicate a Windows 2003 R2 with a Windows 2008 R2_x64 and I’m receiving the fallowing error:

    The DFS Replication service encountered an error communicating with partner server01 for replication group defz-path\personal.

     

    Partner DNS address: server01.domain

     

    Optional data if available:

    Partner WINS Address: server01

    Partner IP Address: 10.160.20.19

     

    The service will retry the connection periodically.

     

    Additional Information:

    Error: 1753 (There are no more endpoints available from the endpoint mapper.)

    Connection ID: BFBDC702-72DA-4A56-A670-5CA5ADADE814

    Replication Group ID: 6D304D07-0294-4D93-B79B-CAA5EDF6847C

    There is not firewall between these servers, there just next to each other, and active directory replication is working fine, connectivity to DC is fine.

     

    Monday, October 04, 2010 1:38 PM

Answers

  • Hi Luis,

    On Windows Server 2008 R2, your firewall rules should reflect any installed roles on the computer.  If you suspect a configuration problem there, you'll want to try opening up the firewall rules to allow RPC traffic to any endpoint, to see if it makes a difference.  You can do this by going into control panel and manually modifying the firewall settings.

    If you've tried this alread and the issue still occurs, it's entirely possible that the problem may be on the network in between the two servers.  One of the really important, but often overlooked details is that Windows Server 2008 R2 uses a different dynamic port range than Windows Server 2003.  If you have a device in between the two servers that is running any sort of basic port filtering, this can screw up communicaton between them.  For more information see this KB article:

    929851 The default dynamic port range for TCP/IP has changed in Windows Vista and in Windows Server 2008
    http://support.microsoft.com/default.aspx?scid=kb;EN-US;929851

    I'd recommend taking a simultaneous network capture while duplicating the failure, and reviewing that to see if any connections are not completing successfully.


    David Beach - Microsoft Online Community Support
    • Marked as answer by Tiger Li Thursday, November 04, 2010 3:06 AM
    Monday, October 18, 2010 5:20 PM

All replies

  • Have a look to this Microsoft article .

    Section: How to resolve RPC Endpoint Mapper Errors

     

     


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
    Monday, October 04, 2010 1:51 PM
  • No luck, every thin looks fine. Other replications to other sites are working fine, it is just this one between windos 2003 R2and Winodws 2008 R2_x64.

    Do I need to do something diferent if I’m replicating 2003 r2 to a 2008 r2?

    Monday, October 04, 2010 2:21 PM
  • Make sure you can ping between the DC's with ip address, computername and FQDN. Also make sure that you use only domain internal ip addresses on the NIC settings, no externals like your ISP's DNS server. Then run repadmin /showrepl and dcdiag /v and post the output here.

     


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
    Monday, October 04, 2010 3:36 PM
  • Hi Luis67,

     

    Thanks for posting here.

     

    You need to prepare the domain first If the domain controller that you plan to add into the domain is the first runs Windows Server 2008 or Windows Server 2008 R2.

    For more information please take look the link below:

     

    Installing an Additional Domain Controller

    http://technet.microsoft.com/en-us/library/cc733027(WS.10).aspx

     

    Thanks.

     

    Tiger Li


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Tuesday, October 05, 2010 4:52 AM
  • The domain schema has been updated to Windows 2003 R2 and Windows 2008 R2, and the issues the I have is with DFS replication between a Windows 2003 r2 and a Windows 2008 Enterprise R2 _x64, I'm not adding a domain controller.

    The error the I'm receiving is "There are no more endpoints available from the endpoint mapper", and I think it is related with the RPC endpointmapper service in W2k8. Because of firewalls between others sites we restrict RPC ports from 29200 to 29700, (There is not firewalls between the servers in question).

     

    Wednesday, October 06, 2010 7:29 PM
  • I can ping the domain controller and I can ping between file servers, as i explain at the beguining, this servers are in the same network.

    The domain schema has been updated to Windows 2003 R2 and Windows 2008 R2, and the issues the I have is with DFS replication between a Windows 2003 r2 and a Windows 2008 Enterprise R2 _x64, I'm not adding a domain controller.

    The error the I'm receiving is "There are no more endpoints available from the endpoint mapper", and I think it is related with the RPC endpointmapper service in W2k8. Because of firewalls between others sites we restrict RPC ports from 29200 to 29700, (There is not firewalls between the servers in question).

    dcdiag /v output

    C:\Windows\system32>dcdiag /s:usmiadc01 /v

    Directory Server Diagnosis

    Performing initial setup:
       * Connecting to directory service on server usmiadc01.
       * Identified AD Forest.
       Collecting AD specific global data
       * Collecting site info.
       Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=xxx,DC=corp,LD
    AP_SCOPE_SUBTREE,(objectCategory=ntDSSiteSettings),.......
       The previous call succeeded

    Repadmin: running command /showrepl against full DC usmiadc01.efgz.efg.corp
    USMIA701\USMIADC01
    DSA Options: (none)
    Site Options: W2K3_BRIDGES_REQUIRED
    DSA object GUID: f4642aba-6c11-4a8b-98fc-c175ab9e97b7
    DSA invocationID: abaa627d-1a2b-467a-8ef9-6bd739130d7e

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

    CN=Configuration,DC=efg,DC=corp
        USMIA701\USMIADC02 via RPC
            DSA object GUID: 3b75bce7-8496-4e5b-8334-a5e1cb8af57e
            Last attempt @ 2010-10-06 15:45:20 was successful.

    CN=Schema,CN=Configuration,DC=efg,DC=corp
        USMIA701\USMIADC02 via RPC
            DSA object GUID: 3b75bce7-8496-4e5b-8334-a5e1cb8af57e
            Last attempt @ 2010-10-06 15:45:10 was successful.

    DC=efgz,DC=efg,DC=corp
        USMIA701\USMIADC02 via RPC
            DSA object GUID: 3b75bce7-8496-4e5b-8334-a5e1cb8af57e
            Last attempt @ 2010-10-06 15:48:10 was successful.

    DC=ForestDnsZones,DC=efg,DC=corp
        USMIA701\USMIADC02 via RPC
            DSA object GUID: 3b75bce7-8496-4e5b-8334-a5e1cb8af57e
            Last attempt @ 2010-10-06 15:45:10 was successful.

    DC=DomainDnsZones,DC=efgz,DC=efg,DC=corp
        USMIA701\USMIADC02 via RPC
            DSA object GUID: 3b75bce7-8496-4e5b-8334-a5e1cb8af57e
            Last attempt @ 2010-10-06 15:45:26 was successful.
      

    Thanks for your help,

    Wednesday, October 06, 2010 7:51 PM
  • Hi Luis67,

    Could you perform "rpcdump /s /i>rpcdump.txt " to dump the replication status on server and post here for further investigation .

    You can get this utitlity from the link below:

     
    Is this issue still occurs frequently?
     
    What if temporarily disable the RPC port restriction on firewall ? 
     
    Thanks.
     
    Tiger Li

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Thursday, October 07, 2010 8:14 AM
  • Querying Endpoint Mapper Database...

    162 registered endpoints found.


    Collecting Data....  This may take a while.

              0    10   20   30   40   50   60   70   80   90  100
              |----|----|----|----|----|----|----|----|----|----|
              ...................................................

     

    ncacn_np(Connection-oriented named pipes)

      USMIABFILP01[\PIPE\InitShutdown] [d95afe70-a6d5-4259-822e-2c84da1ddb0d]  :YES

      USMIABFILP01[\PIPE\InitShutdown] [76f226c3-ec14-4325-8a99-6a46348418af]  :YES

      USMIABFILP01[\pipe\eventlog] [3c4728c5-f0ab-448b-bda1-6ce01eb0a6d5] DHCP Client LRPC Endpoint :NO

      USMIABFILP01[\pipe\eventlog] [3c4728c5-f0ab-448b-bda1-6ce01eb0a6d6] DHCPv6 Client LRPC Endpoint :NO

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

      USMIABFILP01[\pipe\eventlog] [f6beaff7-1e19-4fbb-9f8f-b89e2018337c] Event log TCPIP :NO

      USMIABFILP01[\PIPE\browser] [58e604e8-9adb-4d2e-a464-3b0683fb1480] AppInfo :YES

      USMIABFILP01[\PIPE\srvsvc] [58e604e8-9adb-4d2e-a464-3b0683fb1480] AppInfo :YES

      USMIABFILP01[\PIPE\atsvc] [58e604e8-9adb-4d2e-a464-3b0683fb1480] AppInfo :YES

      USMIABFILP01[\PIPE\browser] [fd7a0523-dc70-43dd-9b2e-9c5ed48225b1] AppInfo :YES

      USMIABFILP01[\PIPE\srvsvc] [fd7a0523-dc70-43dd-9b2e-9c5ed48225b1] AppInfo :YES

      USMIABFILP01[\PIPE\atsvc] [fd7a0523-dc70-43dd-9b2e-9c5ed48225b1] AppInfo :YES

      USMIABFILP01[\PIPE\browser] [5f54ce7d-5b79-4175-8584-cb65313a0e98] AppInfo :YES

      USMIABFILP01[\PIPE\srvsvc] [5f54ce7d-5b79-4175-8584-cb65313a0e98] AppInfo :YES

      USMIABFILP01[\PIPE\atsvc] [5f54ce7d-5b79-4175-8584-cb65313a0e98] AppInfo :YES

      USMIABFILP01[\PIPE\browser] [201ef99a-7fa0-444c-9399-19ba84f12a1a] AppInfo :YES

      USMIABFILP01[\PIPE\srvsvc] [201ef99a-7fa0-444c-9399-19ba84f12a1a] AppInfo :YES

      USMIABFILP01[\PIPE\atsvc] [201ef99a-7fa0-444c-9399-19ba84f12a1a] AppInfo :YES

      USMIABFILP01[\PIPE\browser] [30b044a5-a225-43f0-b3a4-e060df91f9c1]  :YES

      USMIABFILP01[\PIPE\srvsvc] [30b044a5-a225-43f0-b3a4-e060df91f9c1]  :YES

      USMIABFILP01[\PIPE\atsvc] [30b044a5-a225-43f0-b3a4-e060df91f9c1]  :YES

      USMIABFILP01[\PIPE\browser] [c9ac6db5-82b7-4e55-ae8a-e464ed7b4277] Impl friendly name :YES

      USMIABFILP01[\PIPE\srvsvc] [c9ac6db5-82b7-4e55-ae8a-e464ed7b4277] Impl friendly name :YES

      USMIABFILP01[\PIPE\atsvc] [c9ac6db5-82b7-4e55-ae8a-e464ed7b4277] Impl friendly name :YES

      USMIABFILP01[\PIPE\srvsvc] [552d076a-cb29-4e44-8b6a-d15e59e2c0af] IP Transition Configuration endpoint :YES

      USMIABFILP01[\PIPE\atsvc] [552d076a-cb29-4e44-8b6a-d15e59e2c0af] IP Transition Configuration endpoint :YES

      USMIABFILP01[\PIPE\srvsvc] [a398e520-d59a-4bdd-aa7a-3c1e0303a511] IKE/Authip API :YES

      USMIABFILP01[\PIPE\atsvc] [a398e520-d59a-4bdd-aa7a-3c1e0303a511] IKE/Authip API :YES

      USMIABFILP01[\PIPE\atsvc] [98716d03-89ac-44c7-bb8c-285824e51c4a] XactSrv service :YES

      USMIABFILP01[\PIPE\atsvc] [86d35949-83c9-4044-b424-db363231fd0c]  :YES

      USMIABFILP01[\PIPE\atsvc] [378e52b0-c0a9-11cf-822d-00aa0051e40f]  :YES

      USMIABFILP01[\PIPE\atsvc] [1ff70682-0a51-30e8-076d-740be8cee98b]  :YES

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

      USMIABFILP01[\pipe\cpqrcmc] [eb107bd0-c461-11cf-9522-00805fd4a309] CpqRcmc :YES

      USMIABFILP01[\PIPE\protected_storage] [12345778-1234-abcd-ef00-0123456789ac]  :YES

      USMIABFILP01[\pipe\lsass] [12345778-1234-abcd-ef00-0123456789ac]  :YES

     

    ncalrpc(Local Rpc)

      USMIABFILP01[WindowsShutdown] [d95afe70-a6d5-4259-822e-2c84da1ddb0d]  :YES

      USMIABFILP01[WMsgKRpc0A4BE0] [d95afe70-a6d5-4259-822e-2c84da1ddb0d]  :YES

      USMIABFILP01[WindowsShutdown] [76f226c3-ec14-4325-8a99-6a46348418af]  :YES

      USMIABFILP01[WMsgKRpc0A4BE0] [76f226c3-ec14-4325-8a99-6a46348418af]  :YES

      USMIABFILP01[LRPC-cf5a26e14a3efb07db] [c9ac6db5-82b7-4e55-ae8a-e464ed7b4277] Impl friendly name :YES

      USMIABFILP01[WMsgKRpc0A6191] [76f226c3-ec14-4325-8a99-6a46348418af]  :YES

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

      USMIABFILP01[dhcpcsvc6] [3c4728c5-f0ab-448b-bda1-6ce01eb0a6d5] DHCP Client LRPC Endpoint :NO

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

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

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

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

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

      USMIABFILP01[senssvc] [58e604e8-9adb-4d2e-a464-3b0683fb1480] AppInfo :YES

      USMIABFILP01[OLE5AB771C3652C498D95710A954DB3] [58e604e8-9adb-4d2e-a464-3b0683fb1480] AppInfo :YES

      USMIABFILP01[LRPC-f696f1a532e2956318] [58e604e8-9adb-4d2e-a464-3b0683fb1480] AppInfo :YES

      USMIABFILP01[IUserProfile2] [58e604e8-9adb-4d2e-a464-3b0683fb1480] AppInfo :YES

      USMIABFILP01[senssvc] [fd7a0523-dc70-43dd-9b2e-9c5ed48225b1] AppInfo :YES

      USMIABFILP01[OLE5AB771C3652C498D95710A954DB3] [fd7a0523-dc70-43dd-9b2e-9c5ed48225b1] AppInfo :YES

      USMIABFILP01[LRPC-f696f1a532e2956318] [fd7a0523-dc70-43dd-9b2e-9c5ed48225b1] AppInfo :YES

      USMIABFILP01[IUserProfile2] [fd7a0523-dc70-43dd-9b2e-9c5ed48225b1] AppInfo :YES

      USMIABFILP01[senssvc] [5f54ce7d-5b79-4175-8584-cb65313a0e98] AppInfo :YES

      USMIABFILP01[OLE5AB771C3652C498D95710A954DB3] [5f54ce7d-5b79-4175-8584-cb65313a0e98] AppInfo :YES

      USMIABFILP01[LRPC-f696f1a532e2956318] [5f54ce7d-5b79-4175-8584-cb65313a0e98] AppInfo :YES

      USMIABFILP01[IUserProfile2] [5f54ce7d-5b79-4175-8584-cb65313a0e98] AppInfo :YES

      USMIABFILP01[senssvc] [201ef99a-7fa0-444c-9399-19ba84f12a1a] AppInfo :YES

      USMIABFILP01[OLE5AB771C3652C498D95710A954DB3] [201ef99a-7fa0-444c-9399-19ba84f12a1a] AppInfo :YES

      USMIABFILP01[LRPC-f696f1a532e2956318] [201ef99a-7fa0-444c-9399-19ba84f12a1a] AppInfo :YES

      USMIABFILP01[IUserProfile2] [201ef99a-7fa0-444c-9399-19ba84f12a1a] AppInfo :YES

      USMIABFILP01[senssvc] [30b044a5-a225-43f0-b3a4-e060df91f9c1]  :YES

      USMIABFILP01[OLE5AB771C3652C498D95710A954DB3] [30b044a5-a225-43f0-b3a4-e060df91f9c1]  :YES

      USMIABFILP01[LRPC-f696f1a532e2956318] [30b044a5-a225-43f0-b3a4-e060df91f9c1]  :YES

      USMIABFILP01[IUserProfile2] [30b044a5-a225-43f0-b3a4-e060df91f9c1]  :YES

      USMIABFILP01[senssvc] [c9ac6db5-82b7-4e55-ae8a-e464ed7b4277] Impl friendly name :YES

      USMIABFILP01[OLE5AB771C3652C498D95710A954DB3] [c9ac6db5-82b7-4e55-ae8a-e464ed7b4277] Impl friendly name :YES

      USMIABFILP01[LRPC-f696f1a532e2956318] [c9ac6db5-82b7-4e55-ae8a-e464ed7b4277] Impl friendly name :YES

      USMIABFILP01[IUserProfile2] [c9ac6db5-82b7-4e55-ae8a-e464ed7b4277] Impl friendly name :YES

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

      USMIABFILP01[OLE5AB771C3652C498D95710A954DB3] [552d076a-cb29-4e44-8b6a-d15e59e2c0af] IP Transition Configuration endpoint :YES

      USMIABFILP01[LRPC-f696f1a532e2956318] [552d076a-cb29-4e44-8b6a-d15e59e2c0af] IP Transition Configuration endpoint :YES

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

      USMIABFILP01[senssvc] [a398e520-d59a-4bdd-aa7a-3c1e0303a511] IKE/Authip API :YES

      USMIABFILP01[OLE5AB771C3652C498D95710A954DB3] [a398e520-d59a-4bdd-aa7a-3c1e0303a511] IKE/Authip API :YES

      USMIABFILP01[LRPC-f696f1a532e2956318] [a398e520-d59a-4bdd-aa7a-3c1e0303a511] IKE/Authip API :YES

      USMIABFILP01[IUserProfile2] [a398e520-d59a-4bdd-aa7a-3c1e0303a511] IKE/Authip API :YES

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

      USMIABFILP01[OLE5AB771C3652C498D95710A954DB3] [98716d03-89ac-44c7-bb8c-285824e51c4a] XactSrv service :YES

      USMIABFILP01[LRPC-f696f1a532e2956318] [98716d03-89ac-44c7-bb8c-285824e51c4a] XactSrv service :YES

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

      USMIABFILP01[senssvc] [86d35949-83c9-4044-b424-db363231fd0c]  :YES

      USMIABFILP01[OLE5AB771C3652C498D95710A954DB3] [86d35949-83c9-4044-b424-db363231fd0c]  :YES

      USMIABFILP01[LRPC-f696f1a532e2956318] [86d35949-83c9-4044-b424-db363231fd0c]  :YES

      USMIABFILP01[IUserProfile2] [86d35949-83c9-4044-b424-db363231fd0c]  :YES

      USMIABFILP01[senssvc] [378e52b0-c0a9-11cf-822d-00aa0051e40f]  :YES

      USMIABFILP01[OLE5AB771C3652C498D95710A954DB3] [378e52b0-c0a9-11cf-822d-00aa0051e40f]  :YES

      USMIABFILP01[LRPC-f696f1a532e2956318] [378e52b0-c0a9-11cf-822d-00aa0051e40f]  :YES

      USMIABFILP01[IUserProfile2] [378e52b0-c0a9-11cf-822d-00aa0051e40f]  :YES

      USMIABFILP01[senssvc] [1ff70682-0a51-30e8-076d-740be8cee98b]  :YES

      USMIABFILP01[OLE5AB771C3652C498D95710A954DB3] [1ff70682-0a51-30e8-076d-740be8cee98b]  :YES

      USMIABFILP01[LRPC-f696f1a532e2956318] [1ff70682-0a51-30e8-076d-740be8cee98b]  :YES

      USMIABFILP01[IUserProfile2] [1ff70682-0a51-30e8-076d-740be8cee98b]  :YES

      USMIABFILP01[senssvc] [0a74ef1c-41a4-4e06-83ae-dc74fb1cdd53]  :YES

      USMIABFILP01[OLE5AB771C3652C498D95710A954DB3] [0a74ef1c-41a4-4e06-83ae-dc74fb1cdd53]  :YES

      USMIABFILP01[LRPC-f696f1a532e2956318] [0a74ef1c-41a4-4e06-83ae-dc74fb1cdd53]  :YES

      USMIABFILP01[IUserProfile2] [0a74ef1c-41a4-4e06-83ae-dc74fb1cdd53]  :YES

      USMIABFILP01[senssvc] [c9ac6db5-82b7-4e55-ae8a-e464ed7b4277] Impl friendly name :YES

      USMIABFILP01[OLE5AB771C3652C498D95710A954DB3] [c9ac6db5-82b7-4e55-ae8a-e464ed7b4277] Impl friendly name :YES

      USMIABFILP01[LRPC-f696f1a532e2956318] [c9ac6db5-82b7-4e55-ae8a-e464ed7b4277] Impl friendly name :YES

      USMIABFILP01[IUserProfile2] [c9ac6db5-82b7-4e55-ae8a-e464ed7b4277] Impl friendly name :YES

      USMIABFILP01[LRPC-f696f1a532e2956318] [c9ac6db5-82b7-4e55-ae8a-e464ed7b4277] Impl friendly name :YES

      USMIABFILP01[IUserProfile2] [c9ac6db5-82b7-4e55-ae8a-e464ed7b4277] Impl friendly name :YES

      USMIABFILP01[LRPC-f696f1a532e2956318] [2eb08e3e-639f-4fba-97b1-14f878961076]  :YES

      USMIABFILP01[IUserProfile2] [2eb08e3e-639f-4fba-97b1-14f878961076]  :YES

      USMIABFILP01[LRPC-f696f1a532e2956318] [c9ac6db5-82b7-4e55-ae8a-e464ed7b4277] Impl friendly name :YES

      USMIABFILP01[IUserProfile2] [c9ac6db5-82b7-4e55-ae8a-e464ed7b4277] Impl friendly name :YES

      USMIABFILP01[LRPC-08a2911b90f0a76d63] [24019106-a203-4642-b88d-82dae9158929]  :YES

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

      USMIABFILP01[LRPC-e2b510514f84f0127e] [3473dd4d-2e88-4006-9cba-22570909dd10] WinHttp Auto-Proxy Service :NO

      USMIABFILP01[OLE5B9513B9A3B843B3816FF3BA3319] [3473dd4d-2e88-4006-9cba-22570909dd10] WinHttp Auto-Proxy Service :NO

      USMIABFILP01[LRPC-e2b510514f84f0127e] [7ea70bcf-48af-4f6a-8968-6a440754d5fa] NSI server endpoint :NO

      USMIABFILP01[OLE5B9513B9A3B843B3816FF3BA3319] [7ea70bcf-48af-4f6a-8968-6a440754d5fa] NSI server endpoint :NO

      USMIABFILP01[LRPC-af9e713016a10c7eb2] [2fb92682-6599-42dc-ae13-bd2ca89bd11c] Fw APIs :NO

      USMIABFILP01[LRPC-af9e713016a10c7eb2] [7f9d11bf-7fb9-436b-a812-b2d50c5d4c03] Fw APIs :NO

      USMIABFILP01[LRPC-af9e713016a10c7eb2] [dd490425-5325-4565-b774-7e27d6c09c24] Base Firewall Engine API :NO

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

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

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

      USMIABFILP01[LRPC-36bc780bc321e14d2c] [9d5f40ff-f1c2-4394-8671-9e56427fcd70]  :NO

      USMIABFILP01[samss lpc] [12345778-1234-abcd-ef00-0123456789ac]  :YES

      USMIABFILP01[dsrole] [12345778-1234-abcd-ef00-0123456789ac]  :YES

      USMIABFILP01[protected_storage] [12345778-1234-abcd-ef00-0123456789ac]  :YES

      USMIABFILP01[lsasspirpc] [12345778-1234-abcd-ef00-0123456789ac]  :YES

      USMIABFILP01[lsapolicylookup] [12345778-1234-abcd-ef00-0123456789ac]  :YES

      USMIABFILP01[LSARPC_ENDPOINT] [12345778-1234-abcd-ef00-0123456789ac]  :YES

      USMIABFILP01[securityevent] [12345778-1234-abcd-ef00-0123456789ac]  :YES

      USMIABFILP01[audit] [12345778-1234-abcd-ef00-0123456789ac]  :YES

      USMIABFILP01[LRPC-3e26121c18c7fb5521] [12345778-1234-abcd-ef00-0123456789ac]  :YES

      USMIABFILP01[OLEDF121951FF8F4C5C856E96DFB235] [897e2e5f-93f3-4376-9c9c-fd2277495c27] Frs2 Service :YES

      USMIABFILP01[LRPC-3dd52e5b5c1ffcbd82] [906b0ce0-c70b-1067-b317-00dd010662da]  :YES

      USMIABFILP01[LRPC-3dd52e5b5c1ffcbd82] [906b0ce0-c70b-1067-b317-00dd010662da]  :YES

      USMIABFILP01[LRPC-3dd52e5b5c1ffcbd82] [906b0ce0-c70b-1067-b317-00dd010662da]  :YES

      USMIABFILP01[LRPC-3dd52e5b5c1ffcbd82] [906b0ce0-c70b-1067-b317-00dd010662da]  :YES

      USMIABFILP01[LRPC-7911cb76714e9dcbb7] [12345678-1234-abcd-ef00-0123456789ab] IPSec Policy agent endpoint :NO

      USMIABFILP01[WMsgKRpc05843C2] [12e65dd8-887f-41ef-91bf-8d816c42c2e7] Secure Desktop LRPC interface :YES

      USMIABFILP01[WMsgKRpc05843C2] [76f226c3-ec14-4325-8a99-6a46348418af]  :YES

      USMIABFILP01[LRPC-005e7027194304501b] [f1ec59ab-4ca9-4c30-b2d0-54ef1db441b7] Isolation Communication Endpoint :YES

      USMIABFILP01[OLE13F328F170244E1D881BBC17E9C1] [f1ec59ab-4ca9-4c30-b2d0-54ef1db441b7] Isolation Communication Endpoint :YES

      USMIABFILP01[LRPC-bb29de7aa5ad3cc8bf] [f1ec59ab-4ca9-4c30-b2d0-54ef1db441b7] Isolation Communication Endpoint :YES

     

    ncacn_ip_tcp(Connection-oriented TCP/IP)

      USMIABFILP01[49153] [3c4728c5-f0ab-448b-bda1-6ce01eb0a6d5] DHCP Client LRPC Endpoint :NO

      USMIABFILP01[49153] [3c4728c5-f0ab-448b-bda1-6ce01eb0a6d6] DHCPv6 Client LRPC Endpoint :NO

      USMIABFILP01[49153] [30adc50c-5cbc-46ce-9a0e-91914789e23c] NRP server endpoint :NO

      USMIABFILP01[49153] [f6beaff7-1e19-4fbb-9f8f-b89e2018337c] Event log TCPIP :NO

      USMIABFILP01[49154] [58e604e8-9adb-4d2e-a464-3b0683fb1480] AppInfo :YES

      USMIABFILP01[49154] [fd7a0523-dc70-43dd-9b2e-9c5ed48225b1] AppInfo :YES

      USMIABFILP01[49154] [5f54ce7d-5b79-4175-8584-cb65313a0e98] AppInfo :YES

      USMIABFILP01[49154] [201ef99a-7fa0-444c-9399-19ba84f12a1a] AppInfo :YES

      USMIABFILP01[49154] [30b044a5-a225-43f0-b3a4-e060df91f9c1]  :YES

      USMIABFILP01[49154] [c9ac6db5-82b7-4e55-ae8a-e464ed7b4277] Impl friendly name :YES

      USMIABFILP01[49154] [552d076a-cb29-4e44-8b6a-d15e59e2c0af] IP Transition Configuration endpoint :YES

      USMIABFILP01[49154] [a398e520-d59a-4bdd-aa7a-3c1e0303a511] IKE/Authip API :YES

      USMIABFILP01[49154] [98716d03-89ac-44c7-bb8c-285824e51c4a] XactSrv service :YES

      USMIABFILP01[49154] [86d35949-83c9-4044-b424-db363231fd0c]  :YES

      USMIABFILP01[49155] [12345778-1234-abcd-ef00-0123456789ac]  :YES

      USMIABFILP01[63988] [367abb81-9844-35f1-ad32-98f038001003]  :NO

      USMIABFILP01[64018] [897e2e5f-93f3-4376-9c9c-fd2277495c27] Frs2 Service :YES

      USMIABFILP01[49152] [d95afe70-a6d5-4259-822e-2c84da1ddb0d]  :YES

     

    rpcdump.exe completed sucessfully after 1 seconds

     

    Thursday, October 07, 2010 12:02 PM
  • Ok guys, I found out the fallowing, this might help:

    I’m running the fallowing command from the Windows 2003 R2:

    Command:

    NTFRSUTL version usmiabfilp01 (usmiabfilp01 is the windows 2008 file server)

    Result:

    NtFrsApi Version Information

       NtFrsApi Major      : 0

       NtFrsApi Minor      : 0

       NtFrsApi Compiled on: Feb 16 2007 20:01:19

    ERROR - Cannot bind w/authentication to computer, usmiabfilp01; 000006d9 (1753)

    ERROR - Cannot bind w/o authentication to computer, usmiabfilp01; 000006d9 (1753

    )

    ERROR - Cannot RPC to computer, usmiabfilp01; 000006d9 (1753)

    It look like the Windows 2008 R2 firewall is blocking the traffic,

     

    Can someone help me with this one?

    Tuesday, October 12, 2010 2:03 PM
  • If you suspect that the firewall is blocking the traffic, please disable it and check if all is okay or not.

    If when it is disabled, all is okay. Try to configure the firewall rules to allow RPC connections.

    If when it is disabled, the problem persists, try to disable all your security softwares on both servers and check the result.

     
    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
    Tuesday, October 12, 2010 7:24 PM
  • Hi Luis,

    On Windows Server 2008 R2, your firewall rules should reflect any installed roles on the computer.  If you suspect a configuration problem there, you'll want to try opening up the firewall rules to allow RPC traffic to any endpoint, to see if it makes a difference.  You can do this by going into control panel and manually modifying the firewall settings.

    If you've tried this alread and the issue still occurs, it's entirely possible that the problem may be on the network in between the two servers.  One of the really important, but often overlooked details is that Windows Server 2008 R2 uses a different dynamic port range than Windows Server 2003.  If you have a device in between the two servers that is running any sort of basic port filtering, this can screw up communicaton between them.  For more information see this KB article:

    929851 The default dynamic port range for TCP/IP has changed in Windows Vista and in Windows Server 2008
    http://support.microsoft.com/default.aspx?scid=kb;EN-US;929851

    I'd recommend taking a simultaneous network capture while duplicating the failure, and reviewing that to see if any connections are not completing successfully.


    David Beach - Microsoft Online Community Support
    • Marked as answer by Tiger Li Thursday, November 04, 2010 3:06 AM
    Monday, October 18, 2010 5:20 PM
  • Hey guys, I hope to file a bug on this soon. Here is how you can repro

     

    Step 1: Promo a Windows 2003 ent DC\GC (in my lab DFL and FFL are Windows 2003 Native)

    Step 2: Prep Domain and Forest for Window Server 2008 R2

    Step 3: Promote a Windows Server 2008 R2 GC

    Step 4: Set NTFRS port to 49153 or 49154 (the only two ports I tested. Follow KB319553)

    Step 5: Restart the NTFRS service

    Step 6: Attempt to connect to ntfrs service on Windows 2008 R2 Server (NTFRSUTL Version localhost)

    If you set the port to 60000 it works just fine, just cant use those ports....

    Thanks Brantley Whittley for helping me figure this out!

    HollisWms

     

    Tuesday, December 21, 2010 2:21 AM