I have the same problem with the MN700. I rarely get 24 hours of uptime
with this
router. Each time this happens, the router is completely unresponsive. I
reset it and then
check the base station log and see an invalid date when attempting to
contact the time server.
I opened a case with Microsoft and they claim this is a known issue to be
fixed in
an upcoming release of the firmware. Of course, no date for the firmware
release
could be given. I have yet to find a workaround other than resetting the
base station
and runing ipconfig /renew. This is very annoying. If someone else has a
better workaround
please let me know. My base station log contains entries like this:
1999/06/01 12:00:05 DHCP Client : Server response sent from 10.220.48.1 to
66.31.179.64
1999/06/01 12:00:05 **** Base Station Booted: Version 02.00.08.0333
2004/04/19 22:33:47 DHCP Client : Obtained lease for 66.31.179.64 on
6/1/1999 12:00:04; lease expires on 6/5/1999 12:00:04
2004/04/19 22:33:50 System time synchronized with 207.46.130.100, 11 seconds
from system bootup.
"Gary Tsang" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi,
>
> Have you updated the MN-700 to the latest firmware?
> Download the latest firmware from the Microsoft Broadband Networking
> Hardware Site here.
> http://www.microsoft.com/hardware/br...Downloads.aspx
>
> --
> Gary Tsang
> Microsoft MVP - Windows XP Shell/User
> http://www.microsoft.com/mvp
>
>
> "Jason" <(E-Mail Removed)> wrote in message
> news:1907c01c423c9$bf9afa20$(E-Mail Removed)...
> >I should mention that, when I say it stops communicating
> > with all of the systems, that includes the ones that are
> > connected by ethernet cables not just the wireless ones.
> > Thank You
> >>
>
>