|
Posted by Morris Ebbets on October 4, 2005, 3:05 pm
If you were Registered and logged in, you could reply and use other advanced thread options
> On Tue, 4 Oct 2005 12:28:58 -0400, "Morris Ebbets"
>
> >Just got married and moved in with my wife, who has Comcast cable
broadband.
> >(Had previously been on Verizon DSL.) She has a Motorola SB1500
SURFboard
> >cable modem and a LINKSYS BEFSR41 router; runs Windows XP Home. (Pretty
> >sure it's SP2.)
>
> The cable modem is probably a SB5100, I hope. :)
Right you are.
> >Looking at the quick setup guide for the router, I tried plugging my
Windows
> >XP Home SP2 box in. Didn't work. Tried a few things, then finally got
it
> >to work when I found that I can get one computer (but not both) running
> >broadband. Pattern seems to be that the one I plug into port 1 (or
whatever
> >it's called) on the router works, but not the other.
>
> Not much to go on here, but the basics are that the router's Internet
> port, sort of off to one side by itself, should be connected to the
> cable modem, and the PC(s) should be connected to any of the ports
> labeled 1-4. The PC(s) should be configured for DHCP, (easiest to get
> working; you can do static IP assignment outside of the router's DHCP
> range later.)
I'm pretty sure it's not a configuration issue, because my XP box works when
hooked up to port 1, and I'm pretty sure that it's running DHCP.
> Power down the cable modem, the router, and the PC(s),
> then power up the cable modem and let it stabilize, power up the
> router and let it stabilize, then power up one PC at a time. Make sure
> there are Link lights at both ends of all live (powered up) cables.
OK. Did all that.
> Rule out a bad patch cable.
Don't think it's the cable since P 1 works, but not 2-4.
> If Port 1 works on the router, but 2-4
> don't, you may have a bad router.
Good idea. That's my leading hypothesis right now.
> If you have all of the necessary
> Link lights, see if you can ping the LAN side of the router from the
> 'bad' PC, (usually at 192.168.1.1), and if that works, ping the cable
> modem, (usually at 192.168.100.1). The ping results will help you
> determine where to go next.
Forgot to do that...see my response to the entire thread for the info I
*did* gather.
>
> --
> Bill
| 
NewsGroups 
Yahoo! 
Google 
Windows Live 
del.icio.us 
digg 
Netscape 
XML site map