Quantcast
Channel: Cox forum - dslreports.com
Viewing all articles
Browse latest Browse all 5880

T3-T4 timeouts on CM600 reason for packet loss on Gforce Now?

$
0
0
Hello. Network here 300MBPS down, 30MBPS up cox. Equipment CM600 and a Nighthawk AC1900 - Separate units. Getting great speeds wireless and hardwired. Now, I got a Nvidia shield a couple of weeks ago and i signed up for the Gforce now. Gaming is absolutely horrible on it. There own specs show optimal for that service. yet all games, played show major packet loss and games are impossible to play. I tested the hardwired line to the shield and speeds show all good. ran pingtest and others which show no packet loss. I attached a few images of tests and the screen of one game. Don't matter which one though, they all do the same thing. Despite Kodi, Xbox one etc all doing great on wired side of things, games on the shield are not (streaming service) - I did write Nvidia and they claim even though images show no packet loss, yet the system does it must be my internet. So I wanted to show you guys what my logs show via modem and your thoughts. 2016-06-13, 13:21:52 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-********************;CMTS-********************;CM-QOS=1.1;CM-VER=3.0; 2016-06-13, 13:21:09 Notice (6) TLV-11 - unrecognized OID;CM-********************;CMTS-********************;CM-QOS=1.1;CM-VER=3.0; 2016-06-13, 13:20:20 Critical (3) Resetting the cable modem due to docsDevResetNow 2016-06-10, 04:13:55 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-********************;CMTS-********************;CM-QOS=1.1;CM-VER=3.0; 2016-06-09, 23:16:55 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-********************;CMTS-********************;CM-QOS=1.1;CM-VER=3.0; 2016-06-09, 11:17:51 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-********************;CMTS-********************;CM-QOS=1.1;CM-VER=3.0; 2016-05-27, 11:37:04 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-********************;CMTS-********************;CM-QOS=1.1;CM-VER=3.0; 2016-05-23, 13:05:51 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-********************;CMTS-********************;CM-QOS=1.1;CM-VER=3.0; 2016-05-21, 19:35:42 Critical (3) No Ranging Response received - T3 time-out;CM-********************;CMTS-********************;CM-QOS=1.1;CM-VER=3.0; 2016-05-21, 19:32:38 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-********************;CMTS-********************;CM-QOS=1.1;CM-VER=3.0; 2016-05-21, 19:32:00 Critical (3) No Ranging Response received - T3 time-out;CM-********************;CMTS-********************;CM-QOS=1.1;CM-VER=3.0; 2016-05-20, 09:14:59 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-********************;CMTS-********************;CM-QOS=1.1;CM-VER=3.0; 2016-05-19, 04:33:59 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-********************;CMTS-********************;CM-QOS=1.1;CM-VER=3.0; 2016-05-19, 04:31:24 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-********************;CMTS-********************;CM-QOS=1.1;CM-VER=3.0; 2016-05-19, 04:31:10 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-********************;CMTS-********************;CM-QOS=1.1;CM-VER=3.0; 2016-05-19, 00:56:21 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-********************;CMTS-********************;CM-QOS=1.1;CM-VER=3.0; 2016-05-19, 00:55:29 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-********************;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2016-05-19, 00:55:27 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-********************;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2016-05-19, 00:55:26 Critical (3) No UCDs Received - Timeout;;CM-********************;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2016-05-19, 00:55:09 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-********************;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2016-05-19, 00:55:06 Critical (3) No UCDs Received - Timeout;;CM-********************;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2016-05-19, 00:54:49 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-********************;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2016-05-19, 00:54:46 Critical (3) No UCDs Received - Timeout;;CM-********************;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2016-05-19, 00:54:29 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-********************;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2016-05-19, 00:54:26 Critical (3) No UCDs Received - Timeout;;CM-********************;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2016-05-19, 00:54:09 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-********************;CMTS-********************;CM-QOS=1.0;CM-VER=3.0; 2016-05-19, 00:53:37 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-********************;CMTS-********************;CM-QOS=1.0;CM-VER=3.0; 2016-05-19, 00:53:14 Critical (3) No UCDs Received - Timeout;;CM-********************;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2016-05-19, 00:52:57 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-********************;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2016-05-19, 00:52:54 Critical (3) No UCDs Received - Timeout;;CM-********************;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2016-05-19, 00:52:36 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-********************;CMTS-********************;CM-QOS=1.0;CM-VER=3.0; 2016-05-19, 00:51:33 Critical (3) DHCP FAILED - Discover sent, no offer received;CM-********************;CMTS-********************;CM-QOS=1.0;CM-VER=3.0; 2016-05-19, 00:50:24 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-********************;CMTS-********************;CM-QOS=1.0;CM-VER=3.0; 2016-05-19, 00:50:24 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-********************;CMTS-********************;CM-QOS=1.0;CM-VER=3.0; 2016-05-19, 00:50:23 Critical (3) DHCP FAILED - Discover sent, no offer received;CM-********************;CMTS-********************;CM-QOS=1.0;CM-VER=3.0; 2016-05-19, 00:47:07 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-********************;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Time Not Established Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-********************;CMTS-********************;CM-QOS=1.0;CM-VER=3.0; Time Not Established Notice (6) Honoring MDD; IP provisioning mode = IPv4 Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-********************;CMTS-********************;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-********************;CMTS-********************;CM-QOS=1.0;CM-VER=3.0; This field below allows you to modify the frequency the cable modem start with its scan during initialization and registration. Enter the new start frequency and restart the cable modem for it to take effect. Starting Frequency 819000000 Startup Procedure Procedure Status Comment Acquire Downstream Channel 807000000 Hz Locked Connectivity State OK Operational Boot State OK Operational Security Enable BPI+ IP Provisioning Mode Honor MDD IPv4 only Downstream Bonded Channels Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables 1 Locked QAM256 2 807000000 Hz -1.8 dBmV 39.1 dB 3 0 2 Locked QAM256 1 801000000 Hz -2.7 dBmV 38.8 dB 107 6 3 Locked QAM256 4 819000000 Hz -1.3 dBmV 39.4 dB 3 0 4 Locked QAM256 3 813000000 Hz -1.7 dBmV 39.4 dB 3 0 5 Locked QAM256 5 825000000 Hz -1.3 dBmV 39.6 dB 3 0 6 Locked QAM256 6 831000000 Hz -1.3 dBmV 39.6 dB 0 0 7 Locked QAM256 7 837000000 Hz -1.5 dBmV 39.5 dB 42 0 8 Locked QAM256 8 843000000 Hz -1.7 dBmV 39.4 dB 6 0 9 Locked QAM256 9 849000000 Hz -1.6 dBmV 39.4 dB 4 0 10 Locked QAM256 10 855000000 Hz -1.5 dBmV 39.5 dB 7 0 11 Locked QAM256 11 861000000 Hz -1.3 dBmV 39.4 dB 7 0 12 Locked QAM256 12 867000000 Hz -1.2 dBmV 39.4 dB 19 0 13 Locked QAM256 19 909000000 Hz -1.0 dBmV 39.1 dB 260 0 14 Locked QAM256 20 915000000 Hz -1.0 dBmV 39.0 dB 24 0 15 Locked QAM256 21 921000000 Hz -1.0 dBmV 39.1 dB 40 0 16 Locked QAM256 22 927000000 Hz -1.2 dBmV 39.1 dB 14 0 17 Locked QAM256 23 933000000 Hz -1.3 dBmV 39.8 dB 0 0 18 Locked QAM256 24 939000000 Hz -1.2 dBmV 39.9 dB 0 0 19 Locked QAM256 49 945000000 Hz -1.6 dBmV 39.4 dB 0 0 20 Locked QAM256 50 951000000 Hz -1.5 dBmV 39.4 dB 0 0 21 Locked QAM256 51 957000000 Hz -2.1 dBmV 39.3 dB 0 0 22 Locked QAM256 52 963000000 Hz -1.8 dBmV 39.4 dB 0 0 23 Locked QAM256 53 969000000 Hz -1.9 dBmV 39.4 dB 0 0 24 Locked QAM256 54 975000000 Hz -2.3 dBmV 39.1 dB 0 0 Upstream Bonded Channels Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power 1 Locked ATDMA 2 5120 Ksym/sec 23300000 Hz 42.3 dBmV 2 Locked TDMA and ATDMA 1 2560 Ksym/sec 18400000 Hz 41.8 dBmV 3 Locked ATDMA 3 5120 Ksym/sec 29800000 Hz 42.3 dBmV 4 Locked ATDMA 4 5120 Ksym/sec 36300000 Hz 44.3 dBmV I have reset modem and router to see if that would help... It did not. reset from cox site also, did not help. Router firmware from netgear current on nighthawk. if you guys see anything here that could point to why I am having issues it would be much appreciated. Anyways, thank you for your time. -- Videocard: AMD Radeon HD 5970 Processor: i7 930 Mainboard: P6X58D Memory: Corsair VoyagerGT 6GB(3 x 2GB)

Viewing all articles
Browse latest Browse all 5880

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>