This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01BFD641.4A87E402 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable 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=E6r [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: >=20 > 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... >=20 > I have tested with TWO different HUBS (one 100MB x 8 ports / actually 10/100 > x 8 ports);=20 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 --=20 Vidar Haugsv=E6r Bergen Kommune, ITseksjonen =20 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 ------_=_NextPart_001_01BFD641.4A87E402 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">RE: [eepro100] Re: [vortex] True on TRANSMIT ERROR = TIMEOUT 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=E6r [mailto:vidar@gs.bergen.hl.no]<= /FONT>
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=E6r
Bergen Kommune, ITseksjonen
Epost: vidar@gs.bergen.hl.no
Tlf: 5556 9971 = Mob: 977 40 525_______________________________________________
------_=_NextPart_001_01BFD641.4A87E402--
eepro100 mailing list
eepro100@scyld.com
http://www.scyld.com/mailman/listinfo/eepro100