Comcast customers: will Firmware V3.01.14 fix my N450 (CG3000Dv2) connectivity issues?

[MayBTime2Change]

For the past half a year, my N450 (CG3000Dv2) cabel modem router has been completely unreliable. It regularly drops connection. Sometimes restarting helps, sometimes it doesn't. I've rebooted the box a couple times, and that helps for maybe a day, sometimes less. This connectivity issue seems to be a common complaint for N450, and also seems to be tied to the V3.01.06 firmware (makes sense to me, based on when my problems started). I see that V3.01.14 has been pushed by Comcast to its customers. Any Comcast N450 customers on here who had connectivity issues with V3.01.06? And if so, did those problems go away with V3.01.14? I have Spectrum, which is still using V3.01.06.

It's really frustrating to be experiencing this problem, especially since I had suffered through the same issue over a year ago. That time, the probably spontaneously resolved, presumably when the Firmware was updated. I think it happened around the same time as the Time Warner Cable merger with Charter, and this time the problem seems to correspond with the mergers with Spectrum.

[DarrenM]

Hello MayBTime2Change

Are you just having wifi connection issues or is the modem dropping wired and wireless connections?

DarrenM

[MayBTime2Change]

---

@DarrenM wrote:

Hello MayBTime2Change

Are you just having wifi connection issues or is the modem dropping wired and wireless connections?

DarrenM

---

Great question - it's dropping both. We use wireless for most of our devices, but our Apple TV is hooked up to the modem directly and also gets dropped.

[DarrenM]

Can you post the modems logs when these drops are happening.

DarrenM

[MayBTime2Change]

And here are some data from the "Logs":

 
[Description Count]     Last     Occurrence

[TCP- or UDP-based Port Scan ] 1 Sat Jun 24 16:57:24 2017

[Internet connected ] 1 Sat Jun 24 16:54:52 2017

[TCP- or UDP-based Port Scan ] 1 Sat Jun 24 16:54:52 2017

[Firewall Up ] 1 Sat Jun 24 16:54:47 2017

[Public Network Interface up ] 1 Sat Jun 24 16:54:47 2017

[Time Of Day established ] 1 Sat Jun 24 16:54:28 2017

[Internet disconnected ] 1 Sat Jun 24 16:53:59 2017

[SUCCESS: User interface login ] 1 Sat Jun 24 16:52:27 2017

[FAILURE: User interface login ] 1 Sat Jun 24 16:52:06 2017

[TCP- or UDP-based Port Scan ] 1 Sat Jun 24 16:50:17 2017

[Internet connected ] 1 Sat Jun 24 16:50:17 2017

[Firewall Up ] 1 Sat Jun 24 16:50:11 2017

[Public Network Interface up ] 1 Sat Jun 24 16:50:11 2017

[Time Of Day established ] 1 Sat Jun 24 16:49:53 2017

[Internet disconnected ] 1 Sat Jun 24 16:49:07 2017

[Internet connected ] 1 Sat Jun 24 16:47:16 2017

[TCP- or UDP-based Port Scan ] 1 Sat Jun 24 16:47:12 2017

[Firewall Up ] 1 Sat Jun 24 16:47:11 2017

[Public Network Interface up ] 1 Sat Jun 24 16:47:11 2017

[Time Of Day established ] 1 Sat Jun 24 16:46:52 2017

[Internet disconnected ] 1 Sat Jun 24 16:46:12 2017

[Internet connected ] 1 Sat Jun 24 16:44:10 2017

[Firewall Up ] 1 Sat Jun 24 16:44:05 2017

[Public Network Interface up ] 1 Sat Jun 24 16:44:05 2017

[Time Of Day established ] 1 Sat Jun 24 16:43:45 2017

[Internet disconnected ] 1 Sat Jun 24 16:43:12 2017

[Internet connected ] 1 Sat Jun 24 16:42:20 2017

[Firewall Up ] 1 Sat Jun 24 16:42:16 2017

[Public Network Interface up ] 1 Sat Jun 24 16:42:16 2017

[TCP- or UDP-based Port Scan ] 1 Sat Jun 24 16:42:14 2017

[MayBTime2Change]

And here are some data from the "Logs":

 
[Description Count]     Last     Occurrence

[TCP- or UDP-based Port Scan ] 1 Sat Jun 24 16:57:24 2017

[Internet connected ] 1 Sat Jun 24 16:54:52 2017

[TCP- or UDP-based Port Scan ] 1 Sat Jun 24 16:54:52 2017

[Firewall Up ] 1 Sat Jun 24 16:54:47 2017

[Public Network Interface up ] 1 Sat Jun 24 16:54:47 2017

[Time Of Day established ] 1 Sat Jun 24 16:54:28 2017

[Internet disconnected ] 1 Sat Jun 24 16:53:59 2017

[SUCCESS: User interface login ] 1 Sat Jun 24 16:52:27 2017

[FAILURE: User interface login ] 1 Sat Jun 24 16:52:06 2017

[TCP- or UDP-based Port Scan ] 1 Sat Jun 24 16:50:17 2017

[Internet connected ] 1 Sat Jun 24 16:50:17 2017

[Firewall Up ] 1 Sat Jun 24 16:50:11 2017

[Public Network Interface up ] 1 Sat Jun 24 16:50:11 2017

[Time Of Day established ] 1 Sat Jun 24 16:49:53 2017

[Internet disconnected ] 1 Sat Jun 24 16:49:07 2017

[Internet connected ] 1 Sat Jun 24 16:47:16 2017

[TCP- or UDP-based Port Scan ] 1 Sat Jun 24 16:47:12 2017

[Firewall Up ] 1 Sat Jun 24 16:47:11 2017

[Public Network Interface up ] 1 Sat Jun 24 16:47:11 2017

[Time Of Day established ] 1 Sat Jun 24 16:46:52 2017

[Internet disconnected ] 1 Sat Jun 24 16:46:12 2017

[Internet connected ] 1 Sat Jun 24 16:44:10 2017

[Firewall Up ] 1 Sat Jun 24 16:44:05 2017

[Public Network Interface up ] 1 Sat Jun 24 16:44:05 2017

[Time Of Day established ] 1 Sat Jun 24 16:43:45 2017

[Internet disconnected ] 1 Sat Jun 24 16:43:12 2017

[Internet connected ] 1 Sat Jun 24 16:42:20 2017

[Firewall Up ] 1 Sat Jun 24 16:42:16 2017

[Public Network Interface up ] 1 Sat Jun 24 16:42:16 2017

[TCP- or UDP-based Port Scan ] 1 Sat Jun 24 16:42:14 2017

[MayBTime2Change]

Sorry for the late reply - we have a new baby in the house, so it's a bit crazy. I'm a novice, so I'm not sure which logs you want or how to post them in table form, but here are some data from the "Event Log":

Time Priority Description

2017-06-24, 16:54:29.0 Error (4) Missing BP Configuration Setting TLV Type: 17.8;

2017-06-24, 16:54:29.0 Error (4) Missing BP Configuration Setting TLV Type: 17.9;

2017-06-24, 16:54:28.0 Warning (5) DHCP WARNING - Non-critical field invalid in response ;

2017-06-24, 16:54:26.0 Notice (6) Honoring MDD; IP provisioning mode = IPv4

2017-06-24, 16:54:18.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;

2017-06-24, 16:54:11.0 Critical (3) No Ranging Response received - T3 time-out;

2017-06-24, 16:53:58.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;

2017-06-24, 16:53:25.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;

2017-06-24, 16:49:53.0 Warning (5) DHCP WARNING - Non-critical field invalid in response ;

2017-06-24, 16:49:53.0 Error (4) Missing BP Configuration Setting TLV Type: 17.8;

2017-06-24, 16:49:53.0 Error (4) Missing BP Configuration Setting TLV Type: 17.9;

2017-06-24, 16:49:48.0 Critical (3) DHCP FAILED - Discover sent, no offer received;

2017-06-24, 16:49:35.0 Notice (6) Honoring MDD; IP provisioning mode = IPv4

2017-06-24, 16:49:22.0 Critical (3) No Ranging Response received - T3 time-out;

2017-06-24, 16:49:05.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;

2017-06-24, 16:48:33.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;

2017-06-24, 16:46:53.0 Warning (5) DHCP WARNING - Non-critical field invalid in response ;

2017-06-24, 16:46:53.0 Error (4) Missing BP Configuration Setting TLV Type: 17.8;

2017-06-24, 16:46:53.0 Error (4) Missing BP Configuration Setting TLV Type: 17.9;

2017-06-24, 16:46:48.0 Critical (3) DHCP FAILED - Discover sent, no offer received;

2017-06-24, 16:46:35.0 Notice (6) Honoring MDD; IP provisioning mode = IPv4

2017-06-24, 16:46:29.0 Critical (3) No Ranging Response received - T3 time-out;

2017-06-24, 16:46:12.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;

2017-06-24, 16:45:38.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;

2017-06-24, 16:43:46.0 Warning (5) DHCP WARNING - Non-critical field invalid in response ;

2017-06-24, 16:43:46.0 Error (4) Missing BP Configuration Setting TLV Type: 17.8;

2017-06-24, 16:43:46.0 Error (4) Missing BP Configuration Setting TLV Type: 17.9;

2017-06-24, 16:43:42.0 Notice (6) Honoring MDD; IP provisioning mode = IPv4

2017-06-24, 16:43:36.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;

2017-06-24, 16:43:23.0 Critical (3) No Ranging Response received - T3 time-out;

2017-06-24, 16:43:11.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;

2017-06-24, 16:42:38.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;

[DarrenM]

Hello MayBTime2Change

You have alot of T4 and T3 timeouts typically that says there is a signal issue so it would be a issue in the lines coming in your home or the ones outside. You will want to have your ISP send a tech to check things out.

DarrenM

[MayBTime2Change]

Hi DarrenM

I was on the phone with my ISP and they're sending someone out. They said that typically T3 errors are modem-related and T4 errors are line-related? But the frequency of the errors made them suspect there was a problem beyond the modem? I guess I'll know more tomorrow.

Thanks