I am testing a fortianalyzer-vm (ver 5.6.0) and trying to get a remote fortigate (5.6.2) to communicate back to the analyzer inside my network. As long as I keep the inbound ports set to 'any' it communicates fine. As soon as I start to lock it down using this document http://docs.fortinet.com/uploaded/files/3020/fortinet-communication-ports-and-protocols-54.pdf. I loose communication. Anyone have any suggestions? I cannot open a case as its a trial VM.
Nevermind, I found instead of using the built in services for RSH (tcp514) I created my own and it started working. I should have actually looked at the service port prior to using it as RSH has other configurations inside that was causing my issue.
Hi
udp port 514 must enable. can you please share the below command out put.
diagnose sniffer packet any 'port 514' 4 0 Regards
Mahesh
suggestion FTNT has a port listing doc available, it designed to help you determine what ports are in used by various platforms from FTNT
http://docs.fortinet.com/...s-and-protocols-54.pdf
PCNSE
NSE
StrongSwan
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1759 | |
1116 | |
766 | |
447 | |
242 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2025 Fortinet, Inc. All Rights Reserved.