Acutally, I went the other route and forced the developers to set their
DCOM registry settings such that it limits DCOM ports to something
manageable (like say TCP 5000-5020). Then I just allowed that range
through. Just a thought...
J
At 11:41 AM 7/7/00 +0200, Mark van Gelder wrote:
>
>Hi
>
>We have had a ticket open with Checkpoint about this for close to a year
>now. We have just escalated this with them.
>
>Basically you need the CLSID of the application and that is converted to the
>service definition.
>
>I will mail you some info that we have received, even though we have had no
>success so far. It would be nice to hear if anyone else has gotten this to
>work.
>
>Cheers
>mark
>
>
>-----Original Message-----
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED]]On Behalf Of
>emanuela.sacchettini
>Sent: Thursday, July 06, 2000 10:01 PM
>To: [EMAIL PROTECTED]
>Subject: [FW1] service dcom
>
>
>
>Hi,
>our customer needs to use the service 'dcom' for same application.
>This service uses a dinamic assignation of ports.
>Can someone help me for the definition of this service?
>
>thanks a lot
>regards
>
>manus
>
>
>
>============================================================================
>====
> To unsubscribe from this mailing list, please see the instructions at
> http://www.checkpoint.com/services/mailing.html
>============================================================================
>====
>
>
>
>===========================================================================
=====
> To unsubscribe from this mailing list, please see the instructions at
> http://www.checkpoint.com/services/mailing.html
>===========================================================================
=====
>
>
================================================================================
To unsubscribe from this mailing list, please see the instructions at
http://www.checkpoint.com/services/mailing.html
================================================================================
