Background: So, a while (a couple months) ago, I had connected a Netgear wireless router (which model it was exactly, I forget) to my MRI424WR router so that I could have wireless access span my house effectively (the FiOS router is at one end of the house, and wireless access is weak/non-existant at the other end). At first, this worked fine, with both acting as their own DHCP server, with the Actiontec having an IP of 192.168.1.1 and the Netgear was on 192.168.0.1 (the Netgear was using the Actiontec as its . After a day or two, I noticed that the Netgear router lost connectivity to the internet. I logged in to it to see what the problem was, and I noticed that it wasn't being given an IP by the Actiontec router anymore. I was able to get the Actiontec to recognize it again after a bit of time leaving the Netgear router unplugged and power cycling the Actiontec router, but after a while it failed again. This pattern repeated for a little while, and eventually I gave up on the idea of having two routers on the network. Although the Netgear router has been unplugged and turned off for months, the Actiontec router will still have serious problems with ethernet connections at random times.
Here's what I mean by serious problems: the Actiontec router (the only one on the network) will randomly drop all ethernet connections and stop assigning IP addresses to ethernet connections. The only thing that seems to remedy this situation is doing a factory reset, and that doesn't always work. Even after numerous factory resets, it still sometimes refuses to assign IPs to ethernet connections. Assigning an IP for the device trying to connect (ie- telling the computer to use 192.168.1.7 instead of requesting an IP from the router) only works sometimes. Most of the time when it does work, it will connect, but rapidly changes from working ethernet to "limited or no connectivity" (using XP). The Actiontec router will also seemingly randomly start assigning IPs to ethernet connections again, too.
The most unusual part is that wireless never is affected. We have an Xbox360 (sometimes 2, if we have friends over) and an HP network printer (currently disconnected) attatched to the router via ethernet connections, and we add a laptop when we are trying to fix it.
Here's what I've done to try to resolve the issue:
The router has done this to me so many times I'm sick of having to reset it. Is there anything left that I can do, or should I just try to get a replacement from Verizon (we use their FiOS phone, internet, and TV, and from what I understand, the router is under permanent warranty because we have FiOS TV)?
PS- Sorry for the wall of text there. Just trying to give as much information as possible.
Your issue could be because the Actiontech router has a small/tiny NAT Table?
I point to:
If you are the original poster (OP) and your issue is solved, please remember to click the "Solution?" button so that others can more easily find it. If anyone has been helpful to you, please show your appreciation by clicking the "Kudos" button.
I'm afraid that didn't solve the problem for me. Anyone else have any ideas? To reiterate, it seems like the ActionTec router will stop acting as a DHCP server for ethernet connections at random, but wireless will still connect just fine. I'm using the latest firmware, and I can't find anything that might be causing the problem.
01-11-2010 08:33 AM - edited 01-11-2010 08:36 AM
Configure the netgear router with a static address on the actiontech subnet
The leave it as serving dhcp address in the 192.168.0.x range. Should work with no issue. Am not sure that once the dhcp lease that the actiontec granted to the netgear expires if the netgear router has the sense to request a new one. Anyway making the address static is the only way to get port forwarding to work if you attempt to port forward from the actiontec subnet to a machine on the netgear subnet.
However it sound likely that your Actiontec router is flaky so you may want to visit your local Verizon Fios store and see if they will exchange it.
Sounds like it could be a software issue on the router. Have you tried to update the firm ware? You may need to order a new router from Verizon. I have seen posts from other forum users where their Actiontec started acting up (all different kinds of problems) nad the general consensus is that the Actiontec is not very robust. Firm ware and hardware issues abound with the Actiontec.