Can't get second Actiontec connected to the internet

I'm trying to get an older Actiontec MI424WR-GEN2 hooked up to my network by coax as a secondary. My primary router is an Actiontec MI424WR Rev I that is hooked up by coax on a different floor.

I have seen this thread http://www.dslreports.com/faq/verizonfios/3.2_MOCA#15984 and have followed the instructions for #2. When I tried to follow the instructions, I had 2 problems.

Issue 1. In Step 2.2 I could not, at first, set the secondary router's IP address (was trying 192.168.1.27) because I was getting an error message that said could not set that address because I was in the range of the start IP/end IP address. I realized in Step 2.4 the DHCP server gets disabled, so what I did to get around this was to change the start IP to 192.168.1.100 and then I was able to set the secondary router to 192.168.1.27.

Issue 2. When doing step 2.4, I got a message saying "an internal error occurred unknown connection dhcp_mode." It said try again. However, when I checked the DHCP server was disabled. I had reset the router a few times and repeated this step and always got the error message.

I do think I achieved what I was supposed to, but please let me know if I am mistaken: I was able to set my secondary router's IP as 192.168.1.27 and disable off the secondary router's DHCP server despite getting an "error' message.

Here's the results I am getting:

1. Secondary router's main screen says Router Status STOP.

2. When I look at MY NETWORK on the secondary router, the secondary router recognizes some other devices on the network as well as the PC client attached to it with a LAN cable.

3. The internet light won't come in in the secondary router. The PC hooked to the secondary router can't get to the internet, but it can ping any device on the network and it can access the primary router's configuration..

Any idea on how to establish an internet connection on the secondary router?

Thanks!

Accepted answers

skillset1

Hi all - very much appreciate the replies. I did finally get it to work but I think it may just have been a little bit of patience. Everytime I did a change, the router seemed to be in an endless loop updating (no matter what computer I hooked it to) and so, this time, I waited a minute between each change.

Thanks for the comments related to not seeing the internet light. This was very helpful.

I did reset it a few more times to experiment. I was NOT able to disable the DHCP first because when I did, I was not able to log back into the router. So, I'm concluding that I needed to change the IP address first. So, the original link's order seemed to be correct, although there should be additional clarification of how to set the IP address so that it is not in the range of the start/stop.

I also don't understand why I keep getting an error message when disabling DHCP, although it seems to work even after I get the error message.

In any event, it is working now and I've tried moving it to different coax cables and using both wireless and a lan cable and all situations works.

Thanks again for the suggestions provided!

All comments

smith6612

Sounds like your secondary router is working fine in the MoCa Bridge setup you're trying to accomplish if you're able to ping devices that are connecting to the other router. The Internet light should remain out on the second router, since that light is only supposed to light when the router is holding an IP address from Verizon.

As to why devices on the second router can't ping out, does DNS (nslookup www.google.com ) at least work? Can you ping an IP address on the Internet such as 4.2.2.2 from behind the second router?

Just some starting points until someone more knowledgable in the procedure can help.

mfizzy

I had a little trouble with those instructions. I think 2.2 and 2.3 are backwards. Disable dhcp then set the router admin login ip. You definitely want dhcp off in the second router. My setup works just fine after swapping the two steps.

Anti-Phish1

You did't say if you can get out to the internet from behind the secondary router. That's the best indication that it's working.

Regarding #3, it's normal for the internet light to be off. You're creating a LAN bridge. The WAN section of the secondary router is not used, therefore the internet light won't come on.

mfizzy

Just becase you can get to the internet from the second router doesnt mean it is totally correct. Computers connected to the second router need to be able to communicate with with computers on the first. computers on the first router need to be able to communicate with devices on the second. If he is running DHCP on the second router with IPs starting at .100 (true fist IP will be .151) devices connected to the first router do not know how to route to an internal IP that is not assigned in the first routes DHCP pool. 192.168.1.xxx's are internal IP's.

viafax999

@hlppls wrote:
Just becase you can get to the internet from the second router doesnt mean it is totally correct. Computers connected to the second router need to be able to communicate with with computers on the first. computers on the first router need to be able to communicate with devices on the second. If he is running DHCP on the second router with IPs starting at .100 (true fist IP will be .151) devices connected to the first router do not know how to route to an internal IP that is not assigned in the first routes DHCP pool. 192.168.1.xxx's are internal IP's.
That's why there can only be one dhcp server on the subnet. Doesn't matter which router you choose to have an actib=ve dhcp server but there can ONLY be one.
Personally I would leave the new router with the active dhcp server as some old the old revs were a bit flaky with nat tables etc.
The referenced link is odd. I would put disabling the dhcp server as the first step in 2.1 Also would be useful to note in 2.2 that when setting an ip address on the 192.168.1 subnet the gateway should be defined as 192.168.1.1
The dns server could also be specified as 192.168.1.1

skillset1

Thanks for the comments related to not seeing the internet light. This was very helpful.

I also don't understand why I keep getting an error message when disabling DHCP, although it seems to work even after I get the error message.

In any event, it is working now and I've tried moving it to different coax cables and using both wireless and a lan cable and all situations works.

Thanks again for the suggestions provided!