DSL sharing- Starting from Basics

krish_na22 · Post by **krish_na22** » Tue May 08, 2001 2:22 pm

Hi,
I have recently subscribed for Verizon DSL- got the modem and am waiting for the set up to be completed on Verizon's end.

I want to share the DSL between two computers. Neither of the computers have any NICs and they are in different rooms. They run Win 98 and Win ME respectively and both of them have two USB ports. The computers are in no way networked as of now. Given this what are my options? (Verizon provides me with SINGLE DYNAMIC IP address) I am looking for something inexpensive and easy to install.

Please help me out in this.

GRIM · Post by **GRIM** » Tue May 08, 2001 3:14 pm

1.Get a couple nic's
2.Purchase another ip or 2
3.Buy a router( I would go with this one)
4.Use ICS ( last resort)

Dement · Post by **Dement** » Tue May 08, 2001 3:24 pm

I go exactly with what your saying, I would invest the $100 bucks on the router. Just so I didn't have to mess with ICS. You have to buy the NICS regardless. ICS is cheapier if thats the way you want to go. You will have to buy a third NIC that way though.

MosDef112 · Post by **MosDef112** » Tue May 08, 2001 4:20 pm

Given that you said your two PC's are sitting in different rooms, and have no NIC's, I would simplify the process by going wireless. It is relatively a little more expensive, but it's painless to do so. Get one of those Aironet or Proxim 802.1b kits, including the trasmitting tower and NIC's, and pick up a NetGear RT314 router to attach to your Westell DSL modem. The RT314 is particularly nice since it supports PPPoE, including automatic logon and reconnect, and also supports NAT so you don't have to bother with any software NAT on any of your PC's.

krish_na22 · Post by **krish_na22** » Tue May 08, 2001 5:10 pm

Originally posted by GRIM:
1.Get a couple nic's
2.Purchase another ip or 2
3.Buy a router( I would go with this one)
4.Use ICS ( last resort)

These are different alternatives, right? I mean one of the four will do? In that case if I buy two NICs, I guess I would have to use on NIC to connect to the modem, and use the other NIC on the same computer to network. Now, where does the output of this second NIC go into the other computer? And what is the software to be used?

Orphious · Post by **Orphious** » Tue May 08, 2001 5:25 pm

I would definitely go the route solution. Get a nic per comp, buy a router w/ a built in switch, I just got the Dlink 704 which has a 4 port switch built in. Phone line goes into the dsl modem, crossover goes to the wan port (uplink) , computers go to the switch and it handles the rest. Routers function this way and they make it very easy. Definitely the nicest way IMHO

rpeAMP · Post by **rpeAMP** » Tue May 08, 2001 5:55 pm

Which modem do you have? Is it ethernet, PCI, or USB?

JackMDS · Post by **JackMDS** » Tue May 08, 2001 7:01 pm

*********************************************

Read this, hopefully it will clarify the issues.

Hub, Switch, Router, DHCP, LAN, WAN, NAT, etc.

BTW, DSL: USB or PCI Modems are very bad choice for Internet sharing. If you can return the USB modem and get an External Ethernet Modem.

*********************************************

[ 05-08-2001: Message edited by: JackMDS ]

Post by **YeOldeStonecat** » Tue May 08, 2001 8:24 pm

Linksys Wappy, a wireless broad bandwidth NAT router.

A router is definitely the way to go. All the routers log on for you, perform basic NAT firewall protection, and maintain the connection alive 24/7. Wireless is good for computers in different rooms, no drilling, or network cables messing up the place, unless you don't care.

krish_na22 · Post by **krish_na22** » Thu May 10, 2001 9:32 am

Originally posted by Orphious:
I would definitely go the route solution. Get a nic per comp, buy a router w/ a built in switch, I just got the Dlink 704 which has a 4 port switch built in. Phone line goes into the dsl modem, crossover goes to the wan port (uplink) , computers go to the switch and it handles the rest. Routers function this way and they make it very easy. Definitely the nicest way IMHO

So I guess a router is the way to go. But in this solution can I use either a Switch or a Hub? I found this Linksys package which has two NICs and a 5-port Hub (http://www.bestbuy.com/detail.asp?e=110 ... 0&scat=542)
Does this work, given the fact that Verizon gives me only one Dynamic IP address?

krish_na22 · Post by **krish_na22** » Thu May 10, 2001 10:00 am

Originally posted by GRIM:
1.Get a couple nic's
2.Purchase another ip or 2
3.Buy a router( I would go with this one)
4.Use ICS ( last resort)

But why is ICS the last resort- is it so bad- what kinda problems will it result in?

MosDef112 · Post by **MosDef112** » Fri May 11, 2001 10:14 am

*** In response to krish ***

For your purposes, a hub will serve well, and it's adequate enough. You reap benefits with a switch if you wish to avoid broadcast traffic across your LAN, particularly if you run several services and protocols within your LAN. A switch will also minimize collisions in your LAN, since it routes packets to it's intended destination by maintaining a MAC address database, instead of broadcasting the packets across the LAN in hopes that it'll intercept the node it's intended for. As for making use of a router for your setup, yes it is more beneficial for you to consider a router for many reasons, particularly if using Verizon Online DSL. A router like the NetGear RT314 supports PPPoE, and automatic logon. Basically, this eliminates you having to keep your DSL PPP connected by using their proprietary dial-up software on one of your PC's, and when your connection drops, it'll reconnect automatically for you. So once setup, you let it go and let it do it's thing. I'm sure routine maintenance of your router wouldn't be out of the question, like an occasional cold reboot or such. It certainly beats the hell out of using up a dedicated PC to keep your Internet connection alive via software.

MosDef112 · Post by **MosDef112** » Fri May 11, 2001 10:22 am

*** In response to krish ***

ICS is a lousy version of all-in-one NAT/proxy implementations. It does not allow port forwarding, and blocks most ports for incoming and outgoing connections. NAT software like WinRoute http://www.winroute.com will allow incoming connections to all nodes in your LAN when a request for such is made, typically with software requiring a two-way communications link like the telephony feature of MSN Messenger. If you want to host servers publicly behind your WAN link, and lack extra IP addresses, you can also do port forwarding as well.