Check your base station log, if you see bad dates (e.g. 1999) the router may
be
having trouble contacting the time server to get it's system time. When this
happens the
mn700 locks up and has to be rebooted. This happens to me multiple times per
day. I
opened a support call with Microsoft and they say it's a known issue and
they're working
on a firmware fix. They couldn't give me a release date for it. I have no
workaround. I
personally think this is complete bullsh** that they would release a product
with this obvious
of a problem. I know I'm not the only one experiencing this. If you see
something like the
below messages in your base station log, please log a call with Micosoft.
The more people that
complain the better chance we'll get a fix soon.
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
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
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
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
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
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
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
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
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
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
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
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
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
1999/06/01 12:00:08 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/10 20:42:06 RF Reset...Pass
2004/04/10 20:42:07 System time synchronized with 207.46.130.100, 14 seconds
from system bootup.
2004/04/10 20:42:10 System time synchronized with 207.46.130.100
2004/04/10 20:42:59 DHCP Client : Request sent from 66.31.179.64 to
24.34.241.34
2004/04/10 20:43:00 DHCP Client : Server response sent from 24.34.241.34 to
66.31.179.64
<(E-Mail Removed)> wrote in message
news:164c901c41c16$412ec960$(E-Mail Removed)...
> Did you get an answer - same thing is happening to me. I
> just got the MN700 base station - I'm resetting it about
> 4 times a day. I downloaded the latest firmware and
> cloned the MAC address of my main adaptor as Microsoft
> recommended - all to no avail
>
> >-----Original Message-----
> >All my PCs on my wireless network to include my main PC
> >which is wired thru ethernet card is losing
> >internet/intranet connection.
> >I have the 720 wireless router and all the laptops have
> >the MS wireless adapter. It is not a roadrunner issue as
> >resetting the wireless router solves the problem. Was
> >fine for 3 months straight until today. No new programs
> >have been installed and all software drivers are up-to-
> >date. Anyone else getting this error?
> >.
> >
|