Idle Session Disconnection 2

[johnd]

Hi,

I've got a support query outstanding in a topic called "Idle Session Disconnection". It looks like it's been forgotten about.

Can anyone update me please?

Cheers
John

[MPHinteractive]

I recently upgraded one of my clients, a library, from Wingate 5.0.? to 5.2.3 and then encountered the same problem. They use a library software client that connects to a server based in another state on TCP port 2574. After the upgrade the client would loose its connection and quit if left idle for around four minutes.

This happened even when I created a TCP mapped port service and set sessions never to timeout, then redirected the library client to the local mapping service instead of using NAT/ENS to catch and forward a direct connection to the remote server.

I have implemented the suggestion by Wingate tech support in the earlier thread... Under Extended Networking, Port Security tab, "add" a permission for machines on the local LAN to access the internet/port range 2574-2574/allow packets/never timeout.

I was perplexed for a minute that the service did not appear on the Port Security screen after I added it, but realized that I had to use the pull-down menu to look at outbound (LAN to internet) connections.

Preliminary testing seems to indicate this solution worked for us. We're running Wingate 5.2.3 on a fully patched Windows 2000 Pro client dedicated to firewall duty. Our external connection is a T1.

Thank goodness for the forums! John, I hope they come up with a solution for you soon...

Park Hunter, MPH Interactive

[johnd]

Thanks Park. I've tried that approach, but it doesn't work here. Just for good measure, I tried it again just now, in case I'd missed something the first time, but no luck.

The guys at Wingate were supposed to be setting this up in their test labs. Any progress on that folks? Pascal?

Cheers
John