On Sat, 19 Jan 2002, Michael O'Donnell wrote: > I brought a 10baseT-equipped laptop home from work and > tried to connect it to my household 10base2 (thinwire) > Enet with a NetGear EN104 4-port hub.
That should work, or as well as thinwire ever does. I know you didn't ask, but assuming IBM-PC hardware, you should be able to replace the entire thinwire network for less than $100, depending on various factors. Speaking as someone who has had to debug thinwire in the past, do yourself a *BIG* favor and get rid of it. :-) My all-time favorite thinwire problem was a bad tee connection. The *really* fun part was it was *temperature dependent*. When it got warm enough, the tee would start causing problems, and everything would die. Then the room would drop a few degrees in temperature (due to decreased activity) and the LAN would resume working -- only to crash again as things warmed back up. Of course, it was right by the door, so whenever we showed up to debug it in person, things cooled off enough that the problem never manifested itself. It took us *weeks* to track that down. > And the whole time the collision-indicator LED appears > to blink more or less in unison with the Rx LED. I assume you do not have any loops in this network? :-) Could be electrical -- e.g., a bad hub, or a lose connection. Try switching cables, tees, and terminators everywhere. Remember, something slightly out of tolerance at the other end of your segment can cause problems. Make sure the cable shield is grounded properly. It could also be a software problem. If, somehow, a node wants to transmit in response every time it gets a packet from a second node, that might cause problems like what are describing. Check for duplicated addresses, as well as things like two DHCP servers running. Consider throwing a packet sniffer capable of decoding Ethernet frames on the LAN, and see what that shows up. Ethereal is really good for this. Try sacrificing a goat to the Ethernet Gods. -- Ben Scott <[EMAIL PROTECTED]> | The opinions expressed in this message are those of the author and do not | | necessarily represent the views or policy of any other person, entity or | | organization. All information is provided without warranty of any kind. | ***************************************************************** To unsubscribe from this list, send mail to [EMAIL PROTECTED] with the text 'unsubscribe gnhlug' in the message body. *****************************************************************
