Based on your logs, the upstream DHCP server (from your
dynamic IP) is failing from time to time (the NAKs are
sent by the upstream server, and not created by the
MN500).
Also, why is the upstream DHCP server giving you a lease
for just 60 secs? Typically, a lease lasts for hours or
days. A so short lease may overload the router when you
use time crtical tasks, such as video conferencing.
Do you have control over the upstream DHCP server
offering the dynamic IP? If yes, increase the lease time;
otherwise contact your ISP.
BTW -- I'm not MS person, but have a MN500 running with
no problem, including for video.
>-----Original Message-----
>Since upgrading my MN-500 to the latest firmware
Version:
>V1.11.017, Date: 10-03-2003, my base station is locking
>up peridically. Here is what I've found:
>
>Problem 1)
>Symptom - Internet connection is lost for about 5-10
>seconds every 2+ minutes. Very annoying when your video
>conferencing..
>
>Cause - DHCP client in MN-500 router in "Dynamic" mode
>not playing nice with half-bridge in DSL router.
>
>Evidence:
>From MS router log file
><----snip
>2004/02/12 19:01:42 DHCP Client : Receive Nak
>2004/02/12 19:01:51 DHCP Client : Send Discover
>2004/02/12 19:01:51 DHCP Client : Receive Offer from
>192.168.1.2
>2004/02/12 19:01:56 DHCP Client : Send Request, Request
>IP = xxx.xx.xxx.60
>2004/02/12 19:01:56 DHCP Client : Receive Ack from
>192.168.1.2, Lease time = 60
>2004/02/12 19:02:20 DHCP Client : Send Request, Request
>IP = xxx.xx.xxx.60
>2004/02/12 19:02:20 DHCP Client : Receive Ack from
>192.168.1.2, Lease time = 60
>2004/02/12 19:02:49 DHCP Client : Send Request, Request
>IP = xxx.xx.xxx.60
>2004/02/12 19:02:49 DHCP Client : Receive Ack from
>192.168.1.2, Lease time = 60
>2004/02/12 19:03:18 DHCP Client : Send Request, Request
>IP = xxx.xx.xxx.60
>2004/02/12 19:03:18 DHCP Client : Receive Ack from
>192.168.1.2, Lease time = 60
>2004/02/12 19:03:48 DHCP Client : Send Request, Request
>IP = xxx.xx.xxx.60
>2004/02/12 19:03:48 DHCP Client : Receive Ack from
>192.168.1.2, Lease time = 60
>2004/02/12 19:04:17 DHCP Client : Send Request, Request
>IP = xxx.xx.xxx.60
>2004/02/12 19:04:17 DHCP Client : Receive Nak
><----snip
>
>From Nak to Nak times vary.
>M : S
>02:35
>02:38
>02:40
>
>From Nak to Discover is typically about 2-10 seconds
>
>As you can see above there is a discrepancy in times.
If
>the times from Nak to Nak are 2 minutes 35 seconds to 40
>seconds, then how can the DHCP client in the MN-500 be
>requesting it's IP address 5 times at 60 second
intervals
>between each Nak? The loss of internet coincides with
>the Nak - Discover - Recieve process of the DHCP client.
>
>Problem 2)
>Symptom - The router locks up every 12 hours. The
>internal wired and wireless networked devices are
>available, but all routing between LAN and WAN has
>stopped, and the internal management website on the MN-
>500 is not available. Power cycle is required for
>recovery.
>
>Evidence - No log file is recoverable. The DSL router
is
>still functional, so only the MN-500 requires a reboot.
>
>Solution - None known. Going back to a previous version
>of FW has been suggested, though MS does not provide
>older FW software in their download section.
>
>I would like a MS persons take on this issue if any read
>this. Does anyone have the V1.08.XXX version of FW for
>this router that they could send me?
>
>Regards,
>
>Mike
>
>.
>
|