[isalist] Re: Question and confesion.
- From: Jim Harrison <Jim@xxxxxxxxxxxx>
- To: "isalist@xxxxxxxxxxxxx" <isalist@xxxxxxxxxxxxx>
- Date: Wed, 3 Feb 2010 12:23:06 +0000
4 hours?!? On what basis does this particular individual offer this sage (or
terragon) advice?
wattamaroon...
Let them reconnect. If hte application itself needed that much time, it can be
built to send "heartbeats", like any other appli cation that expects a long
idle time (EAS clients, ferinstance)
Asking to "leave a port permanently open" is asking for a DoS.
________________________________
From: isalist-bounce@xxxxxxxxxxxxx [isalist-bounce@xxxxxxxxxxxxx] on behalf of
D PIETRUSZKA USWRN INTERLINK INFRA SHIFT MGR [DPietruszka@xxxxxx]
Sent: Tuesday, February 02, 2010 11:22 AM
To: isalist@xxxxxxxxxxxxx
Subject: [isalist] Question and confesion.
OK, first the confession:
I’m migrating to TMG (well no for own decision but…..)
Now the question and is not related to that migration.
Our users needs to use an application that goes over internet on port 7778 (the
number is not really important but..), the problem is, my users work on this
application and then they decided to take a coffee in the kitchen living the
app opened. Since is an internet connection, the connection just become
disconnected for inactivity, then the user come back click on some option of
the app and receive an error, this is because the application doesn’t have the
capability to reconnect.
What the provider suggest is to increase the timeout for that particular port
to 4 hours. My question is: Is there a way to do that on ISA (still 2006)?
Thanks
Regards
Diego R. Pietruszka
Other related posts:
