Support Forum
The Forums are a place to find answers on a range of Fortinet products from peers and product experts.
Satory
New Contributor III

Forti EMS port range or Alternative

We have a FortiEMS 7.4 and we want to expose RPC ports through the ZTNA.

For what I have read so far there is only possibility to define single port per ZTNA destination rule.

The problem is that by specification RPC uses:

-  TCP 135

- Dynamic TCP range 49152-65535.

 

How to make the dynamic range accessible through the ZTNA?

On the FortiGate site it is OK, but on the client site when we try to create destination rule like:

Server: 49152-65535

The server is no longer resolved through ZTNA and no connection can be processed by it.

2 REPLIES 2
pmeet
Staff
Staff

you can try doing a TCP forwarding instead of https.

You can refer the article referred and instead of youtube.com use your destination server IP with no port forward,

https://community.fortinet.com/t5/FortiGate/Technical-Tip-How-to-implement-ZTNA-TCP-forwarding-for-p... 

PATELMM
Satory
New Contributor III

I am doing TCP forwarding.
But for use of dynamic ports I need to define 14K rules, which is 11MB policy and is not working.

It is easy to forward one port, I need a huge range of ports.

Announcements

Select Forum Responses to become Knowledge Articles!

Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.

Labels
Top Kudoed Authors