Client timeout during 3270 terminal emulation

[rimas]

Hi!

Now that I have my DNS resolution problem resolved (no pun intended...), on to the next problem: my clients' 3270 terminal emulation sessions timeout and get dropped after a minute or two.

Here is my topology:

PC1 - Win XP running WinGate
PC2 - Win XP running as client of PC1
Mac - Mac OS X running as client of PC1

I am evaluating PowerTerm InterConnect for Mac OS X, and I find that after a minute or two of inactivity, the session get dropped. I tried another 3270 terminal emulator (TN3270) on the same machine and I got the same results.

To see if the problem is isolated to the Mac, I tried yet another 3270 terminal emulator (IBM Personal Communications) on PC2 and I got the same results.

To further isolate the problem I tried running the VPN software (AT&T Network Client) on PC2 instead of PC1, and lo and behold, my connection is rock solid, even after almost an hour of inactivity. (Note that PC2 is still using PC1 as its gateway in this case.)

So, I am guessing that WinGate is timing out the 3270 terminal emulation sessions due to inactivity. Does this sound right? If so, (how) can I configure WinGate not to do so?

Thanks,

Rimas

[adrien]

Hi

Yes, it sounds like WinGate is timing it out.

If the connection is being made using Network Address Translation (NAT), then you can override timeouts on a per port number basis by using the port security settings in Extended Networking in GateKeeper - add an entry, specify the port number the service is using, and set the timeout.

Adrien