MN-700 drops connection everyday

My MN-700 disconnects once a day, BOTH wired and wireless
disonnect when this happens. There is no any response from
the router. I have to power off then power on ot.

I did some search in this newsgroup but found no solution.
(Installing another router between MN-700 and modem seems
to work, but I don't have a spare.)

The firmware is up-to-date. There's only some port scans
in activity log.

Thanks for any help.

--
email: (E-Mail Removed)

I have the same problem with the MN-500, though I don't
have an answer, I've heard that going back one revision
in Firmware might provide relief for MN-500 users with
this issue. Not sure if it can help you. My
troubleshooting has found issues with how the MN-500
router deals with DHCP requests, but I can't point to
that as the problem. I'm still working on it.

Mike

>-----Original Message-----
>My MN-700 disconnects once a day, BOTH wired and
wireless
>disonnect when this happens. There is no any response
from
>the router. I have to power off then power on ot.
>
>I did some search in this newsgroup but found no
solution.
>(Installing another router between MN-700 and modem
seems
>to work, but I don't have a spare.)
>
>The firmware is up-to-date. There's only some port scans
>in activity log.
>
>Thanks for any help.
>
>--
>email: (E-Mail Removed)
>.
>

Thanks Mike. I used original firmware that came with my
router for couple days, and updated firmware too, but the
problem was the same. And I don't know how to manually
downgrade the firmware (I can't even find the firmware).

Anyway, no solution found. I just gave up and grabbed a
Netgear MR814v2. Have been connected for 3 days, no
problem so far.

Period.

>-----Original Message-----
>I have the same problem with the MN-500, though I don't
>have an answer, I've heard that going back one revision
>in Firmware might provide relief for MN-500 users with
>this issue. Not sure if it can help you. My
>troubleshooting has found issues with how the MN-500
>router deals with DHCP requests, but I can't point to
>that as the problem. I'm still working on it.
>
>Mike