Forum Discussion
Hamish
Jul 15, 2014Cirrocumulus
Sure sounds like the 300 second idle timeout for TCP connections.
To verify, dump the connection table for the connections and watch the idle time (Compare it to the Idle Timeout). You'll see it hit 300 seconds (Or whatever the idle timeout is set to) and then should get a reset.
Assuming it is the idle timeout, then to fix, just create a new tcp profile with a longer idle timeout. That assumes you really DO need a longer idle time... The reset could simply be a symptom of something else and is reaping bad connections for you.
H