× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hi Phil,


> Swapping the devices out solved the problem.  Note: The devices weren't
> faulty.  Swapping them for the same brand/model did not solve the problem.
> I had to swap them with a different brand.  Unfortunately I don't recall
the
> old hub brand but the new brand is from 3Com.  The Cable/DSL router that
> didn't work was from LinkSys and the one that works is from Netgear.

We've now experienced the problem at two different remote locations. The
first was using IBM 8271 Ethernet switches, and the newest location is now
running Netgear FS524 switches. While troubleshooting the problem at the
first location, I changed the IBM switch to an Intel hub, and ended up with
the same result.

The DSL router is Cisco, and the other location is running ISDN, also using
Cisco equipment.

> I think this is because the as/400 stops getting a response from the PC
and
> closes the connection.  The PC, however, isn't aware of this and continues
> to display the screen until you press a key.  Then the PC sends data to
the
> as/400 and then finds the connection no longer exists.

Then, in my mind, the problem is with the AS/400. It sounds like the server
is timing out to quickly, and we should be able to configure that behaviour.
Did IBM ever mention any system values that control that response?


John Taylor







As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.