- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Session Killed by Firewall
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-28-2002 02:48 AM
05-28-2002 02:48 AM
Session Killed by Firewall
I have a problem with a firewall. I'm executing a ksh script through a remote session but we have got a Firewall. This firewall kills any sessions whom is 7000 seconds inactive. The problem is I execute this script but it delays more than 7000.
Anyone knows how I can keep my session alive?, If I execute a echo, It could run?
Thanks a lot.
David.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-28-2002 02:53 AM
05-28-2002 02:53 AM
Re: Session Killed by Firewall
Using echo is a right solution. Is it possible to run your script in background ?.
regards,
U.SivaKumar
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-28-2002 02:54 AM
05-28-2002 02:54 AM
Re: Session Killed by Firewall
You could use echo, or a ping, or run the script on the remote server using nohup so even if the firewall kills your session the script will continue to run.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-28-2002 02:56 AM
05-28-2002 02:56 AM
Re: Session Killed by Firewall
Bill Hassell, sysadmin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-28-2002 03:09 AM
05-28-2002 03:09 AM
Re: Session Killed by Firewall
Yes, echo statements in your script will work just fine to prevent the idle timeout. This works because the echo output is transmitted across the network through the firewall from your HP-UX server to your client PC where it is displayed.
As a result, your session is never idle as long as the period between echo statements is < 7000 secs.
Hope this helps. Regards.
Steven Sim Kok Leong
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-28-2002 03:12 AM
05-28-2002 03:12 AM
Re: Session Killed by Firewall
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-28-2002 03:18 AM
05-28-2002 03:18 AM
Re: Session Killed by Firewall
Have you tried using rlogin and executing the script ?. Any difference ?.
Also try remsh also.
regards,
U.SivaKumar
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-28-2002 05:55 AM
05-28-2002 05:55 AM
Re: Session Killed by Firewall
It is important to know the difference between "session connection time exceeded" and "idle timeout".
For "session connection time exceeded", the firewall will cut off your connection regardless of whether your connection is idling or not. It limits the total duration of a session.
For "idle timeout", if both the firewalls are implementing "idle timeout", then your session should NOT be cut off as long as the period between your echo statements are less than the "idle timeout" durations implemented on both the firewalls and also less than the tcp_keepalive_interval configured on the HP-UX server.
Hope this helps. Regards.
Steven Sim Kok Leong