<div>
What about the high ports needed like 1024 - 65....<br />
would those be covered in the protocol settings?<br />

</div>


What about the high ports needed like 1024 - 65....
would those be covered in the protocol settings?


<div>
Depends on what you mean exactly.<br />
If you are referring to return traffic, that is allowed by default.<br />
If you are referring to additional incoming connections, the checkpoint is a stateful firewall. This means that it 'knows' that related incoming traffic (related to the initial setup over one of those ports) should be allowed as well.<br />
So you should be ok with that.
</div>


Depends on what you mean exactly.
If you are referring to return traffic, that is allowed by default.
If you are referring to additional incoming connections, the checkpoint is a stateful firewall. This means that it 'knows' that related incoming traffic (related to the initial setup over one of those ports) should be allowed as well.
So you should be ok with that.

<div>
Are those protocol built into checkpoint so that I could just select them?
</div>


Are those protocol built into checkpoint so that I could just select them?

<div>
I think so, they are quite common.<br />
You'll have to create the rules though.<br />
<br />
&nbsp;<a href="https://filedb.experts-exchange.com/incoming/2011/03_w11/417547/How-to-configure-the-Security-Po.doc" target="_blank" class="file-inline" title="checkpoirules (909 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>How-to-configure-the-Security-Po.doc</a>
</div>


I think so, they are quite common.
You'll have to create the rules though.

 How-to-configure-the-Security-Po.doc [https://filedb.experts-exchange.com/incoming/2011/03_w11/417547/How-to-configure-the-Security-Po.doc]

How-to-configure-the-Security-Po.doc

<div>
<div class="content wysiwyg-content">
Hi,<br />
<br />
I need to allow the following through my checkpoint firewall r70.30<br />
&nbsp;• &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;MS RPC EndPoint<br />
• &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;MS-DTC interface<br />
<br />
<br />
It is possible to do this by protocol as apposed to just opening all the ports?<br />
Also what about a UUID inside the packet?
</div>
</div>


Hi,

I need to allow the following through my checkpoint firewall r70.30
 •	MS RPC EndPoint
•	MS-DTC interface


It is possible to do this by protocol as apposed to just opening all the ports?
Also what about a UUID inside the packet?

checkpoint firewall allow msdtc and rpc

Software firewalls, also known as host-based firewalls, provide a layer of software on one host that controls network traffic in and out of that single machine. Most operating systems now include firewall software, but many available software firewalls include central distribution, antivirus systems and disaster recovery.

Software Firewalls

Hardware-based firewalls provide more sophisticated protection for inbound and outbound traffic than the simple Windows software firewall or the basic NAT firewalls found in routers. These devices implement techniques such as stateful packet inspection, deep packet inspection, and content filtering; and may include built-in antivirus and anti-malware protection.

Hardware Firewalls

Network design and methodology, also known as network architecture, is the design of a communication network. It is a framework for the specification of a network's physical components and their functional organization and configuration, its operational principles and procedures, as well as data formats used in its operation. In telecommunication, the specification of a network architecture may also include a detailed description of products and services delivered via a communications network, as well as detailed rate and billing structures under which services are compensated.