none
Server 2008 R2 AD, DC, DNS, CS - No Endpoints -What is the best path to take for Migration to a new Server? RRS feed

  • Question

  • Can I migrate to a new server when there are no endpoints. went through troubleshooting for error 1753 and others. Was unable to determine what exactly was broke. The errors started after a power outage. There Is a member 2008 R2 Server on the network ready to take on the Roles, but am very hesitant about starting a process that will not complete.

    What is the best path to take for Migration to a new Server.

    Event ID 1655:

    Active Directory Domain Services attempted to communicate with the following global catalog and the attempts were unsuccessful.
     
    Global catalog:
    \\Server.DomainName.local
     
    The operation in progress might be unable to continue. Active Directory Domain Services will use the domain controller locator to try to find an available global catalog server.
     
    Additional Data
    Error value:
    1753 There are no more endpoints available from the endpoint mapper.


    Ron Oldham

    Tuesday, July 7, 2015 9:40 PM

All replies

  • Hi,

    Thanks for your post.

    About the error 1753 There are no more endpoints available from the endpoint mapper, you could refer to the following article for troubleshooting:

    https://technet.microsoft.com/en-us/library/replication-error-1753-there-are-no-more-endpoints-available-from-the-endpoint-mapper(v=ws.10).aspx

    About event id 1655, according to Microsoft:

    This behavior occurs because the Kerberos tickets in the domain controller are not valid on other domain controllers in the domain.

    http://kb.prismmicrosys.com/evtpass/evtpages/EventId_1655_NTDSGeneral_46998.asp

    Regards.


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com

    Thursday, July 9, 2015 9:00 AM
    Moderator
  • Hi,

    Any update about the issue?

    Regards.


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com

    Monday, July 20, 2015 6:06 AM
    Moderator
  • Hi Vivian,

    I went through the troubleshooting outlined in the article at:

    http://kb.prismmicrosys.com/evtpass/evtpages/EventId_1655_NTDSGeneral_46998.asp

    until the section on using portquery where there was no output for ncacn_ip_tcp protocol in the MS NT Directory DRS Interface section of the output. And the article does not explain how the fix it. If there is a registry key or a method that would open this port would the endpoint mapper function again.

    Thank you,

    RonO


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

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

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

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


    Ron Oldham

    Monday, July 20, 2015 4:59 PM
  • Hi,

    Thanks for your response.

    Did you refer to the following KB article to troubleshoot the AD Replication error 1753: There are no more endpoints available from the endpoint mapper?

    https://support.microsoft.com/en-us/kb/2089874

    Regards.


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com

    Tuesday, July 21, 2015 5:37 AM
    Moderator
  • Hi,

    Yes https://support.microsoft.com/en-us/kb/2089874 was a possible solution everything was as expected until I used the port query tool and there was no output for ncacn_ip_tcp and I did not find a way to create ncacn_ip_tcp protocol.


    Ron Oldham

    Tuesday, July 21, 2015 8:08 PM