Paul -- While not a fix, a workaround might be to set up a little .pif file that pings a host on the other end of the tunnel and then run it every 15 minutes (or whatever it takes) using Task Scheduler or some other such mechanism. I set up a batch file here with the statement:
c:\windows\ping -n 1 destinationaddress Then I modified the batch file's properties to run minimized and close on exit. I put the resulting .pif file into the Windows 98 Task Scheduler and set it up to run every 15 minutes for 9999 hours (the maximum, about a year and two months). It's minimally disruptive having it pop up in the taskbar, but a) it's better than having to shut down the tunnel and bring it back up and b) you probably won't have to have it run every 15 minutes. Good luck! Don Nims Network & Security Engineer Lighthouse Technologies & Management Solutions Naperville, Illinois & Rhinelander, Wisconsin www.ltmsi.com From: "Paul Mills" <[EMAIL PROTECTED]> Subject: [SonicWALL]- VPN Client Question Date: Fri, 25 Oct 2002 10:39:00 -0500 Reply-To: [EMAIL PROTECTED] Hey all, I was wondering if anyone has experienced an issue with the vpn client in which it appears to timeout if no activity occurs over the tunnel that the client has established. The main activity that occurs over this tunnel is a telnet session, and if no activity occurs for a while the telnet session appears to freeze. The fix thus far is to shut down the session, shut down the vpn client, restart the client, and then the telnet session. Suggestions would be appreciated. Thanks! --- [This E-mail scanned for viruses by Declude/F-Prot AV] ==================================================================================================To unsubscribe, send email to [EMAIL PROTECTED] In the body of the email put the following: unsubscribe sonicwall your_name The archive of this list is at http://www.mail-archive.com/sonicwall%40peake.com/
