[tulip] RE: [eepro100] Re: [vortex] True on TRANSMIT ERROR TIMEOUT

[David Ford]

This is a multi-part message in MIME format.
--------------5E658A96AE31CA4ECAAA5079
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Yes, iirc, it is improperly implemented NWAY negotiation.

I use and have used numerous switches.  Working with NSP/ISP groups that
traffic terabytes a day, hubs are paperweights to hold the trash in the
trash can.

Switching is overwhelmingly more advantageous than doing hubs.

-d

Philip Ronzone wrote:

>
>
> I'd recommend AGAINST using switches. The unfortunate, and frustrating
> reality is the many Ethernet NICS do NOT work well with switches when
> the NIC is set to something OTHER than autonegotiation (like, set to
> 100BASE/half-duplex). Intel has acknowledged that they can replicate
> this problem and so far, have some rational hypothesis for why it
> happens.
>
> These problems do NOT occur with hubs.
>
>
>
> -----Original Message-----
> From: Vidar Haugsvær [mailto:vidar@gs.bergen.hl.no]
> Sent: Wednesday, June 14, 2000 10:18 AM
> To: Daniel Soto Alvarez
> Cc: eepro100@scyld.com; vortex@scyld.com; tulip@scyld.com
> Subject: [eepro100] Re: [vortex] True on TRANSMIT ERROR TIMEOUT
>
> Daniel Soto Alvarez wrote:
> >
> > The problem are the continuos TRANSMIT ERROR (timeouts) in the
> network. To
> > test the network I make 'ping -t server' in any Windows client, and
> when
> > 'transmit timeout' occurs I need to manually restart the HUB. With
> this the
> > network restart, and we can continue out job. This problem occurs
> randomly:
> > days no, days little, days heavy...
> >
> > I have tested with TWO different HUBS (one 100MB x 8 ports /
> actually 10/100
> > x 8 ports);
>
> What kind of HUB are you using? Using a combined 10/100 HUB is like
> begging for trouble. You should really be using a switch instead.
> There
> are many reasons for using a switch instead of a plain old HUB
> nowadays.
> Remember to get a switch with a management module, so you manually kan
>
> check status and set port parameters (forcing full-duplex).
>
> You could also try manually setting _all_ your network devices
> connected
> to the hub to 10baseT half-duplex to see if that changes the
> situation.
> If it does, your problems most surely is related to the hub, which
> they
> must surely are anyway.
>
> Oh...BTW: did i remember to advise you to use a switch instead of a
> combined 10/100 hub (?) :-)
>
> Regards
>
> Vidar
> --
> Vidar Haugsvær
> Bergen Kommune, ITseksjonen
> Epost:  vidar@gs.bergen.hl.no
> Tlf: 5556 9971          Mob: 977 40 525
>
> _______________________________________________
> eepro100 mailing list
> eepro100@scyld.com
> http://www.scyld.com/mailman/listinfo/eepro100

--
"The difference between 'involvement' and 'commitment' is like an
eggs-and-ham breakfast: the chicken was 'involved' - the pig was
'committed'."



--------------5E658A96AE31CA4ECAAA5079
Content-Type: text/x-vcard; charset=us-ascii;
 name="david.vcf"
Content-Transfer-Encoding: 7bit
Content-Description: Card for David Ford
Content-Disposition: attachment;
 filename="david.vcf"

begin:vcard 
n:Ford;David
x-mozilla-html:TRUE
org:<img src="http://www.kalifornia.com/images/paradise.jpg">
adr:;;;;;;
version:2.1
email;internet:david@kalifornia.com
title:Blue Labs Developer
x-mozilla-cpt:;-12480
fn:David Ford
end:vcard

--------------5E658A96AE31CA4ECAAA5079--