New Poster
•
2 Messages
Packet Loss
Hello, for the past few weeks I've been having connection issues on WoW. Connection used to be perfect but recently I started to have issues high ping. When I ran a tracert to the IP address for the server that Blizzard provides, I get some *, which I honeslty do not know what it means, but I also get "Request Timed Out" in the trace. When I checked my logs for my modem I found that there were a TON of T3 errors. To note, I get packet loss to google and youtube. This may not change anything but I just wanted to add that I get packets loss not only from Blizzard but with other services as well. As far as internet connection goes, my internet does not drop to the point where i can't connect to it. It has not completely gone down once. But the issue with WoW is something that I would like to get resolved.
System Log
| Time | Priority | Description |
|---|---|---|
| Tue Jun 09 22:27:42 2020 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=98:de:d0:70:0e:42;CMTS-MAC=00:90:f0:07:01:00;... |
| Time Not Established | Notice (6) | Honoring MDD; IP provisioning mode = IPv6 |
| Tue Jun 09 19:52:21 2020 | Critical (3) | Resetting the cable modem due to docsDevResetNow |
| Tue Jun 09 19:50:35 2020 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=98:de:d0:70:0e:42;CMTS-MAC=00:90:f0:07:01:00;... |
| Sat Jun 06 14:58:22 2020 | Critical (3) | Resetting the cable modem due to docsDevResetNow |
| Sat Jun 06 14:56:58 2020 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=98:de:d0:70:0e:42;CMTS-MAC=00:90:f0:07:01:00;... |
| Time Not Established | Critical (3) | TFTP failed - configuration file NOT FOUND;CM-MAC=98:de:d0:70:0e:42;CMTS-MAC=00:90:f0:07:01:00;CM-QOS=1.0;CM-VER=3.0; |
| Time Not Established | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=98:de:d0:70:0e:42;CMTS-MAC=00:00:00:00... |
| Sat Jun 06 14:34:53 2020 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=98... |
| Sat Jun 06 14:34:53 2020 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=98:de:d0:70:0e:42;CMTS-MAC=00:90:f0:07... |
| Sat Jun 06 14:34:50 2020 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=98... |
| Sat Jun 06 14:34:50 2020 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=98:de:d0:70:0e:42;CMTS-MAC=00:90:f0:07... |
| Sat Jun 06 14:34:44 2020 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=98... |
| Sat Jun 06 14:34:44 2020 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=98:de:d0:70:0e:42;CMTS-MAC=00:90:f0:07... |
| Sat Jun 06 14:34:42 2020 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=98... |
| Sat Jun 06 14:34:42 2020 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=98:de:d0:70:0e:42;CMTS-MAC=00:90:f0:07... |
| Sat Jun 06 14:34:34 2020 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=98:de:d0:70:0e:42;CMTS-MAC=00:90:f0:07:01:00;CM-QO... |
| Sat Jun 06 14:34:30 2020 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=98:de:d0:70:0e:42;CMTS-MAC=00:90:f0:07... |
| Sat Jun 06 14:34:02 2020 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=98:de:d0:70:0e:42;CMTS-MAC=00:90:f0:07... |
| Sat Jun 06 14:33:55 2020 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=98:de:d0:70:0e:42;CMTS-MAC=00:90:f0:07... |
| Sat Jun 06 14:33:43 2020 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=98:de:d0:70:0e:42;CMTS-MAC=00:90:f0:07:01:00;... |
| Sat Jun 06 02:03:45 2020 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=98:de:d0:70:0e:42;CMTS-MAC=00:90:f0:07:01:00;CM-QOS=1.1;CM-VER=3.0; |
| Sat Jun 06 02:03:20 2020 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=98:de:d0:70:0e:42;CMTS-MAC=00:00:00:00... |
| Sat Jun 06 02:02:36 2020 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=98... |
| Sat Jun 06 02:02:36 2020 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=98:de:d0:70:0e:42;CMTS-MAC=00:90:f0:07... |
| Sat Jun 06 02:02:34 2020 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=98... |
| Sat Jun 06 02:02:34 2020 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=98:de:d0:70:0e:42;CMTS-MAC=00:90:f0:07... |
| Sat Jun 06 02:02:28 2020 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=98... |
| Sat Jun 06 02:02:28 2020 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=98:de:d0:70:0e:42;CMTS-MAC=00:90:f0:07... |
| Sat Jun 06 02:02:21 2020 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=98... |
| Sat Jun 06 02:02:21 2020 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=98:de:d0:70:0e:42;CMTS-MAC=00:90:f0:07... |
| Sat Jun 06 02:01:41 2020 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=98:de:d0:70:0e:42;CMTS-MAC=00:90:f0:07... |
Start Up Procedure
| Procedure | Status | Comment |
|---|---|---|
| Acquire Downstream Channel | 525000000 Hz | Locked |
| Connectivity State | OK | Operational |
| Boot State | OK | Operational |
| Configuration File | OK | d11_m_tc7610_silver_c01.cm |
| Security | Enabled | BPI+ |
Downstream Bonded Channels
| Channel | Status | Modulation | Channel ID | Frequency | Power | SNR |
|---|---|---|---|---|---|---|
| 1 | Locked | QAM256 | 9 | 525000000 Hz | -3.2 dBmV | 43.9 dB |
| 2 | Locked | QAM256 | 10 | 531000000 Hz | -3.0 dBmV | 43.7 dB |
| 3 | Locked | QAM256 | 11 | 537000000 Hz | -2.8 dBmV | 41.9 dB |
| 4 | Locked | QAM256 | 12 | 543000000 Hz | -2.8 dBmV | 42.1 dB |
| 5 | Locked | QAM256 | 13 | 555000000 Hz | -2.5 dBmV | 42.5 dB |
| 6 | Locked | QAM256 | 14 | 561000000 Hz | -2.4 dBmV | 42.4 dB |
| 7 | Locked | QAM256 | 15 | 567000000 Hz | -2.5 dBmV | 42.5 dB |
| 8 | Locked | QAM256 | 16 | 573000000 Hz | -2.3 dBmV | 42.5 dB |
Upstream Bonded Channels
| Channel | Status | Channel Type | Channel ID | Symbol Rate | Frequency | Power |
|---|---|---|---|---|---|---|
| 1 | Locked | ATDMA | 1 | 5120 ksym/sec | 16600000 Hz | 44.0 dBmV |
| 2 | Locked | ATDMA | 2 | 5120 ksym/sec | 23000000 Hz | 44.7 dBmV |
| 3 | Locked | ATDMA | 3 | 5120 ksym/sec | 29400000 Hz | 45.0 dBmV |
| 4 | Locked | ATDMA | 4 | 5120 ksym/sec | 35800000 Hz |
45.0 dBmV |
cewebb10
Regular Visitor
•
3 Messages
5 years ago
I'm having the same issues here but with Everquest not WoW lol. Following in case u get a reply as I've not gotten one yet on my thread.
0
0