I have a customer that still uses Thinnet (10base2) and has been having issues with his network. There are random crashes. I was hoping to bring in a Windows 2003 Server Box (that's all I have) with Wireshark installed and hook it up to the network using a media converter and let it analyze all traffic throughout the week. My understanding of 10base2 is limited. But I am assuming it still uses the same protocols. But I wanted to make sure this "solution" won't cause any network issues. Thanks all! This question is marked "community wiki". asked 10 Nov '10, 08:53  ralphy006 |
2 Answers:
All that 10Base2 affects is the media - thinnet and coax. As long as the adapter you are using can be seen by Wireshark then you can capture traffic. Most likely the network is using a protocol set that Wireshark dissects. Check Help > Supported Protocols in Wireshark to see the list. answered 10 Nov '10, 09:47  lchappell ♦ |
When troubleshooting 10Base-2 problems, the following list will typically find the "random" crashes. 1) T connectors with cracks in them. I'm sure no one makes TDRs for 10Base2 anymore so you'll have to visually inspect every one of them. Good luck with that! 2) Terminators that are marginal. You'll probably have to hit ebay to see if you can guy some terminators. If you have a university near by, it may be worth your while to see if any of the network guys have old terminators in their drawers somewhere. Worth a shot. 3) Someone extended the T connector by adding another length of cable. Each T connector must connect directly to the NIC. You can't have a cable running from the NIC to the T connector. This is a long shot, but see if anyone is bringing in a hub with 10Base-2 -> 10Base-T conversion built-in. I won't elaborate for now since it's a long shot. If they have something like this, the troubleshooting path will take a different course. For example, Digital used to make a box called DELNI that did this. With the cost of modern day equipment, I cannot believe they are still running thinnet. My last conversion from NW2.2 running Arcnet to Ethernet was late nineties for a Holiday Inn in Wisconsin. IF they decide to convert, make sure you spec PLENTY of time for the conversion. I had to spend an extra night in the HOliday Inn because I forgot how slow NW2.2 and Arcnet was.....grrrr. answered 11 Nov '10, 08:36  hansangb |
ARCnet! I love it, Hansang! Remember G-net and Omninet? Eeek - I feel old!
I still remember being floored by how slow it was to copy things. we get spoiled so quickly with newer technology that it's very easy to forget "how it used to be" I still remember telling the manager, "oh the drive is so small it won't take long at all to migrate the data" I had my handy dandy (and trusty) JRB Utilities so I thought I'd be out of there in in no time at all. IT TOOK SO LONG!!!! On their PCs, I was able to type "DIR" and READ the lines as it went scrolling by. Unreal that my HTC phone probably has more computing power that our servers from a decade and a half ago.
You guys should write a book or something... ;)
You still run across ARCnet in, of all places, the building automation (think door controls, HVAC, etc.) world...
I still keep an old 3Com EtherLink PCMCIA in my backpack just because its dongle supports 10Base2 - you never know...