Nighthawk M2 (MR2100) constant reboot

Hi Blanca_O ,

Thanks for the reply, in answer to your questions;

Reboot - It is mostly a case of the MR2100 turning itself on and off although it does also freeze where the power light is solid blue and the screen is non-responsive and I need to re-set the device.

My network setup, pretty standard started with just wifi enabled and the device plugged into the power and various devices connecting to it's wifi. Although that became to unstable so I have turned off wifi and am connected to an old router I have and using that for Wifi. Given the device does not yet have IP passthrough that is causing some other issues but at least the mr2100 is stable.

How many devices - it can happen just with one connected but normally i have 2-3.

I checked the firware and there is non available. The current one on the device is NTGX24_10.09.01.00

As for factory reset, I have done that several times already.

Thanks for you help

Hi 

I used to work for Netgear - they have good kit and the RA process is probably the best.
That is or was my job for a while.
SO ... in another life the company I'm helping has had some problems with the NightHawk M2

Here are a few thoughts on the matter. - work out which ones might apply

A) The battery may create heat that affects the CPU - causing problems.

B) The single ethernet port could be stressed by issues farther down the line.
    A lot of people are buying trashy switches - so dumb that they fall for the
    old - lets plug all the cables into an 8 port switch - Oh and just for fun
    lets make sure one of those cables forms a loop - one cable plugged
    into the switch twice - Unfortunately that is deadly as  smarter switches
    Turn one of the looped feeback ports into a standby mode but the
    dumb switch does not - causing a cascade of traffic.

C)  This device is not designed - I think, I'm not sure - for very heavy traffic
   so it may have some limitations on throughput. It is possible that it
   runs out of steam when someone plays games or if someone decides
   to finish that spreadsheet late in the afternoon - and now wants to push
   it off to a couple of mates ??

D)  Maybe there is a limit in the number of DHCP assignments inside this
   unit - if that happens it may be a bit slow - clearing the problem and
   effectively stopping the DHCP service from operating.
   The symptom of course would be felt most keenly in the WiFi side
    of things. It tends to lose connection more often and for longer periods
   which - means that a device would ask for an IP address assignment
   and there would be no free slots in the limited DHCP IP table.
   This would probably seem like a full blown failure to the WiFi device
   asking - and the problem would be classified as the WiFi is down.
   In fact a few people in better reception areas - would still be working
   away - since they have kept their IP address.
   Ethernet people  might need to shutdown their PC to experience the
   Wifi is down (actually Ethernet is down) problem. They would try to
   connect and their PC (using the ipconfig) would say "it" is connected)
   but they would be unable to access the internet. The physical ethernet
   may be "connected" but without DHCP it would be DOWN.

OK> I'm hoping you may have followed me so far.
    If you want to try and fix this and get back onto the internet ???
    Try and assign a specific IP address as a backup in case the DHCP
    service is the only thing DOWN.
    This is possible inside a Windows PC - be it ethernet or WiFi.
    There is a place inside Windows WiFi admin that allows you to configure
    a specific IP address for a particular WiFi location. It maye be harder
    for PC's that travel but get connected via Ethernet - just for testing
    learn how to do this.
    I once turned on a fleet of PC's and made their BACKUP IP address
    exactly the same as the one they got from the DHCP server. They
    were all connected to a router - if it died  they all got the proverbial
    196.kiss of death IP address - a specific IP address randomly
   generated by the PC itself. Not good if you happen to want work done.
   At any rate so long as they all get, say a 192.168.1.X or the other
   common 192.168.0.X address (both of these exclude the two
   IP addresses 192.168.1.1 or 192.168.0.1 which is the router's
   own IP address). Then things should/may work because the 
   router may still be connected to the internet and it may still be
   transferring info in and out - it just needs to know the IP address
   of every PC that is talking to it. It gets this info with every so
   called packet - every single packet has to have a FROM and
   a TO  IP address. Sometimes  packets are setup to broadcast
   and that is a special address X.Y.Z.255. Lets not get to
   complex and I will end it here.

HOPEFULLY this may help some peop[le out there?

HELPFUL