Quote:>|THis has always puzzled me. If I discount distance as being a problem, and the
>|cost of a hub is not a problem, WHY would I ever use 10base2 wire for a net with
>|it's enherrant (SP??) problems of expense and total loss of net if one WS goes
Well, one reason is because 10BASE-2 was around five years ago and 10BASE-T
wasn't. Your reasons are certainly valid for a new installation.
Our building lease is up in Feb of '96 but we're moving out a little early.
Two years ago we knew we wouldn't be renewing the lease, so management was
understandably reluctant to replace the 10BASE-2 we put in seven or eight
years ago with Cat 5 UTP. Of course, this stupid thinnet is giving us
more and more problems as we get closer and closer to moving out. Ironically,
our new office space has thinnet already installed, but I am 95% sure I will
get approval to have it replaced with a Cat 5 UTP installation. If not, I'm
going to look for a new job because no one in 1995 should be wasting their
time hunting down problems on a large thinnet network.
Quote:>There's only one application where IMO 10base2 makes sense:
>where you've got a very small number of nodes that are all
>in extremely close proximity, and where clueless users won't
Amen to that. I've seen users come up with some very creative
topologies for thinnet networks, given a few T connectors and a
few transceivers with two BNC connectors. I saw someone make
a network shaped like an "H" once (no repeaters or bridges). Even our
sys admins don't know the rules; they go over the 30 tap per segment
limit, and I have seen them connect two routed subnets together.
Quote:>Note: a 10base2 segment does NOT go down just because a station
>goes down - but it does if the person attached to that station
>decides to disconnect the network.
But a bad T-connector or bad transceiver will bring down the whole
segment. I even had a terminator go bad a couple weeks ago and bring
down a segment.