techguyinohio :
dieselboy-
Hey thanks for the help on everything.. after investigating with IBM a couple things, it turned out to be a combination of the ispection rules on the firewall as well as the ibm client access terminal sessions keep alive needing added to each computer's config file. and updating the TCP/IP in windows registry to add the line KEEPALIVETIME=60000 for (60 sec) decimal
Everyhing is up and running normally now.. I appeciate the insight and have saved all the info if anyone else needs, or runs into this problem with remote connections back through to an AS/400, or similar using a client access product, etc.
Thanks again.
TechGuyinOhio
Hey thanks for the help on everything.. after investigating with IBM a couple things, it turned out to be a combination of the ispection rules on the firewall as well as the ibm client access terminal sessions keep alive needing added to each computer's config file. and updating the TCP/IP in windows registry to add the line KEEPALIVETIME=60000 for (60 sec) decimal
Everyhing is up and running normally now.. I appeciate the insight and have saved all the info if anyone else needs, or runs into this problem with remote connections back through to an AS/400, or similar using a client access product, etc.
Thanks again.
TechGuyinOhio
Can you tell me what changes you made to the inspection rules?