Discussion Locked

Connecting a data point

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We have a 10-base-t ethernet network in the office, and we would like to connect a remote point to the network that is almost 500 meters away, We don't want to use RAS and a leased line for a single point is not practical. So we installed an FTP 4 pairs cable from the office to the specific point and we will install a router later on.

I Would like to know if this concept will work before we can invest in a router? and what are the alternatives?

9 replies

by barry hensley

What do you mean by an FTP 4 pairs?

If you ran twisted pair cable, you are over the limit of 100 meters, approx. 330 feet. You will experience signal loss, poor performance, and be very unhappy with the solution.

If you ran fiber optic cable,you're in great shape. Use a 10BaseT to Fiber transceiver in each end of one of the fiber cables (one pair) and your remote node will simply be another node on your network. There is no need to install a router unless you want the remote network to be on a separate LAN. You can hang a 10BaseT hub off the transceiver at the remote site and connect several machines if you need to.

by kevin anderson

I agree with the other poster. 500 meters is too far for copper cabling unless you can put in several repeaters (every 100 meters or so.) If repeaters can work, you're set.

If not, Fiber is your best bet. It allows for huge growth in the future if that station developes into two or three, or a hundred. It will last longer, and is completely resistant to interference. Alternately, you would run Ethernet over Coax, and you'd be close... Thicknet specs are 500 Meters max for a simgle segment. This is shortsighted though. And probablly more expensive than Fiber anyways, since you'll have a hard time finding a NIC that supports it anymore (which means a transciever at each end, etc...)

Run Fiber into a small Fiber hub. and then run 10BaseT from there. In the long run, that will show the most expandability, and the longest useful life.

Or run a fast internet connection to both locations, and run a VPN. In my experience this isn't ready yet for some apps, so try it first. File, Print Email is fine, but Telnet Sessions, etc will be dropped due to the latency inherent in an internet connection.

Kev.
Kev.

by estebandelatorre

Consider Using a single Thick Ethernet Coax between the 2 points, but leave some cable near a power outlet (between 250 and 350 meters), just in case that you need a repeater in the middle.
This will allows you to extend your lan, and runs 10 mbps single LAN.
In boths extremes, you shoud put a Coax to RJ45 conversor, one of those with a big transformer should be used. Don't use an rj45 hub with a coax output, they do not have enought power and you will experience signal-loss.
Consider putting a storm filter in order to protect against electric discharges.
You don't need a router unless you need two separate LAN.
Using UTP cable or SUTP (Shielded UTP) you should add a repeater each 180 meters!

edt@bancobgn.com

by mckaytech

I assume what you have is STP (shielded twisted pair) cable. While it is true that you are beyond the range of Ethernet signaling, you could use a pair of "line-haul modems" to make the connection at some speed less than that.

Whether it is reasonable to do so depends on the intended use. As an alternative to a leased 56k line, it would work just fine and if you're running terminal sessions, print jobs, mail transfers or other uses that leave a light footprint on the network, the performance will probably be acceptable.

If you want to extend full Ethernet speeds across this segment, you'll need fiber or thick Ethernet because even with Category5 cable, you'll run up against the "3-4-5" rule because you would need a repeater every 100 meters and the rule only allows two repeaters on a collision domain.

By the way, there never WERE NIC cards that directly supported ThickEthernet. You used a NIC with an AUI port and plugged a ThickEthernet transceiver into that. Such NICs and transceivers are still out there...
in fact, it hasn't been all that long since our Cisco routers still came with AUI ports rather than the now-standard RJ45 Ethernet connection.

paul

This discussion is closed to new replies.