Created on ‎04-28-2008 12:28 PM
As the FG is in transparant mode, I assume session time-outs don' t come into play, or do they?Timeouts play even in TP mode, but you' re talking about couple of minutes, a very short timeout. Defaults are higher (3600 sec), so it seems to be another issue. Check table sessions in dashboard and play with ' config system session-ttl' CLI command for your protocols, i.e, for rdp standard 3389/tcp port:
config system session-ttl
config port
edit 3389
set timeout 7200
next
end
end
regards
/ Abel
Created on ‎04-29-2008 02:00 AM
config system session-ttl
set default 300
config port
edit 22
set timeout 3600
next
end
end
interesting, maybe your previous admin tried to react to ' The system has entered conserve mode' message for a overloaded box; there' s an kc' s article (http://kc.forticare.com/default.asp?id=1076) where one of the emergency settings was set default timeout to 300 sec.
Or the emergency became permanent or you' ve inherited the box meanwhile; maybe the cluster was the way to solve the overload, or maybe earlier admin ' had some interesting ideas... '
best regards,
regards
/ Abel
| User | Count |
|---|---|
| 2735 | |
| 1417 | |
| 812 | |
| 739 | |
| 455 |
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.