Oh yes it must be a firmware problem...
This is the answer from a colleague of Chris, it is
from "Neel Malik [MSFT]" <(E-Mail Removed)>
from a post I had about this issue some days ago (around
July 30):
>... I could tell you that I have had an MN-700 in my
>house running for weeks without a problem as have many
>other people.
>What might help is for you to push the Restore to
>factory defaults button
>and then set up the MN-700 again. It is possible that
>some configuration
>setting is not quite right and restoring to factory
>defaults should fix
>that.
Needless to say that I tried this several times before I
made the first post and that I tried it again after this
answer - well, I still have the problem...
Chris, it would be great if you could use your
connections to get this fixed!
Thanks and best regards, Alex
>-----Original Message-----
>Hey~
>
>This is certainly still an issue with the firmware. I
>have a similar post - hang tight while we figure this
>out. (i.e. I work at MS, so I will probably try and
find
>someone internally to figure out what is going on)
>
>Thx,
>~C
>>-----Original Message-----
>>I find I need to reset the wireless hub on a daily
>basis.
>>I'm using PPOE and have the connection duration set to
>>the max (999). However on a daily basis it goes
>>unresponsive and I need to reboot it. I never had this
>>issue with my previous linksys hub.
>>
>>I don't see anything in the device log to help. Here's
a
>>log from the last 24 hours. (I rebooted the device
>>yesterday and cleared the log after upgrading the
>>firmware).
>>
>>1999/06/01 12:00:04 PPPoE send PADI
>>1999/06/01 12:00:04 PPPoE receive PADO
>>1999/06/01 12:00:05 PPPoE send PADR
>>1999/06/01 12:00:05 PPPoE receive PADS
>>1999/06/01 12:00:05 **** Device Booted: Version
>>02.01.02.0590
>>2004/08/08 09:16:28 RF Reset...Pass
>>2004/08/08 09:16:30 System time synchronized with
>>207.46.130.100, 14 seconds from system bootup.
>>2004/08/08 09:17:53 192.168.2.102 login successful
>>2004/08/08 09:19:22 RF Reset...Pass
>>.
>>
>.
>
|