Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years.

Thanks,

CNET Support

Question

Router occasionally fails to asssign IPv4 address

Feb 27, 2018 2:16PM PST

I've been working on this issue for weeks and haven't found a solution. Can anyone make a suggestion?

My network:
Router: Hintron CODA 4582
Clients: 1 Windows 10 Pro hardwired
1 Windows 7 Enterprise Hardwired
several WiFi clients
TV, A/V receiver & 2 media centres hardwired

The problem:
Occasionally the Win 7 computer does not get a correct IPv4 address assigned. When this happens, it is assigned 169.254.0.0. Normally it is assigned 192.168.0.10. The IPv6 address is correctly assigned. When this happens, none of the WiFi clients are able to join the network. The Win 10 computer gets both IPv4 & IPv6 addresses assigned correctly. Rebooting the Win 7 computer does not resolve the issue but rebooting the router does fix it.

I have recently moved and have a new ISP (cable). This same network worked flawlessly on my previous ISP (DSL).

Here is what I have done so far...
-relocated the router closer to the Win 7 computer (shorter Ethernet cable)
-connected the Win 7 computer via WiFi
-replaced the Ethernet cable
-replaced the Router
-full virus scan on the Win 7 PC (AVG & MalwareBytes)

None of these actions resolved the issue.

I'm in a little over my head but my research tells me that when the PC client is unable to get an IP address from the DHCP, an IP address in the 169.254.X.X is assigned to enable LAN connections.

My last corrective action was a router replacement since nothing else worked so, by process of elimination, it seemed that the router was the problem but I've had a failure with the new router.

I though that it might be something in the Win 7 PC since the Win 10 PC didn't have a problem. However, it didn't have the same problem with my former ISP. In addition the failure also disables the ability of WiFi clients to join the network.

So.....
I'm at a loss. Does anyone have a suggestion?

Discussion is locked

- Collapse -
Clarification Request
Problem is router settings
Mar 1, 2018 11:17AM PST

Allow more IP connections in the 192.168.. range. Disallow any IPv6 address assignments.

- Collapse -
Router Settings
Mar 2, 2018 7:19AM PST

Sorry. Somehow I missed this post.
I looked at the router settings and didn't find anything that exactly matched "Allow IP X connections". However, I found the following 2 entries:
DHCP Starting IP 192.168.10
DHCP Ending IP 192.168.200

I believe that this means 191 IP addresses are available in this range. The maximum IP addresses that could be assigned on my LAN is 10. Therefore, I don't think that this is the problem.

I think that is what you meant. Correct?

- Collapse -
Correct
Mar 2, 2018 9:39AM PST

So, that's NOT causing the problem.

- Collapse -
Home Group. Are you using it?
Mar 2, 2018 9:44AM PST
"Occasionally the Win 7 computer does not get a correct IPv4 address assigned. When this happens, it is assigned 169.254.0.0. Normally it is assigned 192.168.0.10. "

Is your Windows 7 computer using the Home Group networking area? I've found that to cause problems, including moving to 10.0.0.0 type IP addresses which interfere with router connections. There's another networking area in W7 which isn't Home Group and I prefer to use that on newer windows systems because I've had less problems with W7 computers connecting to router properly on my own home LAN. Set it up with that and I suspect these problems with the W7 will disappear. In fact, Microsoft plans in future to remove Home Group from Windows 10 system. They haven't said why, but I have my suspicions on the "why", based on my own experiences with it.
- Collapse -
Not using homegroup
Mar 2, 2018 2:23PM PST

No. I'm not using Homegroup for networking.

- Collapse -
Answer
Some good news.
Feb 27, 2018 2:19PM PST

That Enterprise version comes with gold support. Get back to those that supply this and get your free support.

- Collapse -
Thanks
Feb 28, 2018 6:34AM PST

OK. I'll look into that. However, I bought this computer used and it had the Ultimate version pre-installed. I don't have any information that helps me access Ultimate help. However, I'll investigate.

- Collapse -
Enterprise is expensive.
Feb 28, 2018 1:37PM PST

And I take folk's word they have such. As to Ultimate that's a different version.

Since it only happens occasionally you have time to figure out if it's a network card or cable failure.

- Collapse -
Correction
Mar 1, 2018 8:12AM PST

Sorry, my mistake. My Win 7 version is Ultimate not Enterprise. I guess that I've been so wrapped up in the issue that I mis-typed.

From a logic perspective, I don't see how it could be a network card problem:
- I didn't have this problem with my former ISP and I have the same hardware/software.
- When the Win 7 PC in unable to get an IPv4 address, WiFi also has failed.

The common element here is the router and the cable. However, the Win 10 PC is able to get an IPv4 address. I'm really stumped.

- Collapse -
I deal with new IT staff like that.
Mar 1, 2018 8:30AM PST

That get so consumed trying to logic it out when I know to try a new cable and card fast. Time at the office is money and we want those doing the IT work to not waste time over a 10 buck card or cable.

Yes, we have an office with spares just for such work but may not soon as our last desktops are removed. Don't have as many as before.

That said, if a full reload fixes it, that's a fix too.

- Collapse -
My previous corrective attempts
Mar 1, 2018 11:00AM PST

I did previously replace the Ethernet cable with a much shorter one when I moved the router.

I also connected via WiFi instead of hardwired. My Ethernet port is on the motherboard but the WiFi card is a plug-in.

I had failures in both configurations. Therefore, I assumed that neither the on-board Ethernet port nor the cable were the cause of the problem.

As you suggest, a full router reboot is a fix but it is a pain in the butt and I shouldn't have to do it. There is something causing the problem and I'd like to find and fix the problem.

- Collapse -
Here's an oddity.
Mar 2, 2018 3:25PM PST

"The maximum IP addresses that could be assigned on my LAN is 10."

That's well under the stock settings I've seen on any router. What else is not stock.

- Collapse -
Answer
Status Update
Mar 6, 2018 7:21AM PST

While I'd really like to determine the cause and fix the problem, now I just want the problem to go away. Given all the trouble shooting that I have done, I'm pretty sure that the problem lies in the DHCP part of the cable modem/router. However, the router has been replaced and the problem still exists.

Therefore, here is my latest attempt....
-I have a good ASUS router from my previous configuration.
-I have connected it to the output of the troublesome cable router/modem.
-The ASUS router WAN has been assigned a static IP address (to avoid the DHCP auto assigning process).
-Both desktop PCs are assigned static IP addresses from the cable modem/router
-Half of the wireless LAN clients are connected to the cable modem/router.
-Half of the wireless LAN clients are connected to ASUS router.

Here's my assumption....
If the WiFi clients connected to the cable modem/router fail and those connected to the ASUS router do not fail, then the problem is definitely the cable modem/router. If that's the situation, I can go to battle with the cable company. Alternatively, I can merely have all WiFi clients connect to the ASUS router and completely avoid the DHCP auto assigning issue in the cable modem/router.

Is my strategy sound?

- Collapse -
It's just OK.
Mar 6, 2018 7:36AM PST

When I see folk setup this, they often complain about the issues of having two LANs.

If that issue comes up, try the common "Router as a WAP" instead.

Here's the google: https://www.google.com/search?q=How+to+use+a+router+as+a+WAP

My thought is something is not stock on settings or there is a real issue with this PC or PC's NIC or cable. Your new networker might be thinking the NIC or cable is OK because it worked on another network or another PC on this connection. What you learn over time is that you have to keep an open mind and have spare NICs.

- Collapse -
Further info
Mar 6, 2018 12:32PM PST

If I understand the info in your link, that second router would simply act as an extension of the main router. That way, the number of Ethernet ports would be increased or the second router could be located in a remote location to extend the range of the LAN.

What I'm attempting to do is set up two separate LANs that each utilize their own DHCP server. i.e. I'm trying to prove that the DHCP server on the original cable modem/router isn't working properly.

Here's what I expect to see....
-if the cable modem/router DHCP fails, the WiFi clients connecting to that router will be assigned IP addresses in the 169.254.165.XX range. At the same time, the WiFi clients connecting to the ASUS router will be assigned correct IP addresses.

Am I "out to lunch"?

- Collapse -
The thing is.
Mar 6, 2018 12:51PM PST

You should have completed the tests by now.

As to two LANs, your design so my comments is more about what the majority sets up.

- Collapse -
Still Waiting
Mar 6, 2018 1:33PM PST

It will take a while to fully complete my test.

I don't see the failure consistently. It seems very random. i.e. about once a week or so.

So far both LANs are working as they should. If and when I get a failure, I'll look at the WiFi clients on both networks to see if my theory is borne out.

I'll post my results.

- Collapse -
have you checked...
Mar 6, 2018 6:56PM PST

...the MAC blocking on the problem or suspect router? Checked router firewall? Parental control area?

- Collapse -
Answer
Update
Mar 7, 2018 12:28PM PST

My problem solving seems to be effective in identifying the source of the issue.

I've just had another failure.
-the Wifi devices connecting to the cable modem/router LAN were unable to get a correct IPv4 address. They got a 169.254.x.x address.
0the Wifi devices connecting to the ASUS router were able to get a correct IPv4 address.

To me, this proves that the problem is the DHCP autoconfiguration process in the cable modem/router.

Armed with this information, I called my ISP (Rogers in Canada). After a lengthy discussion with both their front line tech and their Level 2 tech, they advised me that this is a known problem and they are working on a fix. It was a little unclear but it sounded like the firmware fix was still in the Beta stage. They indicated that they would download a firmware upgrade to my cable router/modem (Hintron CODA 4582).

I'll post back with the results of this fix.

- Collapse -
Next Chapter
Mar 13, 2018 9:28AM PDT

Well the new firmware didn't fix the problem. I had two subsequent failures.

I'm still dealing with Rogers in an attempt to solve the problem. However, they don't seem to have a ready answer. I've had a look at their forum and others have reported the same problem with this and older modem/routers.

In the meantime, does anyone have any suggestions that haven't been previously mentioned in this post?

Post was last edited on March 13, 2018 9:29 AM PDT

- Collapse -
No Resolution
Mar 24, 2018 7:15AM PDT

I've finally given up and resorted to an expedient answer rather than getting the problem solved. I again talked at length with Rogers (ISP) techs and they have been unable to provide a solution. They tell me that they have given me the latest firmware and they have no other reports of this same problem with the Hintron CODA 4582 modem/router. (This really isn't true since I have seen similar problems posted on various forums.)

In short, my Rogers Hintron CODA 4582 modem router randomly fails to assign correct IPv4 addresses using the autoconfiguration process of the HDCP. A 169.x.x.x address is assigned instead. (It correctly assigns IPv6 address). A modem reboot will temporarily resolve the problem but it returns. If anyone else is experiencing this issue, please report it to Rogers so that they become convinced of the problem and work to solve it.

In the meantime, here is my expedient solution:
- all my network devices that have the capability of being assigned a static IP address are so assigned.
- I have separate router connected to the output of the Rogers modem/router and assigned a static IPv4 address. All my WiFi devices that do not have the capability to be assigned a static IP address are set up to connect to this router rather than the Rogers modem/router.
This solves my connectivity problem but does not fix the Hintron CODA 4582 problem.

Thank you to everyone that provided suggestions.

Post was last edited on March 24, 2018 12:20 PM PDT