MN500 cannot handle 100 Mbps cable modem connection?

After a re-boot, my modem connection continually (about
every 30 seconds) connects and then disconnects. The
Broadband Network Utility during this time notes a 100
Mbps connection speed. After a short period of time, the
BNU will drop back to 10 Mbps, at which connection is
perfect.

Details: Everest is the ISP we're using. Everest can ping
the modem regularly at 100 Mbps, so the issue seems to
between the modem and the router. The cable modem is a
Motorola. The MN500 is connected to the cable modem via
the WAN connection port. There are two computers hard-
connected to the MN500 in slots 1 & 2, a laptop dedicated
to email and our Dell tower. All lights on the cable
modem and router are fully functional and correctly lit.
The only device currently using wireless is my Fujitsu
TabletPC.

Is there an issue with the MN500 such that it cannot
handle this initial connection speed? If so, is there a
fix? I know of two other friends having this identical
issue. Any help would be appreciated.

Sam Johnson

Sam, I believe you're confusing the ratings on your Ethernet card with the
service provided by your ISP. Ethernet cards are rated generally at 10
Megabit to 100 Megabit per second, and most have a handful of settings you
can "tweak" in Device Manager. Call your ISP and ask them the rating of
your current subscription. Remember, too, that the 10/100 is not megabytes
per second, it is megabits.
--
Chris H.
Microsoft Windows MVP
Associate Expert
Expert Zone - www.microsoft.com/windowsxp/expertzone

"Sam Johnson" <(E-Mail Removed)> wrote in message
news:f56001c3f188$5d58c1d0$(E-Mail Removed)...
> After a re-boot, my modem connection continually (about
> every 30 seconds) connects and then disconnects. The
> Broadband Network Utility during this time notes a 100
> Mbps connection speed. After a short period of time, the
> BNU will drop back to 10 Mbps, at which connection is
> perfect.
>
> Details: Everest is the ISP we're using. Everest can ping
> the modem regularly at 100 Mbps, so the issue seems to
> between the modem and the router. The cable modem is a
> Motorola. The MN500 is connected to the cable modem via
> the WAN connection port. There are two computers hard-
> connected to the MN500 in slots 1 & 2, a laptop dedicated
> to email and our Dell tower. All lights on the cable
> modem and router are fully functional and correctly lit.
> The only device currently using wireless is my Fujitsu
> TabletPC.
>
> Is there an issue with the MN500 such that it cannot
> handle this initial connection speed? If so, is there a
> fix? I know of two other friends having this identical
> issue. Any help would be appreciated.
>
> Sam Johnson

The WAN Modem connection port is only 10Mbps. The MN500
only supports 100Mbps for the internal LAN

I would check the computer ethernet card and cables, if
it drops from 100 to 10.

>-----Original Message-----
>After a re-boot, my modem connection continually (about
>every 30 seconds) connects and then disconnects. The
>Broadband Network Utility during this time notes a 100
>Mbps connection speed. After a short period of time, the
>BNU will drop back to 10 Mbps, at which connection is
>perfect.
>
>Details: Everest is the ISP we're using. Everest can
ping
>the modem regularly at 100 Mbps, so the issue seems to
>between the modem and the router. The cable modem is a
>Motorola. The MN500 is connected to the cable modem via
>the WAN connection port. There are two computers hard-
>connected to the MN500 in slots 1 & 2, a laptop
dedicated
>to email and our Dell tower. All lights on the cable
>modem and router are fully functional and correctly lit.
>The only device currently using wireless is my Fujitsu
>TabletPC.
>
>Is there an issue with the MN500 such that it cannot
>handle this initial connection speed? If so, is there a
>fix? I know of two other friends having this identical
>issue. Any help would be appreciated.
>
>Sam Johnson
>.
>

I don't think you answered Sam's question. He asked
rather politlely if there is an "issue" with the MN-500
in lossing connections.

Reading further down the line in your news group that's
all you see, the same "issue" over and over again.

I'd call it a problem. Period!

What's important to Sam and the rest of us is not how many
Megabits/second ethernet cards can send or that someone
mistakes "bytes" for "bits", but that a product purchased
does what it was purchased for, i.e. stay connected.

If MN-500(s) or MN-700(s) cannot stay connected what do
their manufactures expect us to do, unplug them every 15
or 30 minutes and then reboot their gadgets.

Isn't the media the message...! And what kind of message
does the media have here...?

Wouldn't it be easier to find a solution, update something
or recall a series instead of giving spelling lessons
about "bits" for "bytes".

Yes, Mr. Chris H. of the expertzone I am displeased with
you. It would have been far wiser to tell your boss that
there may be a problem in the MN-500 (or MN- 700) and
that your clients are wasting time, which is really
another way of spelling productivity.


James Sexton
(E-Mail Removed)

And I explained what I thought was the correct answer. Why not let him
speak for himself?

BTW - I'm a user just like you, and Microsoft isn't my "boss." I'm disabled
and will never work for anyone, so I voluntarily try to assist other users.
--
Chris H.
Microsoft Windows MVP
Associate Expert
Expert Zone - www.microsoft.com/windowsxp/expertzone

"James Sexton" <(E-Mail Removed)> wrote in message
news:f00e01c3f1f9$bcbcb3e0$(E-Mail Removed)...
> I don't think you answered Sam's question. He asked
> rather politlely if there is an "issue" with the MN-500
> in lossing connections.
>
> Reading further down the line in your news group that's
> all you see, the same "issue" over and over again.
>
> I'd call it a problem. Period!
>
> What's important to Sam and the rest of us is not how many
> Megabits/second ethernet cards can send or that someone
> mistakes "bytes" for "bits", but that a product purchased
> does what it was purchased for, i.e. stay connected.
>
> If MN-500(s) or MN-700(s) cannot stay connected what do
> their manufactures expect us to do, unplug them every 15
> or 30 minutes and then reboot their gadgets.
>
> Isn't the media the message...! And what kind of message
> does the media have here...?
>
> Wouldn't it be easier to find a solution, update something
> or recall a series instead of giving spelling lessons
> about "bits" for "bytes".
>
> Yes, Mr. Chris H. of the expertzone I am displeased with
> you. It would have been far wiser to tell your boss that
> there may be a problem in the MN-500 (or MN- 700) and
> that your clients are wasting time, which is really
> another way of spelling productivity.
>
>
> James Sexton
> (E-Mail Removed)
>

I agree with "anonymous." Unless you are paying for a
bussiness class service there is NO way yuo're modem is
connecting at the 100Mbps speed, that would cost you way
too much. Plus the modem etherports are only rated at
10Mbps.

Al

I used to be a Cable Systems Tech for Time Warner Cable
and we were using Toshiba and Motorola cable modems.


>-----Original Message-----
>After a re-boot, my modem connection continually (about
>every 30 seconds) connects and then disconnects. The
>Broadband Network Utility during this time notes a 100
>Mbps connection speed. After a short period of time, the
>BNU will drop back to 10 Mbps, at which connection is
>perfect.
>
>Details: Everest is the ISP we're using. Everest can
ping
>the modem regularly at 100 Mbps, so the issue seems to
>between the modem and the router. The cable modem is a
>Motorola. The MN500 is connected to the cable modem via
>the WAN connection port. There are two computers hard-
>connected to the MN500 in slots 1 & 2, a laptop
dedicated
>to email and our Dell tower. All lights on the cable
>modem and router are fully functional and correctly lit.
>The only device currently using wireless is my Fujitsu
>TabletPC.
>
>Is there an issue with the MN500 such that it cannot
>handle this initial connection speed? If so, is there a
>fix? I know of two other friends having this identical
>issue. Any help would be appreciated.
>
>Sam Johnson
>.
>