Re: Anybody ever heard of an E4B having weird TCP issues?

["Jim Franz" <franz400@xxxxxxxxxxxx>]

Lots of stuff can change between different hardware.
Same OS (must be 6.1.1 or 7.1) ?
Same ptfs (not just cume but hipers & groups)
Same ethernet hardware config?
Same tcp config?
Any packet filtering?
Any new security turned on?
Same switch>routing>firewall?
That's a lot of stuff that "should" be the same.
While verifying the above (if the old hardware still around) start some 
traces.
Jim Franz

----- Original Message ----- 
From: "James H. H. Lampert" <jamesl@xxxxxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Monday, November 22, 2010 6:29 PM
Subject: Re: Anybody ever heard of an E4B having weird TCP issues?


> I wrote:
>
> > At any rate, this client seems to have developed strange issues,
> > immediately upon migrating to the E4B, anytime a write or update request
> > is processed. Supposedly, nothing has changed but the physical midrange 
> > box.
>
> Oops, I didn't mean the client program. I think I meant the customer and
> their box.
>
> At any rate, more information: if the client-server connection actually
> gets shut down, a passive diagnostic gets tripped, one I put in over a
> decade ago, that only trips if, while the server program is waiting for
> the requisite number of bytes to arrive, goes a full minute without so
> much as a single new byte arriving.
>
> --
> JHHL
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
> list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.