Yes, VPN stays up.
We even started a ping to an IP on the same subnet. Ping never blinked but at 4 minutes the Telnet session dies. I just spoke to TGA (Shook you know who I'm referencing) Jim stated: /QUOTE There is a timeout value for NAT translations and packet streams.. Here are the defaults from a configuration. timeout xlate 3:00:00 timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02 timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00 mgcp-pat 0:05:00 timeout sip 0:30:00 sip_media 0:02:00 sip-invite 0:03:00 sip-disconnect 0:02:00 timeout uauth 0:05:00 absolute /QUOTE He will look into that in an hour or so. ________________________________ From: Andy Shook [mailto:[EMAIL PROTECTED] Sent: Thursday, May 01, 2008 8:26 AM To: NT System Admin Issues Subject: RE: Time out issue Do you have keep alives setup on the tunnel to the left coast? In other words, when the app dies, is the VPN still up? Shook ________________________________ From: Tom Strader [mailto:[EMAIL PROTECTED] Sent: Thursday, May 01, 2008 8:22 AM To: NT System Admin Issues Subject: Time out issue Guys and Ladies, I've got a problem that we cannot seem to resolve and need the knowledge of you fine folks. We provide application access to a remote site through a dedicated VPN. The application itself on OUR side is provided to US through another dedicated VPN to the California vendor hosting the application. At exactly 4 minutes (240 seconds), the telnet session this application uses terminates. We've checked all routing devices and cannot find any parameters set to 240 seconds. Power Management is turned off at all devices. We've called the application provider; they state there are no settings on their side either. This one remote site is the only one experiencing this anomaly. Any suggestion as to what might be causing this is appreciated. Thanks in advance, Tom ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
