×
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.
Where were the devices attached that could not connect? Where were the
devices attached that could still connect? Your problem was in between.
Chris Bipes
Director of Information Services
CrossCheck, Inc.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Burns, Bryan
Sent: Thursday, December 06, 2007 1:44 PM
To: Midrange Systems Technical Discussion
Subject: RE: Switch on Network and Looped to Itself Crashes Client
Access
What do you think was overloaded? Some say the iSeries Ethernet
adapter.
Low end 4PORT 3COM switch (with loop) ---HP ProCurve Switch ---- Cisco
3570 switch ----- iSeries adapter
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Chris Bipes
Sent: Thursday, December 06, 2007 3:08 PM
To: Midrange Systems Technical Discussion
Subject: RE: Switch on Network and Looped to Itself Crashes Client
Access
Not necessarily. You connection was fine but you probably did not get
any traffic to the iSeries do to your switch being overloaded with the
looped traffic. Nice thing about switches, they do not send unnecessary
traffic down all ports.
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
