Forum Discussion
Before Blaming the bucket guy you have to consider some things and im not saying he didnt mess up but until your side is pristine condition there is no way to ever convince them its their side of the box with the issues because they do have to check there work and log it. BUT Man its more just increase in traffic with all the people no longer going to work but working at home from their computers you can time it and see what parts of the day are worse than others it's just like the freeway They say we don't share our bandwidth like DSL but at some point of course we do its unavoidable But there are things you can try replacing all connections like couplers where two wires screw together they go out all the time very easily and cause most problems with tv internet anything traveling along that wire basically and the fewer you have the better of course as well, and you can totally rewire your modem line being sure it is split correctly off the main line with good quality RG6 cable with proper ends as well I hate the compression ones usually used by Cox techs as they Loesing and will cause a worse connection then they first gave I like real Crimp style ends with no *** out middle no small or to long Tang or wire and make sure the grounding wire is stripped and done correctly Now that's a little over board maybe but that is what you can do on your side so there is no doubt that it is not your side of the box with problems but theirs which is all the care or will want to fix So if you have a friend or someone like me knowledgeable with RG cabling It's not hard or expensive to get them to do it offer them something and in 2 4 hours you'll have the best possible connection to cox you can do yourself. Now sadly as giga blast customers we are not guaranteed that speed plus you also have to take into effect the server or service you are connecting to as they might not have as great of a connection as you think. But we passed the Load tests now when they stop squeezing every half Shekel out of DOSIC 3.1 and get DOSIC 4.0 available that is when a giga blast will be a giga blast customer with at least a 1gig upload which is the biggest and most important increase needed and 2 to 6gig down load which is probably unneeded truly but That copper line has a lot more to offer than most could imagine cause this is just with a few upgrades to their lines and nothing huge so they can still take it beyond this next level and here in phoenix fiber probably isn't ever coming to your house especially if you knew Who really owned all of it (Hint its a water and power distributor who owns most of Phx infrastructure as my dad who work for them 55 years enlightened to me one day when i brought it up back in google fiber days Its SRP and cox pays them well to keep them on lock) But copper has at least a decade maybe more and is already there and everywhere and is better than fiber to the house in my opinion It has its place and need and its used there properly I watch A whole prison get wired for fiber witched it had already Blown millions of tax payers money runing it thruout their prison to sit unused and now outdated being fiber is much purer and more flexible and durable now. But paid to run a 48 line trunk i believe into there comm room for 2 of those 48 wires to run the whole prisons everything It was hilarious to me especially all the problems it caused at first just switching to that kind of in out system and the usual bottlenecks it creates instead of the magical flow most all think it is easily switch over to. But i digress back to our COX and what we should be asking for and demanding updates about and possible release dates or beta trials as I am almost positively sure they have already done the simple upgrades to DOSIC 4.0 needed by them on their few components required, but maybe Like with everything else 5g cell and all those other wonders promised 4 years ago when it was feasible COX like all others are still tearing out all of their Huawii equipment from the network as I can only imagine how it must of been so immense and costly to replace especially if they had to go with cisco. And i am all for any product not made in Communist China or any communist country ide love USA but that is a dream just like the excuse from mister half shekel that Huawii and the other banned companies which if looked into has more to do with US citizens not being able to buy or invest in their companies not the stuff fed to us more lies and things that made is easier for them to do things quickly and quietly by saying things like they have Spying stuff in its setup or systems in them with no proof or evidence just accusations lies and money from other competitors and other countries illegally arresting others for a good show to make it real because there is no way it had nothing to do with their uncanny ability to release the same techs either as fast or faster for far cheaper with no real lose in quality really if you knew what you were doing. Either way when DOSIC 4.0 comes at least here in Phoenix its going to be what most have been really wanting and some actually needing 1 gig upload now gaming becomes something and even this emerging meta verse has potential of real growth all from the beautiful nice pure solid wire of copper. And DOSIC 4.0 is just the first and easiest and fastest upgrade they can still get even more out of that one wire than you can imagine and only need the one not 2 like fiber and all it will take it some upgrades to the network with new tech now the next update will be alot more and still not as destructive as google fiber or any of those destructive projects tried all over I mean like i said all the main fiber is already laid I saw it years ago but COX has it on lock and i think for good reason I really feel with the next update we will have the better internet system in the nation Of course competion would be nice and there is some finally but not enough i know.
- Bruce3 years agoHonored Contributor III
Did you say something?
- JillPill3 years agoNew Contributor
Ok. So I was trying to post on here earlier after husband bypassed splitters but there was too much happening at home. So here we go now. After he bypassed the splitter and did a direct barrel connect, speedtest was good but internet kept dropping. These are not lengthy drops but enough for the computer to notify me every couple of minutes. I copied the current modem logs after a little time went by and will attach to this post. In the meantime, the tech came out, tested at the box (just like the last tech) except this one said there was ingress and the problem is inside, then left. He said ingress is always inside. He was here maybe 5-10 mins. I mentioned the pixelation of tv as well and he said he hears that all the time and there's no telling what is causing that.
Should we just redo all of our indoor wiring?
Here are my modem logs while connected with NO splitter.
Connection
Top of Form
Startup Sequence
Startup Step
Status
Comment
Acquire Downstream Channel
381000000 Hz
Locked
Upstream Connection
OK
Operational
Boot State
OK
Operational
Configuration File
OK
Security
Enabled
BPI+
Connection Status
System Up Time
0 days 00h:52m:44s
Network Access
Allowed
Downstream Bonded Channels
Channel
Lock Status
Modulation
Channel ID
Freq. (MHz)
Pwr (dBmV)
SNR (dB)
Corrected
Uncorrected
1
Locked
QAM256
37
381.0
7.1
45.1
0
0
2
Locked
QAM256
1
681.0
3.7
42.5
0
0
3
Locked
QAM256
2
687.0
3.9
42.8
0
0
4
Locked
QAM256
3
693.0
3.9
42.8
0
0
5
Locked
QAM256
4
699.0
4.0
42.6
0
0
6
Locked
QAM256
5
705.0
4.2
42.9
0
0
7
Locked
QAM256
6
711.0
4.3
42.9
0
0
8
Locked
QAM256
7
717.0
4.4
42.9
0
0
9
Locked
QAM256
8
723.0
4.3
42.7
0
0
10
Locked
QAM256
9
729.0
4.5
42.7
0
0
11
Locked
QAM256
10
735.0
4.5
42.6
0
0
12
Locked
QAM256
11
741.0
4.5
42.7
0
0
13
Locked
QAM256
12
747.0
4.4
42.7
0
0
14
Locked
QAM256
13
753.0
4.7
42.8
0
0
15
Locked
QAM256
14
759.0
4.6
42.7
0
0
16
Locked
QAM256
15
765.0
4.4
42.6
0
0
17
Locked
QAM256
16
771.0
4.1
42.4
0
0
18
Locked
QAM256
33
357.0
7.0
44.9
0
0
19
Locked
QAM256
34
363.0
6.9
45.0
0
0
20
Locked
QAM256
35
369.0
7.2
45.2
0
0
21
Locked
QAM256
36
375.0
7.3
45.2
0
0
22
Locked
QAM256
38
387.0
7.0
45.2
1
0
23
Locked
QAM256
39
393.0
7.2
45.2
0
0
24
Locked
QAM256
40
399.0
7.1
45.2
0
0
25
Locked
QAM256
41
405.0
7.0
45.3
0
0
26
Locked
QAM256
42
411.0
7.0
45.2
0
0
27
Locked
QAM256
43
417.0
7.2
45.3
0
0
28
Locked
QAM256
44
423.0
7.1
45.2
0
0
29
Locked
QAM256
45
429.0
6.9
45.2
0
0
30
Locked
QAM256
46
435.0
6.9
45.0
0
0
31
Locked
QAM256
47
441.0
6.8
45.1
0
0
32
Locked
QAM256
48
447.0
6.7
45.0
0
0
33
Locked
OFDM PLC
159
300.0
7.5
43.3
27035069
0
Upstream Bonded Channels
Channel
Lock Status
Channel Type
Channel ID
Symb. Rate (Ksym/sec)
Freq. (MHz)
Pwr (dBmV)
1
Locked
SC-QAM
1
5120
36.8
38.5
2
Locked
SC-QAM
2
5120
30.4
38.0
3
Locked
SC-QAM
3
5120
24.0
38.0
4
Locked
SC-QAM
4
5120
17.6
37.3
5
Locked
SC-QAM
5
5120
60.0
39.5
6
Locked
SC-QAM
6
5120
67.0
40.0
7
Locked
SC-QAM
7
5120
74.0
40.0
8
Locked
SC-QAM
8
5120
81.0
40.5
Downstream Frequency Setting
Downstream Frequency Select
Bottom of Form
Event Log
Top of Form
Event Log
Time
Priority
Description
10:28:28
Tue Jan 4 2022Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;
14:34:44
Tue Jan 4 2022Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;
16:30:13
Tue Jan 4 2022Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;
16:34:39
Tue Jan 4 2022Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;
17:26:08
Tue Jan 4 2022Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;
17:33:27
Tue Jan 4 2022Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;
17:41:47
Tue Jan 4 2022Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;
19:13:26
Tue Jan 4 2022Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;
08:10:43
Wed Jan 5 2022Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;
07:48:31
Thu Jan 6 2022Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;
10:16:17
Thu Jan 6 2022Critical (3)
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;
Time Not Established
Critical (3)
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Time Not Established
Critical (3)
No Ranging Response received - T3 time-out;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;
Time Not Established
Notice (6)
Honoring MDD; IP provisioning mode = IPv4
10:24:15
Thu Jan 6 2022Warning (5)
DHCP WARNING - Non-critical field invalid in response ;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;
10:24:16
Thu Jan 6 2022Notice (6)
TLV-11 - unrecognized OID;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;
10:24:21
Thu Jan 6 2022Notice (6)
DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;
10:24:26
Thu Jan 6 2022Warning (5)
REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;
10:24:27
Thu Jan 6 2022Warning (5)
RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;
10:24:27
Thu Jan 6 2022Warning (5)
Dynamic Range Window violation
10:24:27
Thu Jan 6 2022Warning (5)
RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;
10:24:27
Thu Jan 6 2022Warning (5)
Dynamic Range Window violation
10:24:27
Thu Jan 6 2022Warning (5)
RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;
10:24:27
Thu Jan 6 2022Warning (5)
Dynamic Range Window violation
10:24:27
Thu Jan 6 2022Warning (5)
RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;
10:24:27
Thu Jan 6 2022Warning (5)
Dynamic Range Window violation
10:24:27
Thu Jan 6 2022Warning (5)
RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;
10:24:27
Thu Jan 6 2022Warning (5)
Dynamic Range Window violation
10:24:28
Thu Jan 6 2022Warning (5)
RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;
10:24:28
Thu Jan 6 2022Warning (5)
Dynamic Range Window violation
10:36:36
Thu Jan 6 2022Critical (3)
SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;
10:36:39
Thu Jan 6 2022Warning (5)
DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;
Bottom of Form
- JillPill3 years agoNew Contributor
And we were still connected without splitters when he tested.
Related Content
- 10 years ago
- 6 years ago
- 11 days ago
- 12 years ago
- 9 years ago