MN-700 FAILURE

First symptoms were disconnection requiring reboot. The
wifi link remained intact, but "wired" connection was
lost. Then it ALL failed which was corrected by resetting
the bases station. 5 days later and here we go again.
I've just pulled it out of the system.

When is the fix going to come out? We know this is a
widespread problem with a Sh**load of variations.

Your not the only one.

>-----Original Message-----
>First symptoms were disconnection requiring reboot. The
>wifi link remained intact, but "wired" connection was
>lost. Then it ALL failed which was corrected by
resetting
>the bases station. 5 days later and here we go again.
>I've just pulled it out of the system.
>
>When is the fix going to come out? We know this is a
>widespread problem with a Sh**load of variations.
>.
>

I'll second that!

I've gone through all the tech support lines, received a new router as the
lockups "must be a bad unit", surprise, surprise the new unit locked up
today after 3 days of use.

I guess I should not be complaining, after all 3 days of uptime is a good
record for a MN-700!

"Hanafi" <(E-Mail Removed)> wrote in message
news:14a2a01c418ca$3f7a8130$(E-Mail Removed)...
> First symptoms were disconnection requiring reboot. The
> wifi link remained intact, but "wired" connection was
> lost. Then it ALL failed which was corrected by resetting
> the bases station. 5 days later and here we go again.
> I've just pulled it out of the system.
>
> When is the fix going to come out? We know this is a
> widespread problem with a Sh**load of variations.

I have a similar problem. Check your base station log. There is a bug that
if the
base station cannot contact the time server (it uses a time server to set
it's clock, microsoft
hosts this I believe), then the unit locks up and has to be rebooted. I
opened a SR with
Microsoft and they say this is a known issue that is currently be fixed in a
future firmware
release. I can't believe they would release this product without finding
this issue. Check your
base station log for messages that have 1999 as the date. If you see this
after you have to
reboot your base station, you probably have the issue I'm describing.
Example log:

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


"Andrew" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> I'll second that!
>
> I've gone through all the tech support lines, received a new router as the
> lockups "must be a bad unit", surprise, surprise the new unit locked up
> today after 3 days of use.
>
> I guess I should not be complaining, after all 3 days of uptime is a good
> record for a MN-700!
>
> "Hanafi" <(E-Mail Removed)> wrote in message
> news:14a2a01c418ca$3f7a8130$(E-Mail Removed)...
> > First symptoms were disconnection requiring reboot. The
> > wifi link remained intact, but "wired" connection was
> > lost. Then it ALL failed which was corrected by resetting
> > the bases station. 5 days later and here we go again.
> > I've just pulled it out of the system.
> >
> > When is the fix going to come out? We know this is a
> > widespread problem with a Sh**load of variations.
>
>