NSE7_NST-7.2 Exam Study Guide: The Ultimate 2026 Practice Test

Refused Connection: A refused connection typically indicates a mismatch in the TCP port configuration between the FortiGate and the collector agent. Ensuring both are configured to use the same TCP port is crucial for proper connectivity.

Mismatched Pre-Shared Password: If the pre-shared password configured on the FortiGate does not match the one set on the collector agent, authentication will fail, leading to connectivity issues.

Inability to Reach IP Address: This can occur due to network issues such as incorrect routing, firewall rules blocking traffic, or the collector agent being down. Verifying network connectivity and the status of the collector agent is necessary to resolve this issue.

References:

Fortinet Community: Troubleshooting FSSO Connectivity Issues​ ( Welcome to the Fortinet Community! ) ​​ ( Welcome to the Fortinet Community! ) ​​ ( Welcome to the Fortinet Community! ) ​.

The exhibit shows log entries from the FSSO (Fortinet Single Sign-On) collector agent logs. These logs provide insights into why there might be issues with the collector agent connecting to workstations or the registry.

Remote registry is not running on the workstation : The failure to connect to the workstation registry can occur if the remote registry service on the workstation is not running. This service needs to be active to allow the FSSO collector agent to query the workstation for user login information.

DNS resolution is unable to resolve the workstation name : The logs indicate a failure in connecting to a workstation by name, which can happen if the DNS server is unable to resolve the workstation's name to an IP address. This is a common issue when the DNS settings are incorrect or the workstation name is not properly registered in the DNS.

A firewall is blocking traffic to port 139 and 445 : Communication issues to the workstation or registry are often caused by firewall rules blocking essential ports. Ports 139 (NetBIOS) and 445 (SMB) are critical for these operations. Ensure these ports are open on both the workstation and any intermediate firewalls.

References

Fortinet Community Documentation on FSSO Troubleshooting

Fortinet Community on FSSO Collector Agent Issues

The exhibit shows a sniffer capture where TCP port 8013 is being used for communication. The communication appears one-way, indicating potential issues with the upstream FortiGate receiving the necessary packets or being able to respond.

To ensure successful communication in a Security Fabric setup:

Ensure TCP port 8013 is not blocked along the way : Verify that no firewalls or network devices between the downstream and upstream FortiGates are blocking TCP port 8013. This port is crucial for Security Fabric communication.

Authorize the downstream FortiGate on the root FortiGate : In the Security Fabric, the root FortiGate must recognize and authorize the downstream FortiGate to allow proper communication and management.

Enable Security Fabric/Fortitelemetry on the receiving interface of the upstream FortiGate : The upstream FortiGate must have the Security Fabric or Fortitelemetry enabled on the interface that receives the communication from the downstream FortiGate. This enables proper data exchange and monitoring within the Security Fabric.

References

Fortinet Documentation on Security Fabric Configuration

Fortinet Community Discussion on Port Requirements