On 9 Nov 2005 13:32:21 -0800,
(E-Mail Removed) wrote:
>I know that the official distance that CAT5e can run is 100 meters; to
>read some web sites, you'd think that an attempt to go 101 meters would
>be a catastrophic failure. Some imply that to violate the natural
>order of things by running it further is to invite divine retribution.
>
>But surely CAT5e can go more than 100 meters? Perhaps at reduced
>speed? I don't need 100 mbps; 10 mbps would be fine as the bottleneck
>is a shared 1 mbps internet connection. If ~150 meters is OK, but at
>10 mbps, will my dumb 10/100 autosensing switches be smart enough to
>fall back on the slower speed? Would I be better off using a new high
>quality 10/100 switch that tries to make 100 mbps work, or an older 10
>mbps only switch that forces the connection to the slower speed?
The correct newsgroup is comp.dcom.cabling. I posted articles there
on the topic before.
You're on the right track. One of my fun demonstrations is to put
connectors on both ends of a 1000ft roll of CAT5, plug it into my
office LAN switch and my laptop and surf merrily. No error shown on
the SNMP statistics in the switch. I also have several installations
using CAT5 at about 800ft which work just fine. I'm not sure exactly
what is the maximum, but my guess is about 1200ft.
As usual, there's a catch. You should use a switch or dedicated NIC
port on both ends. 10baseT-HDX (half-duplex) only. Don't bother
trying it with 100baseTX. It won't work. 10baseT-FDX (full duplex)
is problematic because of NEXT (near end crosstalk).
The orthodoxy in comp.dcom.cabling will claim that the rules are the
rules and that 100 meters was selected to insure that it will always
work under all circumstances. They are correct. I can create
situations where 10baseT-HDX will NOT work at much over 100 meters.
Examples on request. However, if you're careful, you shouldn't run
into any of these.
Your dumb and unspecified 10/100 NWAY switch will NOT guarantee
10baseT-HDX. It will start at the highest speed and stay there. To
force it down to 10baseTX, the easiest way is to insert a cheapo
10baseT hub (not switch) in the line. That will force both ends to
10baseT-HDX. (Hubs cannot do full duplex).
You might also consider using coax cable. I have one system with
about 1200 ft of RG-6/u coax, using 10base2 to 10baseT media
converters at each end. Works just fine. The 75 ohm to 50 ohm
mismatch is barely noticeable as the high cable loss eliminates any
reflections from being seen at the opposite end. Radio Shock sells a
Type F to BNC adapter which is all you need to make it work with
common CATV coax. Do NOT use RG-59/u. It's usually garbage or worse.
The following thread might be worth reading:
http://groups.google.com/group/alt.i...72743a913d8cb9
Incidentally, if you want to go miles over one twisted pair, it can be
done with SDSL. Some pairs of SDSL modems can talk to each other.
Flowpoint, Lucent DSL-HST, Elastic, PairGain, Xpeed, etc can work
without a DSLAM. 3com and Coppercom, cannot. 768-1500Kbits/sec
symmetrical maximum with the older equipment.
--
Jeff Liebermann
(E-Mail Removed)
150 Felker St #D
http://www.LearnByDestroying.com
Santa Cruz CA 95060
http://802.11junk.com
Skype: JeffLiebermann AE6KS 831-336-2558