As the Mythbusters like to say, "Busted." The firewall guys tell us that there is not a single firewall between point A (VM) and point B (MVS). Both are on the same internal network. The only firewall is between it and the outside world.
Tracerte is not very helpful, either. It seems to confirm what the firewall guys said. tracerte mvs1 Trace route to MVS1 (xx.xx.xx.xx) 1 (yy.yy.yy.yy) 29 ms 0 ms 1 ms 2 MVS1.visa.com (xx.xx.xx.xx) 4 ms 1 ms 1 ms What is the difference between the NJE keepalive and the RSCS keepaliv=yes? We have tried both =yes and =no to no effect. We have been running with keepalive turned on for 48 hours. The same errors show up like clockwork when the link is idle for an extended period. Regards, Richard Schuh -----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of David Boyes Sent: Wednesday, June 13, 2007 5:50 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: TCPNJE > Interesting thought. Isn't the keepalive packet supposed to prevent that > from being a problem? In theory, yes, but some firewalls try to be "smart" and look for simple repetitive traffic. A traceroute to determine a good sample of exactly how the packets are traversing the network might be a good next step. Then at least you'd have some idea of how A gets to B, and what might be in between. You might also try turning on the NJE keepalive -- wastes a little bandwidth, but that *definitely* doesn't look like repetitive traffic generated by J Random ScriptKiddie.
