Technical Tip : Resolving AIM login issues when FortiGate blocks as HTTPS
Description
This article gives tips on resolving issues involving AIM IM login and FortiGuard utilization on the FortiGate.
Scope
All FortiGate users
Solution
A FortiGate using FortiGuard web filtering may experience issues whereby AIM IM users are unable to login. This can happen because AIM uses TCP port 443 for login which is shared with Fortinet FortiGuard services.
There are two recommendations to reduce any potential conflict:
1. Ensure that IPS updates are working and up to date. Internal signatures are used to identify new and old AIM versions and separate them from HTTPS traffic.
2. Keep FortiOS firmware up to date. Try to stay within two releases of the current firmware version, and on the most recent patch of that version.