Welcome to ISAserver.org

"No more endpoints available" message

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [ISA Server 2004 General ] >> Exchange Publishing >> "No more endpoints available" message

Page: [1]

Message

<< Older Topic Newer Topic >>

"No more endpoints available" message - 19.Nov.2004 8:27:00 PM

unclehughie

Posts: 70
Joined: 31.Dec.2001
From: Montreal, Canada
Status: offline

I've been working my way through Tom's FE/BE Perimeter setup instructions in the kit. I've got as far as joining the front-end server to the domain, but this fails with a message that "no more endpoints available from endpoint mapper". I believe this has something to do with RPC and I did notice an unexplained requirement in connection with the ADLogon/DirRep new protocol that "RPC key" needs to be set on BEServer. This is not a domain AD problem because I have subsequently joined another client machine to the domain successfully. What is an RPC key and how do I set it, please?

Post #: 1

Featured Links*

RE: "No more endpoints available" message - 20.Nov.2004 5:38:00 AM

TitusHoc

Posts: 114
Joined: 17.Nov.2004
From: Canada - Toronto
Status: offline

Hello unclehughie,

What is the port on the ADLogon/DirRep Protocol? Did you change the registry key on the DC to match that port?
Fallow these steps on your DC
1.Click Start and click Run. In the Open text box enter Regedit and click OK.
2.Go to the following Registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters\
3.Click the Edit menu and point to New. Click DWORD Value.
4.Rename the entry from New Value #1 to TCP/IP Port, and then double click the entry.
5.In the Edit DWORD Value dialog box, select the Decimal option. Enter the port that you specify on the ADLogon/DirRep Protocol in the Value data text box. Click OK.
6.Restart the domain controller.
Based on my experience only one port is not enough for the RPC ports so I suggest trying these steps on all the Domain controllers:

1. Add the Internet key under: HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc
2.Under the Internet key, add the values "Ports" (MULTI_SZ), "PortsInternetAvailable" (REG_SZ), and "UseInternetPorts" (REG_SZ).
In this example, use ports 5000 through 5020 inclusive, so the new registry
key appears as follows:
Ports: REG_MULTI_SZ: 5000-5020
PortsInternetAvailable: REG_SZ: Y
UseInternetPorts: REG_SZ: Y
3.Restart the server. All applications that use RPC dynamic port allocation uses ports 5000 through 5020, inclusive. In most environments, a minimum of 20 ports should be opened, because several system services rely on these RPC ports to communicate with each other.
Alos you need to change the ADLogon/DirRep Protocol to point to the same range is this case 5000-2020

Have a look on this article for more details:
http://support.microsoft.com/default.aspx?scid=kb;en-us;154596

Let me know if this help

(in reply to unclehughie)

Post #: 2

RE: "No more endpoints available" message - 7.Dec.2004 9:38:00 PM

topski2000

Posts: 4
Joined: 7.Dec.2004
Status: offline

Hello,

I have the same problem. I read the reply but I do not understand why first to add a single port to the NTDS parameters and later on use different ports. After you say to modify the ADLogon/DirRep Protocol. Where can you do this and on what servers ? All of them ? And do I have to change the ISA2004 rule as well ?

Please comment. I am really stuck [Mad]

(in reply to unclehughie)

Post #: 3

RE: "No more endpoints available" message - 12.Dec.2004 1:30:00 PM

tshinder

Posts: 47644
Joined: 10.Jan.2001
From: Texas
Status: offline

Hey guys,

Have you tried it using the instructions I provided? The purpose of creating the custom port is to prevent the requirement for negotiating dynamic RPC connection ports.

HTH,
Tom

(in reply to unclehughie)

Post #: 4

RE: "No more endpoints available" message - 30.May2006 12:28:45 PM

waynewhittle

Posts: 96
Joined: 21.Apr.2004
From: Cardiff
Status: offline

Hi Tom,

Are you referring to the instructions as detailed in http://www.isaserver.org/articles/2004dmzfebe.html ? I am having trouble finding the registry key to edit:

HKEY_LOCAL_MACHINE\CurrentControlSet\Services\NTDS\Parameters

The CurrentControlSet is found under HKEY_LOCAL_MACHINE\System.?? I don't mess with the registry so I want to make sure that what I am doing is correct. Also pelase confirm I will need to set this registry on all BE Exchanges, Global Catalogs and Domain Controllers across all sites in our domain ?We have one domain and three sites with two domain controllers and a BE Exchange in each site.

Best regards

Wayne

(in reply to tshinder)

Post #: 5