DFSR error 1753 (Event id 5002) - There are no more endpoints available from the endpoint mapper

עידן טנקל 26 Reputation points
2020-11-29T18:34:28.557+00:00

Hey all,

We have 2 windows 2016 servers within a single replication group.

When we attempt to start the DFS replication between the 2 servers, we get the following error:

1753 (There are no more endpoints available on endpoint mapper)

Also, our files do not replicated at all!

I found a previous thread in the old forums

dfs-replication-eror-1753-there-are-no-more-endpoints-available-from-the-endpoint-mapp

https://social.msdn.microsoft.com/Forums/en-US/d256fa87-d9c3-40b9-9c3a-98d21d823e89/dfs-replication-eror-1753-there-are-no-more-endpoints-available-from-the-endpoint-mapp?forum=winserver8gen&prof=required

And we have tested the connectivity between the 2 servers, it seems fine.

I need your help to resolve this issue :-)
We do not have network problem (e.g. firewall drops in 135 or something obvious like that)

Is there a way to resolve / bypass this issue?

Tnx

Idan Tankel

Windows for business | Windows Server | User experience | Other
{count} votes

Accepted answer
  1. Anonymous
    2020-11-29T19:11:51.49+00:00

    There are no more endpoints available on endpoint mapper

    I usually see this one when some process that uses dynamic ports does not close cleanly and at next call gets next higher available port until we eventually run out.
    netstat -aon
    should show this result, and a reboot should release the ports at least temporarily. More info here.
    https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/manage/replication-error-1753-there-are-no-more-endpoints-available-from-the-endpoint-mapper

    --please don't forget to Accept as answer if the reply is helpful--


2 additional answers

Sort by: Most helpful
  1. עידן טנקל 26 Reputation points
    2020-12-07T09:03:21.943+00:00

    Hey, We have found the process holding up ports and killed it :-)

    We have noticed that the replication started after the processes killed by event log under DFSR windows event log

    Another solution is to restart one of the servers trying to establish the session

    Thanks a lot

    Tankel


  2. Dinesh Rakhyani 1 Reputation point
    2022-08-25T11:19:51.79+00:00

    234849-affected.png

    I am facing the same issue, the attached screeshot shows the ports are open except 3268 and 3269 because the destination DC is not a GC. What else can be checked here.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.