The first requirement is the connection from the FortiGate unit to the collector agent. If not found search for the username of the test host. This can be viewed in the collector agent logs. Reset the password between the two devices. Start at the end of the file and search backwards for the IP of the test host. 
| Uploader: | Gabar |
| Date Added: | 7 September 2008 |
| File Size: | 37.39 Mb |
| Operating Systems: | Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X |
| Downloads: | 38097 |
| Price: | Free* [*Free Regsitration Required] |
If it is not using a domain administrator account, please change the account. Otherwise proceed to section "Not seeing logon events". Only the first authenticated group is allowed through a FortiGate firewall policy Troubleshooting Tip: If the IP is listed with the username of a service account, the service account is generating a logon event and is overriding the user's logon.
Make sure nothing is blocking fortiyate traffic between the FortiGate and the collector agent. A common problem is with multi-homed hosts i.
To confirm that the DC agent is installed, you can refer to article "Where is DCagent service" in the related articles. Please check also the article "Only ffsae first authenticated group allowed through policy" see related articles csae. The first requirement is the connection from the FortiGate unit to the collector agent.
These include the collector agent unable to resolve the host name at all or resolving to an incorrect IP. It is assumed the initial setup of FSAE has been completed.
This can be viewed in the collector agent logs. You should try to disable it and running the commands from branch point 3 again. The following command will start capturing traffic on the FortiGate: Collector agent not running Steps to follow: Is the Collector Agent running? This article provides troubleshooting steps that can fswe used when encountering FSAE problems.
Fortinet fsae collector agent
Otherwise, proceed to section "Collector Agent running but not connected". Verify the groups configuration. Is the FortiGate unit connected to the collector agent? The best way to verify the connectivity is by running the following CLI commands: If you found the host in any of the searches proceed to subsection A, otherwise proceed to subsection B.
Reset the password between the two devices. A good article on this issue is "Windows application forces to log-off the current user on FSAE and access through the FortiGate is blocked" see related articles below. If the Collector agent is not running, go to section clent agent not running".
The FortiGate will receive traffic from the IP of the other interface and think the host is not authenticated. The related article "Troubleshooting Tip: If not found search for the username of the test host.
Fortinet fsae collector agent download
Start at the end of the file and search backwards for the IP of the test host. Either way you will need to check the DNS server. If still not found search for the hostname of the test host. More on group caching as well as how to disable this feature can be found on "New Feature in FSAE build 42 and later Group caching " see related articles below. Overview The following chart shows an overview of the troubleshooting process: Opening the collector agent configuration interface displays the status of the collector agent service.
Not seeing logon events Steps description: A multi-homed host may resolve host name to the IP address of one interface while send traffic out another.
Комментарии
Отправить комментарий