FDL-nj wrote:
> I have a DSL modem (Westell model 6100 from Verizon) connected via USB to
> a desktop PC. I bought a Linksys Wireless-N router (model WRT300N) so I can
> share the internet connection with another desktop PC in a downstairs room.
> I used an ethernet cable to connect the router to the modem. With the
> primary PC on I powered up the modem, then the router. Because the primary
> PC is connected to the modem I was able to access the internet but even
> though I was getting a signal on the second PC I was unable to connect to the
> internet. Plus if I rebooted the primary PC the USB connection to the modem
> is dropped. Rebooting without the router connected to the modem does not
> effect the the USB connection.
> The extent of my technical knowledge is I know enough to get myself in
> trouble, so after about 6 hours of troubleshooting I stumbled on the fact
> that both the modem and router are trying to use the same IP address. Will
> changing the IP address on either the modem or the router fix my problem? If
> so, how do I do that?
>
My advise here would be to get a modem that uses the RJ45 jack
connection and dump the USB. You take a regular networking cable that
uses the RJ45 plug and plug one end into the modem that uses RJ45 and
the other end into the RJ45 WAN port on the router.

You then use a regular Ethernet Networking Interface Card with a RJ45
connection in the desktop computer and take a networking cable like the
one up above and plug it into the LAN port on the router.

If possible, you should put all of your computers behind the protection
of the router. The router protects them from attacks from the Internet.
That's what the router is for and not the computer, which is to protect
the LAN-Local Area Network from attacks from the Internet.

http://www.homenethelp.com/web/explain/about-NAT.asp

You might want to look into the wireless security for the home too and
apply where possible.

http://netsecurity.about.com/cs/wire...aa112203_2.htm

If the router has a syslog and Wallwatcher can be implemented, then you
should use WW and watch traffic to and from the router for possible
connections from machines behind to dubious remoter IP(s) on the Internet.

http://www.sonic.net/wallwatcher/

Duane :)