Re: What is the upper and lower port range for RPC - Remote Procedure Call -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

On 5/9/2017 3:10 PM, Steinmetz, Paul wrote:

What is the upper and lower port range for RPC - Remote Procedure Call ?

The ports used are determined by the server. In this case, 'server'
means the platform where the RPC is executing, not your IBM platform.

What happens is the client calls up the server on port 135 and the
server says 'Let's go to port nnn' and they get off the 'command'
channel and on to the 'data' channel.

We need to open the range of ports for RPC on the firewalls.
For PCI compliancy reasons, can this range be limited/reduced?

Sounds weird, but I didn't write that law :-/ Contact the server
people; they hold the keys to this kingdom. Here's why: Say the server
has an 'available port' table holding 1, 2, 3. The firewall has
permission for port 1. The client calls up the server, which says 'Go
to port 2' (it's port 2's turn). Because as far as the server is
concerned, port 2 is OK. They both go to port 2 which is denied by the
firewall, and the RPC client will time out trying to connect.

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.