You can do more research on ONCRPC or SUNRPC for details, but portmapper itself has a TCP/IP Port, which RPC clients connect to, to query for the port that a named service is listening on, (which is arbitrarily assigned when the server process registers with the portmapper) So in effect, it can be any port > 1023 and < the cap 65XXX (Don't remember exactly what the top is). - and it will likely be different every time the app server app is started. We'll generally use name resolution based balancers / failover systems for portmapper based stuff. - or you can just set your session based balancer to forward ALL of those ports. As for not being able to set your client app, if it uses a recent API library to connect (I'm thinking >= 5.x) , I believe it should pay attention to the ARTCPPORT environment variable. HTH, -Brian Luke ________________________________
From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Gray, Alexander Sent: Friday, January 26, 2007 2:44 PM To: [email protected] Subject: What port range does portmapper use? ** Having an issue with a custom built API app that doesn't allow you to set a port. We need to set the port because we have everything running through a Load Balancer where setting ports is a requirment. They will let us turn on a range of ports but I do not know what range of ports portmapper uses...does anyone have an idea of the range? Thanks Alexander P. Gray Operations Planning Manager, ITS/ICS COE, Infrastructure & Technology [EMAIL PROTECTED] [EMAIL PROTECTED] ----------------------------------- 703. 676. 2375 (office) 703. 932. 9979 (nextel) 703. 676. 2931 (fax) __20060125_______________________This posting was submitted with HTML in it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
