Re: FW-1 and RPC with MSDTC

[Michael Nelson <mikenel () iapetus com>]

P.S. The decision about dynamic/static endpoints is one that the
programmer makes at development time.

On Fri, 12 Jan 2001, Michael Nelson wrote:

> On Sat, 13 Jan 2001, Darren Reed wrote:
> > - you can't control what port number an RPC service gets (you can only
> >   influence the range used for the random allocation)
>
> Dynamic endpoints (TCP ports) is a feature that is not mandatory.  You can
> use statically bound endpoints. Exchange, in fact, has registry options
> that let you put some of its well-known services (like the DS and IS) on
> specific TCP ports.
>
> > Now if you can do all that with MS RPC packets too, someone please send
> > me the docs on how to decode the "service number" or "service name" in the
> > RPC-loc packets.  It has got to be there, else the client end cannot talk
> > to the server, I just don't know how...anyone, please ? :)
>
> You register interface UUIDs with the endpoint mapper.
>
> Also, see http://support.microsoft.com/support/kb/articles/Q159/2/98.ASP.
>
> I am pretty sure that CheckPoint 4.x has support for MSRPC interface
> filtering.
>
> -mike

_______________________________________________
firewall-wizards mailing list
firewall-wizards () nfr com
http://www.nfr.com/mailman/listinfo/firewall-wizards