As I see it, increasing the SA life value is not a solution. Whatever that value is, it will at some point time out and thus disconnect a teerminal services connection. This is to me unacceptable and needs to be ssorted out by GTA support. For me and my company the product is useless with a 20 sec timout, independent of how often thsi occurs.
I have heard from my Swedish Gnat Box supplier here in Sweden that the renegotiation should only take 3-5 sec. Can anyone verify this for me and what is the GTA tech support reply to this problem?? Do they read this at all? /U -----Original Message----- From: RSR FL [mailto:[EMAIL PROTECTED]] Sent: den 14 februari 2002 22:51 To: Brian Fort (Mushkin); Urban Sterner; [EMAIL PROTECTED] Subject: RE: [gb-users] VPN and MS Access Problem I've thought about upping the SA life but one thing you run into is if the connection or PC gets rebooted/dropped then you can not connect via the VPN until the balance of that life expires. So if it drops right after a rekey then they must wait 50 minutes before connecting. Once I'm sure they have a stable connection I will probably up it. I'll check out the site and see if it helps. Let you all know results. Thanks again. Mike -----Original Message----- From: Brian Fort (Mushkin) [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 14, 2002 1:10 PM To: Urban Sterner; 'M Pilletere'; [EMAIL PROTECTED] Subject: RE: [gb-users] VPN and MS Access Problem I've set the SA Life for my clients to 3000 seconds so they only get cutoff from network connection dependent applications like Terminal Client every 50 minutes. I believe you can set the SA life much longer but you need to realize that your VPN Licenses will be used for that complete 50 minutes so if multiple people share licenses then it may cause problems if you set the SA Life to long. Also, I think you need GB 3.2.3 in order to set the SA Life longer than 600 seconds. Terminal Services/Clients is most definitely the way to go. Downloading over the VPN gives me about 1/4 the bandwidth I would normally get, but when working on a Terminal Client everything's pretty smooth. You may want to try optimizing Windows for networking over the Internet. One site I know of that can help with this is http://www.speedguide.net/Cable_modems/cable_reg_win2k.shtml. I haven't tried this personally, so I would love to know if you get good results! -Brian -----Original Message----- From: Urban Sterner [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 14, 2002 8:22 AM To: 'M Pilletere'; [EMAIL PROTECTED] Subject: RE: [gb-users] VPN and MS Access Problem I have the same problem, key renegotiation takes 16-22 sec and that is enough to make my terminal services clients to time out. This is something that is unaccaptable and I am hoping to get some help from support but none yet. /U -----Original Message----- From: M Pilletere [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 13, 2002 23:53 To: [EMAIL PROTECTED] Subject: [gb-users] VPN and MS Access Problem Wondering if anyone is doing this? Have a VPN client connected via a cable modem to our office GB Flash which has a full T. We can telnet without a problem but when we map a drive that is at the office and then try running access with a 15mb database we get problems. 1. Slow performance (ping times average 100ms) 2. Every time the key is renegotiated access generates errors. I have turned off in access the "refresh database every xx secs" option, that helped. Is the database just to large to work over a VPN or is it something else? Any thoughts or suggestions? Thanks Mike RSR Group, Inc. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] To subscribe to the digest version first unsubscribe, then e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
