My dad says you can go upto 300' away with it, I was assuming it was alot shorter than that.

My mom is fixing to get DSl. Has a puter in the house on one desk with a laptop on the desk next to it. Then, she has a puter in her shop that is prob about 150-200' away, (but I am sure it would take more cable than that to reach)

We had a poneline network, but it ran off the dial up. It is gone now. With the DSL, I recomended a 4 port broadband router. I though she should get wireless, but it is expensive. I looked at phoneline kits on Dlink.com and they all say you will have to have multiple IP's


basically, what can we do? WIll have 2 desktops and one laptop (already has a NIC in it)

I doubt she wants to spend too much on it. I assume, if the cat 5 can really go the distance, a router would be the way to go

Keep in mind, I will prob the the one setting it up. It will be my first network ( I am no networking genius either)

thx!

------------------
www.krawdaddy.net (http://www.krawdaddy.net)
http://www.themelee.com/smilies/s/contrib/sarge/happyNeo.gif
geoffrey@krawdaddy.net
etc.....

No, phoneline networks work just fine on Cable, I know that for fact. DSL should be just the same.

One computer is the "server" which is attached to the incoming internet connection, and also has the phoneline network card. Depending on the NAT software, you need to configure it so that your internet is through the server machine. Whether its a Sygate/Dynanat or a Win ME/2000 connection sharing, you can do it. Set up each machine with an internal ip such as 192.168.0.2 to whatever, and the server machine will have two tcp/ip entries. The first entry will be for the ethernet card attached to the modem, and leave that on auto detect (unless told specific settings by your provider) while the tcp/ip settings for the phoneline modem will have the ip of 192.168.0.1.

I'm pretty sure that'll do it.

You need line filters on lines for phones that are connected to lines used for DSL, so you'll need to connect all the computers to phone lines that have not been filtered. I plugged a line splitter into the wall jack, to make two jacks. From there one line is filtered for the phones, and the other one is not for all the computers. There are other ways to do this, but I guess I just like wires hanging all over my house... It gives it character, ya know. http://discussanything.com/Ubb/biggrin.gif

The maximum length for Cat-5 cables is 300 feet. If you place your hub halfway in between the systems attached to it, you can get 600 feet. A friend of mine has done that, and it works great. He has one computer in his garage, and another in the living room of his house, and he mounted the hub on the wall by the back door of his house. The computers are actually only 500 feet apart, and he has excess cable over what he needs, but he's using two 300 foot cables. He said the store he got his cables in had Cat-5's in 25, 50, 100, 200 and 300 foot lengths. No 250 though...

Sygate Home Network will eliminate the need for multiple ISP's or IP addresses.

------------------
Take Only Pictures, Leave Only Footprints.

No IP, that doesn't seem right. Linksys has routers that are plug and play if you have recently designed NIC cards. The user isn't aware of the IPs their computers have but they're still there.

Well, you COULD run cat5 cable...

It would work. 300ft. isn't a limit, just you start getting degredation of speed.

Wireless IS the ideal way to go in your situation...but make sure that is reaches that far! Som wireless routers are VERY picky.

------------------
Manu Narayan

That isn't quite what I meant to say. What I meant was "Sygate Home Network will eliminate the need for multiple ISP's or multiple IP addresses" because when you set it up you set your NIC with two "Network Adaptors". One for the Internet, and one for Local Networking. For the Internet, you set the Network Adaptor to automatically get an IP address from your ISP, and for the Local Network Adaptor you set a specific IP address. Myself, since I have three system in my network, I have set this to 90.0.0.1 for the server, and 90.0.0.2 and 90.0.0.3 for the other two systems.

In the Sygate docs it says to set these IP addresses to 192.168.0.x, as slayr420 mentioned, but I had already assigned it to these addresses before I installed Sygate, so I left it like it was, and it still works. It's just a suggested address assignment, based on a range of acceptable addresses.

The Sygate website states: "You don't have to use IP addresses specified by Sygate. If you want to define your own TCP/IP settings, you should use settings reserved for private networks by the Internet Assigned Numbers Authority (IANA) as defined in RFC1918."

Go to RFC1918 (http://www.faqs.org/rfcs/rfc1918.html) for more information.


3. Private Address Space

The Internet Assigned Numbers Authority (IANA) has reserved the following three blocks of the IP address space for private internets:

10.0.0.0 - 10.255.255.255 (10/8 prefix)
172.16.0.0 - 172.31.255.255 (172.16/12 prefix)
192.168.0.0 - 192.168.255.255 (192.168/16 prefix)

We will refer to the first block as "24-bit block", the second as "20-bit block", and to the third as "16-bit" block. Note that (in pre-CIDR notation) the first block is nothing but a single class A network number, while the second block is a set of 16 contiguous class B network numbers, and the third block is a set of 256 contiguous class C network numbers."

Hope that clears any confusion... http://discussanything.com/Ubb/smile.gif


------------------
Take Only Pictures, Leave Only Footprints.