Hi everyone, I am totally at a loss here with a problem I'm having.
I'll break it down, and hopefully someone will be able to shed some
light on it.

Hardware: Linksys BEFSR41 router and a Terayon TeraPro series modem..
not sure what model.
I have a Rogers cable internet connection here that has been working
perfect for about 6 months. So, now there's a roomate so the internet
connection has to be shared. I go out, buy an SMC Barricade 4pt
router and hook it all up. Here's the connection process: I connect
the router to the modem, works fine. As soon as I connect the router
to the NIC on the computer that was originally directly connected to
the modem, the physical link light on the back of the modem starts
blinking. I disconnect it, and it goes solid again, connect it,
starts blinking again. Doesn't seem to matter if the OS is going yet
or not as it starts as soon as power is running through the PC. On
the other computer, this isn't happening.. the connection is fine.

So, to break it down:
- the modem to router with no other connection works flawlessly. (i
can see that the router got an ip by going to the status page when i
connect a client pc)
- pc to router without modem works flawlessly
- as soon as the pc connects to the router when it's running, it
breaks the connection between the modem and the router.

weird, isn't it? Anyway, I hope some of you smart guys have heard
something about this, as I have tried it with 3 seperate routers and 2
different brands (SMC and Linksys)

Thanks for any and all responses.

Chris

On 10 Nov 2003 19:13:42 -0800, greektos@hotmail.com (Snake Factory)
wrote:

Chris,

I'm not sure exactly what's going on. But try power resetting the
modem. Power everything off, connect modem to router to computer,
then power on in this sequence:
1) Computer
2) Router
3) Modem

Does Rogers provide straight DHCP service? Or are they PPPoE? Did
you have to install any client software on the computer?

Cheers,

Chuck
I hate spam - PLEASE get rid of the spam before emailing me!
Paranoia comes from experience - and is not necessarily a bad thing.

Chuck wrote:
Chuck,
Your power on sequence is the exact opposite of that recommended by
ALL other references, and my personal experience. Power on modem, wait
for sync, then router/switch, then the computer. Your sequence will not
get DHCP assigned IP.

On Tue, 11 Nov 2003 11:27:04 -0600, Ron Hunter <rphunter@charter.net>
wrote:

Ron,

Frequently, you need to power cycle a cable modem to get it to
recognise the MAC address of whatever you connect to it.

You're right, though, about the DHCP issue. If a DHCP client is
powered up without a DHCP server being available, the client will
issue itself a bogus address which of course won't allow it to connect
to the upstream device (computer to router, or router to network).

If you power up the computer, then power up the router, chances are
the router will be up long before the computer gets around to asking
for a DHCP address. But best not to take a chance.

So you're right:
1) Power everything off.
2) Power up the modem - clears the client MAC address.
3) Power up the router - sets its MAC address in the modem, gets its
upstream IP address and starts its downstream DHCP server.
4) Power up the computer - gets its IP address from the router (its
DHCP server).

Cheers,

Chuck
I hate spam - PLEASE get rid of the spam before emailing me!
Paranoia comes from experience - and is not necessarily a bad thing.