> Standard software versioning numbers ... That's the bes...

[mdk]

> Standard software versioning numbers ...

That's the best part of standards -- there are so many of them.

Have you configured all those "self-assigned" IP-addresses on each device? It's something one might do for a networked printer.

Via the router's web-interface, have you "reserved" all those IP-addresses, so that the router's DHCP-server will never assign each IP-address to a device that is making a DHCP-request?

[Kilted_Canuck]

1) Everything is set to get an IP via DHCP. 

2) Only 2 devices are set to a reserved IP. 

This is part of the issue, and I've seen it happen more than once. 

Everything will be working perfectly, everything will have a DHCP-IP in the Hitron Admin. Then the Hitron will glitch, and a device won't be able to connect. (I'm assuming the device tries to renew its lease, and the Hitron doesn't let it. Possibly the DHCP server on the Hitron is crashing?)

When you connect to the Hitron Admin, it will show the device that's not able to connect is "Self-Assigned".

However, since I changed the DHCP lease time from 2 days down to 2 hours, it just happened in a more condensed time frame.  Sometimes it can go for days... sometimes it happens every day. 

As per previous messages.

1) Restarting the device that's not getting an IP does not fix the issue.

2) Renewing lease on the device that's not getting an IP does not fix the issue.

3) Turning off, and back on the LAN DHCP Status in Hitron Admin, does not fix the issue. 

You are able to connect to the Hitron Admin page just fine through the device that won't connect to the internet. 

The only solution appears to be a restart of the Hitron. 

[shaw-tony]

@Kilted_Canuck checking into your account I do see the upstream signal to the modem is out of spec which is likely the cause of your issue. Although the WiFi is available, the modem does not have a solid connection (causing the IPs to reassign each time it gets a connection). Can you tell me if the coax cable from the wall outlet goes through any splitters before it connects to your modem? Are the cables old? For testing, can you connect the modem into another active coax outlet and test the stability of the internet? If the problems persist, a technician will need to be scheduled to check the signal outside your home.

The Hitron's firmware is not a beta software.

[Kilted_Canuck]

Interesting, I haven't had what seems to be "internet issues". (Speed has been great, no slow downloads, etc).  But the outbound connection dropping, and causing it to reset. 

Cables aren't old, and the line in the wall isn't crazy old either (10 years?). 

I'll chat / call in, and get them to run a test on the line while I put it in different locations. (I can move the modem... but, then it wouldn't be connected to most of the network, as a good chunk of it is wired.) So wouldn't really be able to test, since it only happens once in awhile. 

I'll do that and post back. 

[mdk]

> . Standard software versioning numbers, b is for beta, when used on the last digit. a is for Alpha, rc is for release candidate

Now I understand.  I had to watch a bunch of episodes to determine:

• James Kirk captained "NCC-1701",
• that ship was replaced by an "alpha" version: "NCC-1701A",
• that ship was replaced by a "beta" version: "NCC-1701B",
• that ship was replaced by the "NCC-1701C",
• and so on.

Life lawn hand prawn-spear.  🙂