If other device within the same subnet/on the same interface work but those, and you don't see anything obvious in the config blocking traffic from those specific devices, you need to run "flow debug" to see why it's dropped or blocked.
Try this: open a CLI console and type:
show | grep -f x.x.x.x
(where x.x.x.x is the IP address that is not working on the LAN)
If this IP address is defined anywhere in your FortiGate's configuration this will tell you where. For example, the IP could be used in a bad Policy Route that is sending traffic from that IP out a bad gateway, or you could find that IP misconfigured in an IP Pool.
If this matches an address object (e.g. "ComputerX"), run the command again for hits against the object name (e.g. show | grep -f ComputerX).
Russ
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 |
---|---|
1740 | |
1109 | |
752 | |
447 | |
240 |
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.