mebedave
Well-known member
My shop is about 200' from my house. Can I run an ethernet cable from my router in my house to my shop for internet access,or is that too far?
i wouldn't just run one either... cables fail.
+1. Hell, +2.True, but even on their worst day, copper cable beats wireless.

No, it won't. The only reason ethernet ever slows down is from poor connections or insufficiently rated cable. A 200-foot run with Cat6 cable and a router/switch at both ends will pose no speed limitation at all. Fiber's fine, but rather costly and unnecessary unless you need extremely high speeds (way over gigabit) or very long runs (thousands of feet).200 ft may slow it down a bit.
I don't understand. I know length = resistance, but doesn't the signal come off cable strung for miles? Are there boosters? For within the home?
What happens is if the cable is too long, the signal to noise ratio becomes too high and the equipment is unable to work with the signal.
The signal eventually attenuates and you get dropped/lost packets or even interfaces going up/down at random.
I would run it directly from a good quality router or switch to same on the other end, to ensure a clean signal. Not all ethernet ports/cards on equipment are as robust as those in routing gear. It may seem like overkill to run it from, say, your cable or DSL modem to an adjacent switch, then through the long run to another switch, and from there to a computer, but it will improve your reliability and transfer speeds.
Cat 5e and Cat 6 are virtually the same price in small quantities (= 1 spool). It might be worth using only the grade needed for a commercial installation, but if you're going to go buy a spool, it's hard to argue against the slightly better characteristics of 6, essentially for free.Cat6 cable won't have any advantage for these distances.
I would run it directly from a good quality router or switch to same on the other end, to ensure a clean signal. Not all ethernet ports/cards on equipment are as robust as those in routing gear. It may seem like overkill to run it from, say, your cable or DSL modem to an adjacent switch, then through the long run to another switch, and from there to a computer, but it will improve your reliability and transfer speeds.
You can't string Ethernet for miles. 328' (100m) @ 100BASE-T and 1000BASE-T with Cat5 shielded and up. If you need to go farther, you convert to something else. Miles would be single mode fiber. They sell various extenders or you could use a cheap router or switch but that will peter out somewhere between 1000' and 8000' or so.
if you are running it outdoors of even burying it you should get the underground cat 5 or 6. It is designed to withstand the elements.
The maximum length of a cat 5 or 6 run from what I have read is 328' More than that you suffer bandwith problems.
i wouldn't just run one either... cables fail.
I guess if connecting his shop is worth a four-figure bill...I would run fiber between the buildings then use a transceiver to connect up to the switches. Switches like the cisco catalyst or HP procurve.

Absolutely correct. Ethernet has the 100meter limit. To run a cable for miles, you need a different protocol from ethernet. Ethernet is a digital signal for computers.
DSL can be run for miles because it is an analog signal to a modem. DSL is a totally different world from ethernet. Even through DSL stands for digital subscriber link, it uses an analog modulated signal to carry the digital signal. This is where we get Modem (modulator-demodulator), and the ethernet protocol isn't modulated like DSL.
I guess if connecting his shop is worth a four-figure bill...![]()
Wireless works fine if you use good gear and set it up right.True, but even on their worst day, copper cable beats wireless.
Regarding cable....Cat5E has the same freq limit as Cat6. Cat6 is just spec'd for noisy installations....like running it in a cable tray with AC.
Nope. Ethernet's length limitations on copper have nothing to do with signal degradation or quality.
It actually has to do with the speed that the signal propagates over the wire.
Data is transmitted in discrete packets, with a pause between them, and the sender must wait for a response. Packets have a maximum length, because a response is expected in a fixed window of time. As the wire length increases, it takes longer for the packet to reach the destination (and for the response to return). After a point, the packets take too long to return, and the network fails.
10BaseT has ten times the bit timing, so it can effectively work over ten times the length. If you're cable is borderline long, you can switch your system to use 10BaseT, and that should fix it.
Cat6 cable won't have any advantage for these distances.
Now, if you're running 1000BaseT, then there -can- be a difference between Cat5 cable (and connections), and Cat5e. Cat5e will work for 1000BaseT, whereas Cat5 will more than likely work, for shorter runs.
ahhhh what kind of OEM are you buying?Most OEM NICs and equipment ports are for the cheapest short-haul use, like ten feet to the switch.
Absolutely correct. Ethernet has the 100meter limit. To run a cable for miles, you need a different protocol from ethernet. Ethernet is a digital signal for computers.
Cat 5e/6 cable is about 8-10 cents a foot even at retail spool price. Running two or three lines for redundancy is the cost of one spool or even less.Fiber is cheap, you will spend more money on the conduit to protect it than the fiber itself.
Yeah, I love that Chinese **** - you can always spot it from the weird typeface they use. I don't know of any decent fiber converters for less than about $100 - and those are single-port, meaning (tadaaaa!) he's going to need a switch on each end anyway. Or at least one.Just need two of these:
http://www.ebay.com/itm/330623168589
