🚀 go-pugleaf

In article <6r4p9s$39m$1@sol6.tvd.be>,
"Simon Hampton" <simon.hampton@tvd.be> wrote:
>
>mike.luther@ziplog.com a �crit dans le message
><6r48a6$ii2$1@news2.myriad.net>...
>>When I finally gave up on thin net and went to 10bT or CAT-5, and got
>>the EXACTLY right driver from the vendor for my cards, my system came
>>alive POOF!  Without a hub and all NOTHING.
>>
>
>Did you need a special kind of wire for a thick connection.  The only reason
>I bought the coax was because I thought it was going to be very hard to buy
>so=called crossover UTP cable.  Have I made  another mistake.
>
>How do you make a card use the the thin ethernet port rather than the thick
>port?

The difference between thick and thin ethernet, is the type of coaxial
cable used.  Thick uses RG8 cable which is about 0.5" in diameter and 
thin refers to RG58 cable (0.2").  Also, thick networks used 
transceivers attached directly to the cable with a cable similar to 
twisted pair going a 15 pin connector on the NIC.  From an electrical
point of view, you could in theory use a T connector with thick cable
in the same manner as thin ethernet, but you'd then have two of the
larger and less flexible cables coming to the computer and also have
mechanical problems in connecting the cable to the T connectors.  With
10Base2 (thin ethernet) and 10BaseT (twisted pair) the tranceiver is 
located on the NIC.  Thick ethernet is known as 10Base5.

Cross over cables are easy to make, provided you have the proper tool 
for the RJ45 connectors.  Some stores also carry them.  Another trick 
I've seen is to buy a box with two RJ45 sockets and do the cross over 
in it.  You'd then have a two port "hub".  A friend of mine did 
something similar when he networked two computers in ajoining rooms. 
He simply put a jack in each room and performed the cross over between
the two jacks.  To create a crossover, connect pins 1&2 at each end to
3&6 at the other end.

Hope this helps.

-- 
E-mail jknott@ca.ibm.com
_________________________________________________________________________
The above opinions are my own and not those of ISM Corp., a subsidiary of
IBM Canada Ltd.