Spectator

TGsixteenseventytwoG

I have a touchstone TGsixteenseventytwoG modem and I have read online that it has a intel puma six chipset that has problems.  I decided to look for this problem with my modem after having experienced alot of latency issues wih my modem I called spectrum and they said they saw on my end they saw problems with my modem it keeps timing out and told me they saw timed out in logs or something I looked in my logs and I see unpriv packets a bunch Ill go back and post my logs here if it helps.

 

I have read from MsRaye that the router in the TGsixteenseventytwoG is crap so Im trying to install my router and seeing if that fixes anything.  Please let me know if my problem can be fixed please and thank you.

7 REPLIES
Expert

Re: TGsixteenseventytwoG

Need the signal level and error log pages, you posted the IP log which does us no good...

 

Spectator

Re: TGsixteenseventytwoG

Ok it says I cant post?  Let me see if this works.

Spectator

Re: TGsixteenseventytwoG

I should have realized those were the ip logs my bad.  I got access to the HSD my firewall was blocking the ip address this should be the signal levels:

 

Downstream

 DCIDFreqPowerSNRModulationOctetsCorrectedsUncorrectables
Downstream 19627.00 MHz0.10 dBmV37.36 dB256QAM1334685519920
Downstream 211639.00 MHz-0.20 dBmV37.36 dB256QAM13129773270170
Downstream 312645.00 MHz0.20 dBmV37.64 dB256QAM1061747881500
Downstream 413651.00 MHz0.10 dBmV37.64 dB256QAM1118109060520
Downstream 514657.00 MHz0.00 dBmV37.36 dB256QAM10551526904160
Downstream 615663.00 MHz0.40 dBmV37.64 dB256QAM1044527943310
Downstream 716669.00 MHz0.50 dBmV37.36 dB256QAM1140092209320
Downstream 817675.00 MHz0.50 dBmV37.64 dB256QAM10871234907461
Downstream 918681.00 MHz0.70 dBmV37.36 dB256QAM11679462333610
Downstream 1020693.00 MHz0.70 dBmV37.36 dB256QAM12973220501260
Downstream 1121699.00 MHz0.80 dBmV37.36 dB256QAM12128777949250
Downstream 1223711.00 MHz1.00 dBmV37.36 dB256QAM1262093440400
Downstream 1325723.00 MHz0.80 dBmV36.61 dB256QAM1233772933990
Downstream 1428741.00 MHz0.80 dBmV36.61 dB256QAM1303425614360
Downstream 1530753.00 MHz0.50 dBmV36.61 dB256QAM1327346900180
Downstream 1631759.00 MHz0.20 dBmV36.61 dB256QAM1320055079010
Reset FEC Counters

Upstream

 UCIDFreqPowerChannel TypeSymbol RateModulation
Upstream 15637.00 MHz48.25 dBmVDOCSIS2.0 (ATDMA)5120 kSym/s64QAM
Upstream 25530.60 MHz48.00 dBmVDOCSIS2.0 (ATDMA)5120 kSym/s64QAM
Upstream 35424.20 MHz47.25 dBmVDOCSIS2.0 (ATDMA)5120 kSym/s64QAM
Upstream 45319.40 MHz46.25 dBmVDOCSIS1.x (TDMA)2560 kSym/s16QAM

 

 Status
System Uptime:9 d: 22 h: 21 m
Computers Detected:staticCPE(2), dynamicCPE(0)
CM Status:Telephony-Reg Complete
Time and Date:Wed 2018-01-10 15:21:40

 

 Interface Parameters
Interface NameProvisionedStateSpeed (Mbps)MAC address
LAN Port 1EnabledUp100(Full)E8:ED:05:5B:44:51
LAN Port 2EnabledDown-----E8:ED:05:5B:44:51
LAN Port 3EnabledUp1000(Full)E8:ED:05:5B:44:51
LAN Port 4EnabledDown-----E8:ED:05:5B:44:51
CABLEEnabledUp-----E8:ED:05:5B:44:52
MTAPassUp-----E8:ED:05:5B:44:53

 

This should be the Error Logs:

 

DOCSIS(CM) Events

 

Date TimeEvent IDEvent LevelDescription
1/6/2018 7:07820002003No Ranging Response received - T3 time-out;CM-MAC=e8:ed:05:5b:44:52;CMTS-MAC=00:01:5c:7c:40:58;CM-QOS=1.1;CM-VER=3.0;
1/6/2018 7:08820009005B-INIT-RNG Failure - Retries exceeded;CM-MAC=e8:ed:05:5b:44:52;CMTS-MAC=00:01:5c:7c:40:58;CM-QOS=1.1;CM-VER=3.0;
1/6/2018 7:08820002003No Ranging Response received - T3 time-out;CM-MAC=e8:ed:05:5b:44:52;CMTS-MAC=00:01:5c:7c:40:58;CM-QOS=1.1;CM-VER=3.0;
1/6/2018 7:09820009005B-INIT-RNG Failure - Retries exceeded;CM-MAC=e8:ed:05:5b:44:52;CMTS-MAC=00:01:5c:7c:40:58;CM-QOS=1.1;CM-VER=3.0;
1/6/2018 7:09820002003No Ranging Response received - T3 time-out;CM-MAC=e8:ed:05:5b:44:52;CMTS-MAC=00:01:5c:7c:40:58;CM-QOS=1.1;CM-VER=3.0;
1/6/2018 17:43820004003Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=e8:ed:05:5b:44:52;CMTS-MAC=00:01:5c:7c:40:58;CM-QOS=1.1;CM-VER=3.0;
1/6/2018 17:44820002003No Ranging Response received - T3 time-out;CM-MAC=e8:ed:05:5b:44:52;CMTS-MAC=00:01:5c:7c:40:58;CM-QOS=1.1;CM-VER=3.0;
1/6/2018 17:45820009005B-INIT-RNG Failure - Retries exceeded;CM-MAC=e8:ed:05:5b:44:52;CMTS-MAC=00:01:5c:7c:40:58;CM-QOS=1.1;CM-VER=3.0;
1/6/2018 17:45820002003No Ranging Response received - T3 time-out;CM-MAC=e8:ed:05:5b:44:52;CMTS-MAC=00:01:5c:7c:40:58;CM-QOS=1.1;CM-VER=3.0;
1/6/2018 17:47820009005B-INIT-RNG Failure - Retries exceeded;CM-MAC=e8:ed:05:5b:44:52;CMTS-MAC=00:01:5c:7c:40:58;CM-QOS=1.1;CM-VER=3.0;
1/6/2018 17:47820002003No Ranging Response received - T3 time-out;CM-MAC=e8:ed:05:5b:44:52;CMTS-MAC=00:01:5c:7c:40:58;CM-QOS=1.1;CM-VER=3.0;
1/6/2018 17:48820009005B-INIT-RNG Failure - Retries exceeded;CM-MAC=e8:ed:05:5b:44:52;CMTS-MAC=00:01:5c:7c:40:58;CM-QOS=1.1;CM-VER=3.0;
1/6/2018 17:48820002003No Ranging Response received - T3 time-out;CM-MAC=e8:ed:05:5b:44:52;CMTS-MAC=00:01:5c:7c:40:58;CM-QOS=1.1;CM-VER=3.0;
1/6/2018 17:50820009005B-INIT-RNG Failure - Retries exceeded;CM-MAC=e8:ed:05:5b:44:52;CMTS-MAC=00:01:5c:7c:40:58;CM-QOS=1.1;CM-VER=3.0;
1/6/2018 17:50820002003No Ranging Response received - T3 time-out;CM-MAC=e8:ed:05:5b:44:52;CMTS-MAC=00:01:5c:7c:40:58;CM-QOS=1.1;CM-VER=3.0;
1/6/2018 17:51820009005B-INIT-RNG Failure - Retries exceeded;CM-MAC=e8:ed:05:5b:44:52;CMTS-MAC=00:01:5c:7c:40:58;CM-QOS=1.1;CM-VER=3.0;
1/6/2018 17:51820002003No Ranging Response received - T3 time-out;CM-MAC=e8:ed:05:5b:44:52;CMTS-MAC=00:01:5c:7c:40:58;CM-QOS=1.1;CM-VER=3.0;
1/6/2018 17:53820005003Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=e8:ed:05:5b:44:52;CMTS-MAC=00:01:5c:7c:40:58;CM-QOS=1.1;CM-VER=3.0;
1/6/2018 22:33820002003No Ranging Response received - T3 time-out;CM-MAC=e8:ed:05:5b:44:52;CMTS-MAC=00:01:5c:7c:40:58;CM-QOS=1.1;CM-VER=3.0;
1/10/2018 14:2724171643086Unit has been restored to factory defaults from a software issued command;CM-MAC=e8:ed:05:5b:44:52;CMTS-MAC=00:01:5c:7c:40:58;CM-QOS=1.1;CM-VER=3.0;

 

 PacketCable(MTA) Events

 

Date TimeEvent IDDescription
12/31/2017 17:0226MTA PROV: Successful!
12/31/2017 17:023Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS
1/3/2018 20:263Voice Line State Change, Line Number = 1, Prev State = IS, New State = OOS
1/3/2018 20:2714Power Supply Telemetry Log - BATTERY MISSING
1/3/2018 20:2716MTA TFTP: Successful
1/3/2018 20:2726MTA PROV: Successful!
1/3/2018 20:273Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS
1/4/2018 2:193Voice Line State Change, Line Number = 1, Prev State = IS, New State = OOS
1/4/2018 2:2116MTA TFTP: Successful
1/4/2018 2:2126MTA PROV: Successful!
1/4/2018 2:213Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS
1/4/2018 2:2114Power Supply Telemetry Log - BATTERY MISSING
1/6/2018 6:043Voice Line State Change, Line Number = 1, Prev State = IS, New State = OOS
1/6/2018 6:0714Power Supply Telemetry Log - BATTERY MISSING
1/6/2018 6:0716MTA TFTP: Successful
1/6/2018 6:0726MTA PROV: Successful!
1/6/2018 6:073Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS
1/6/2018 6:103Voice Line State Change, Line Number = 1, Prev State = IS, New State = OOS
1/6/2018 6:1214Power Supply Telemetry Log - BATTERY MISSING
1/6/2018 6:1216MTA TFTP: Successful
1/6/2018 6:1226MTA PROV: Successful!
1/6/2018 6:123Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS
1/6/2018 7:043Voice Line State Change, Line Number = 1, Prev State = IS, New State = OOS
1/6/2018 7:1016MTA TFTP: Successful
1/6/2018 7:1026MTA PROV: Successful!
1/6/2018 7:103Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS
1/6/2018 7:1014Power Supply Telemetry Log - BATTERY MISSING
1/6/2018 17:433Voice Line State Change, Line Number = 1, Prev State = IS, New State = OOS
1/6/2018 17:5314Power Supply Telemetry Log - BATTERY MISSING
1/6/2018 17:5316MTA TFTP: Successful
1/6/2018 17:5326MTA PROV: Successful!
1/6/2018 17:533Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS

 

Let me know if this is all you needed.

Expert

Re: TGsixteenseventytwoG

looks like it's been fine since jan 6th...

some sort of excessive upstream noise before that. maybe it's fixed.

Looks like there was also some broadcast tv ingress.

 

Spectator

Re: TGsixteenseventytwoG

I got this again on the tenth:

 

No Ranging Response received - T3 time-out

 

I read that msraye said this is a upstream issue how can I fix this?  Im going to install that router.  If I use a different router can that fix this or is this something that the intel puma six chipset issue is causing or do I need to have a tech come out.  I typed something up and clicked on post and got a authentication error again.  Also I just recently got a one hundred Mbps speed increase could they have messed up something implementing that?  Please let me know.  When I go on facebook alot of times Ill get the blue circle spinning meaning not all content has loaded and one time yesterday its like all connectivity got lost for about five minutes Im paying alot of money for spectrum this internet service is to expensive not to work the way its supposed to.  Also you mentioned excessive upstream noise is that normal and you also mentioned broadcast tv ingress is that normal I may be new at some of this but Im learning and your helping alot msraye so thank you.

Expert

Re: TGsixteenseventytwoG

needs TWC out, the constant T3's are going to give you fits of bumps in connectivity and resets

 

Highlighted
Spectator

Re: TGsixteenseventytwoG

Ok well the technician came out said the boot file was messed up on my modem and he installed a new ubee modem and everything looked good but now I just got a error message:

 

Your computer appears to be configured correctly but the device or resource (dns server) is not responding.

 

What could cause that?  For your information the error message is from windows seven professional I got it by going to click on network icon in the system tray and then clicked on open network and sharing center and then clicking on local area connection and then diagnose windows seven professional networking diagnostics displays that error.    I have researched that error and tried so many solutions and I am (edited) that the guy said tthrees timed out they dont worry about its the tfour's that I should worry about.  He checked my signal levels and error logs and said everything was good.  I use to get this error message now Im getting it again what is wrong with the connection out here Im so done with all this internet (edited)