Xfinity plant
Xfinity globe
Community Forum

High upstream levels on modem + DNS errors. How do I fix this?

Frequent Visitor

High upstream levels on modem + DNS errors. How do I fix this?

I have had this error for a very very long time. My internet keeps going down completely and windows keeps saying that it is a DNS error, specifically "

Windows can't communicate with the device or resource (primary DNS server)

It goes down constantly for anywhere to 2 minutes to 2 hours. It can happen anywhere for once every 4 days to every 30 minutes. My family has stated that it seems to only happen when I am home (I am usually living in dorms for college). Though I have formatted my home desktop and laptop (the only things that stay off / away when im gone) several times and this issue is still occuruing. When this error occurs, I can no longer connect to the modem IP to check diagnostics, but I CAN connect to the router. When the internet is back up, I can connect to the modem through an internet browser again.   

 

I checked my modem and this is what it is telling me 

 
 

 

Whenever it fixes itself or I reset it manually, the Upstream will go back down to about 48, then climb back up to 57. 

I have also tried many software fixes too such as the ipflush stuff, changing the DNS on the router to OpenDNS (which is another issue in itself, my EA6900 wont update the IPv4 DNS to OpenDNS), checking the Event Viewer (Which does show DCOM errors 10010 and 10016). 

 

If anyone has any idea what to do, I would really appreciate it. It has been doing this on and off for years and I have contacted support many times and it has never been fixed. I have even had techs come to the house and they replaced the signal booster but that didnt work at all. 


Accepted Solutions
Frequent Visitor

Re: High upstream levels on modem + DNS errors. How do I fix this?

UPDATE: My issue is still here, but the T3 and T4 timeouts seem to be fixed. Since the issue specifically asked was fixed, I guess this will be the answer. I will probably make a new thread asking for help with the other issue I am having. I posted what I think my other issue is at the bottom of the thread. 
I will still keep this post here for archival purposes


The problem seems to be fixed now. For everyone reading this thread in the future, ill keep it brief 
THE CAUSE: Water in the cable coming from the telephone pole
MY SOLUTION: Call a tech to replace the wire. 
IN GREATER DETAIL: 
A tech came to visit my house and was probably the best comcast tech ive had. His name was David and he was extremely professional and explained exactly what he was doing and why in great detail. Since I am going to school for computer info systems, I highly appreciated the opportunity to learn a little physical networking and his willingness to explain so I can understand. He spliced and replaced every end of every cable that was currently in use with brand new ends. After some testing and monitoring, he took a look at the line coming from the telephone pole to my drop. He showed me that animals have eaten through parts of the drop cable and the line from the pole. Once he cut the end off of the pole wire, he showed me water dripping like crazy out of the wire. He cut off the end of the drop cable that was bad and spliced a new end on it. He then replaced the entire wire coming from the pole with a new one and added some weather shielding device to the connection points. After he did this my upstream levels dropped from MIN 44.8, to a MAX of 39. Huge improvement. Especially since most of the time the average was about 54, and for the last few days it was stuck at 57.
It has only been a day, so I am not counting my chickens before they hatch, but me and the tech feel confident that the issue is solved now. 
I will be seeing if it cuts out again for another week or so, but if I dont reply to this thread again, we can assume that the issue was completely fixed. 
 


All Replies
Expert

Re: High upstream levels on modem + DNS errors. How do I fix this?

When Windows fails to connect, it gives the DNS error. It's not really a DNS error, but more of a general connection issue. Clearly, you have a signal/modem issue. It could be a bad splitter, bad coax, something on Comcast's plant or just a bad modem. You'll probably need another tech to figure it out. 

 

See the troubleshooting guide.

 

I've asked a Comcast employee to help you. You should expect a reply in this thread. 

Frequent Visitor

Re: High upstream levels on modem + DNS errors. How do I fix this?

Thanks for the reply. I have replaced some of the coax cables but not all of them. I did this last year. I will be checking again to see if the splitter should be replaced as well. If it still goes down again I will bite the bullet and call another tech. But the tech will be a last resort. 

 

I have read through the troubleshooting guide and found it very helpful. I will defintely be using it as a reference when I try to fix the wiring. 

 

I am still open to any other suggestions. I have tried so much and to no avail. I will take all advice and suggestions into consideration. 

Frequent Visitor

Re: High upstream levels on modem + DNS errors. How do I fix this?

Update, After checking the modem again a day or two later I am suddenly seeing that there are now level measurements for more channels in the upstream. 

Anyone know what this means? Channel 2 and 3 were 0 for a long time until now. 

Expert

Re: High upstream levels on modem + DNS errors. How do I fix this?

When the upstream power level is too high, the multiple channel bonding is lost.

Frequent Visitor

Re: High upstream levels on modem + DNS errors. How do I fix this?

Hello again, Sorry for the late update. Due to the infrequent nature of the issue, it took a while to see if the issues were truly fixed. They are not. 

 

I have a powered commscope splitter. It was the large 10 way home splitter. In an attempt to fix these issue, I bought a smaller 5 way splitter since we only use 2 cables and I couldnt find a smaller powered splitter. I am using a powered splitter because last time comcast was at the house, they claimed the issue was our run was too long, and a powered splitter will fix it. I plugged in the main line, the remote power into slot 1 for power and TV, and then the modem to slot 2, with all other slots terminated. It seemed to work for a few days but my internet went down again. I then decided to pick up a brand new NETGEAR CM600 to replace my old Linksys DPC3008, thinking that would solve the issue. That did not either as only a few hours later my internet went down again. The cable going to the modem is only a year old and goes straight to the modem with no other splitters. The TV never goes out though, even when the internet goes down. 

 

I do have some more information though. The new router has logs for me to post for someone to look at. 

 

2018-05-20, 15:57:07 Notice (6) Honoring MDD; IP provisioning mode = IPv6
2018-05-20, 15:56:57 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:7f:b9:6a:72:60;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2018-05-20, 15:54:49 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:6a:72:60;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2018-05-20, 15:54:47 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:7f:b9:6a:72:60;CMTS-MAC=00:01:5c:7d:72:48;CM-QOS=1.1;CM-VER=3.0;
2018-05-20, 15:54:47 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:6a:72:60;CMTS-MAC=00:01:5c:7d:72:48;CM-QOS=1.1;CM-VER=3.0;
2018-05-20, 15:50:52 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:7f:b9:6a:72:60;CMTS-MAC=00:01:5c:7d:72:48;CM-QOS=1.1;CM-VER=3.0;
2018-05-20, 15:50:52 Warning (5) MDD message timeout;CM-MAC=b0:7f:b9:6a:72:60;CMTS-MAC=00:01:5c:7d:72:48;CM-QOS=1.1;CM-VER=3.0;
2018-05-20, 15:32:30 Notice (6) Honoring MDD; IP provisioning mode = IPv6
2018-05-20, 15:32:05 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:6a:72:60;CMTS-MAC=00:01:5c:7d:72:48;CM-QOS=1.0;CM-VER=3.0;
2018-05-20, 15:30:35 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:6a:72:60;CMTS-MAC=00:01:5c:7d:72:48;CM-QOS=1.0;CM-VER=3.0;
2018-05-20, 15:30:10 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:6a:72:60;CMTS-MAC=00:01:5c:7d:72:48;CM-QOS=1.0;CM-VER=3.0;
2018-05-20, 15:20:27 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:6a:72:60;CMTS-MAC=00:01:5c:7d:72:48;CM-QOS=1.1;CM-VER=3.0;
2018-05-20, 15:13:42 Notice (6) Honoring MDD; IP provisioning mode = IPv6
2018-05-20, 15:13:32 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:6a:72:60;CMTS-MAC=00:01:5c:7d:72:48;CM-QOS=1.0;CM-VER=3.0;
2018-05-20, 15:12:59 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:6a:72:60;CMTS-MAC=00:01:5c:7d:72:48;CM-QOS=1.0;CM-VER=3.0;
2018-05-20, 15:12:33 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:6a:72:60;CMTS-MAC=00:01:5c:7d:72:48;CM-QOS=1.0;CM-VER=3.0;
2018-05-20, 15:10:05 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:6a:72:60;CMTS-MAC=00:01:5c:7d:72:48;CM-QOS=1.0;CM-VER=3.0;
2018-05-20, 15:09:38 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:6a:72:60;CMTS-MAC=00:01:5c:7d:72:48;CM-QOS=1.0;CM-VER=3.0;
2018-05-20, 15:06:43 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:6a:72:60;CMTS-MAC=00:01:5c:7d:72:48;CM-QOS=1.1;CM-VER=3.0;
2018-05-20, 14:41:22 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:6a:72:60;CMTS-MAC=00:01:5c:7d:72:48;CM-QOS=1.0;CM-VER=3.0;
2018-05-20, 14:40:50 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:6a:72:60;CMTS-MAC=00:01:5c:7d:72:48;CM-QOS=1.0;CM-VER=3.0;
2018-05-20, 14:40:25 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:7f:b9:6a:72:60;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2018-05-20, 14:40:17 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:6a:72:60;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2018-05-20, 14:39:46 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:6a:72:60;CMTS-MAC=00:01:5c:7d:72:48;CM-QOS=1.0;CM-VER=3.0;
2018-05-20, 14:37:49 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:6a:72:60;CMTS-MAC=00:01:5c:7d:72:48;CM-QOS=1.1;CM-VER=3.0;
2018-05-20, 13:42:03 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:6a:72:60;CMTS-MAC=00:01:5c:7d:72:48;CM-QOS=1.0;CM-VER=3.0;
2018-05-20, 13:39:58 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:6a:72:60;CMTS-MAC=00:01:5c:7d:72:48;CM-QOS=1.1;CM-VER=3.0;
2018-05-20, 13:19:09 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:6a:72:60;CMTS-MAC=00:01:5c:7d:72:48;CM-QOS=1.1;CM-VER=3.0;
2018-05-20, 13:19:09 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=b0:7f:b9:6a:72:60;CMTS-MAC=00:01:5c:7d:72:48;CM-QOS=1.1;CM-VER=3.0;
2018-05-20, 13:19:09 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=b0:7f:b9:6a:72:60;CMTS-MAC=00:01:5c:7d:72:48;CM-QOS=1.1;CM-VER=3.0;
2018-05-20, 13:12:50 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:6a:72:60;CMTS-MAC=00:01:5c:7d:72:48;CM-QOS=1.1;CM-VER=3.0;
2018-05-20, 13:12:50 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=b0:7f:b9:6a:72:60;CMTS-MAC=00:01:5c:7d:72:48;CM-QOS=1.1;CM-VER=3.0;
2018-05-20, 13:12:50 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=b0:7f:b9:6a:72:60;CMTS-MAC=00:01:5c:7d:72:48;CM-QOS=1.1;CM-VER=3.0;
2018-05-20, 13:11:57 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:6a:72:60;CMTS-MAC=00:01:5c:7d:72:48;CM-QOS=1.1;CM-VER=3.0;
2018-05-20, 13:11:57 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=b0:7f:b9:6a:72:60;CMTS-MAC=00:01:5c:7d:72:48;CM-QOS=1.1;CM-VER=3.0;
2018-05-20, 13:11:57 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=b0:7f:b9:6a:72:60;CMTS-MAC=00:01:5c:7d:72:48;CM-QOS=1.1;CM-VER=3.0;
2018-05-20, 12:34:12 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:6a:72:60;CMTS-MAC=00:01:5c:7d:72:48;CM-QOS=1.0;CM-VER=3.0;
2018-05-20, 12:32:43 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:6a:72:60;CMTS-MAC=00:01:5c:7d:72:48;CM-QOS=1.1;CM-VER=3.0;
Time Not Established Notice (6) Honoring MDD; IP provisioning mode = IPv6
Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:6a:72:60;CMTS-MAC=00:01:5c:7d:72:48;CM-QOS=1.0;CM-VER=3.0;

 

This is everything that has happened in only a few hours of it being installed on a new powered splitter. 

I note the T3 and T4 errors. 

Here is the new DS/US levels. 

 

Frequency start Value
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
 
Startup Procedure
Procedure Status Comment
Acquire Downstream Channel 603000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Security Enable BPI+
IP Provisioning Mode Honor MDD IPv6 only
 
<tabindex=-1>Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
1 Locked QAM256 23 603000000 Hz -4.3 dBmV 38.7 dB 0 0
2 Locked QAM256 1 465000000 Hz -4.6 dBmV 38.5 dB 0 0
3 Locked QAM256 2 471000000 Hz -1.2 dBmV 40.0 dB 0 0
4 Locked QAM256 6 495000000 Hz -3.5 dBmV 39.4 dB 0 0
5 Locked QAM256 8 507000000 Hz -2.6 dBmV 35.7 dB 0 0
6 Locked QAM256 9 513000000 Hz -2.6 dBmV 39.7 dB 0 0
7 Locked QAM256 10 519000000 Hz -1.2 dBmV 40.1 dB 0 0
8 Locked QAM256 11 525000000 Hz -4.6 dBmV 38.7 dB 0 0
9 Locked QAM256 12 531000000 Hz -1.0 dBmV 40.2 dB 0 0
10 Locked QAM256 13 537000000 Hz -3.8 dBmV 38.7 dB 0 0
11 Locked QAM256 14 543000000 Hz -4.9 dBmV 38.2 dB 0 0
12 Locked QAM256 15 555000000 Hz -5.7 dBmV 37.7 dB 0 0
13 Locked QAM256 16 561000000 Hz -3.3 dBmV 38.6 dB 0 0
14 Locked QAM256 20 585000000 Hz -2.6 dBmV 39.4 dB 0 0
15 Locked QAM256 22 597000000 Hz -0.6 dBmV 40.5 dB 0 0
16 Locked QAM256 24 609000000 Hz -2.4 dBmV 39.5 dB 0 0
17 Locked QAM256 26 615000000 Hz -2.2 dBmV 40.3 dB 0 0
18 Locked QAM256 27 621000000 Hz -3.8 dBmV 39.4 dB 0 0
19 Locked QAM256 28 627000000 Hz -0.8 dBmV 41.4 dB 0 0
20 Locked QAM256 29 633000000 Hz -3.8 dBmV 39.4 dB 0 0
21 Locked QAM256 30 639000000 Hz -1.8 dBmV 40.4 dB 0 0
22 Locked QAM256 31 645000000 Hz -1.8 dBmV 40.3 dB 0 0
23 Locked QAM256 32 651000000 Hz -4.1 dBmV 39.0 dB 0 0
24 Locked QAM256 33 657000000 Hz -1.0 dBmV 40.8 dB 0 0
 
<tabindex=-1>Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 17 5120 Ksym/sec 35600000 Hz 57.0 dBmV
2 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
3 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
4 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
5 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
6 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
7 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
8 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV

 

I also note that the starting frequency has changed since I checked when I installed the modem. 

I also note that my US levels have not changed at all. 

 

I am at a complete loss and I am about to give up entirely. I really hope someone can help soon. I have replaced all parts that personally belong to me. I am confident it is no longer on my end, but I am still not sure. 

 
Expert

Re: High upstream levels on modem + DNS errors. How do I fix this?

@malarky345

Sorry you didn't get an employee response! I've escalated by another method. Hang in there. 

Official Employee

Re: High upstream levels on modem + DNS errors. How do I fix this?

Hi malarky345, 

 

Sorry for the delayed reply. I'd like to help to help look further into the issues you're having with your internet. In order assist you, please send me a private message verifying your first and last name, street address including city state and zip code, and the full account number or phone number associated with your services. 

 

To send a private message click on my name "ComcastChe", then click private message me. 

Frequent Visitor

Re: High upstream levels on modem + DNS errors. How do I fix this?

UPDATE: My issue is still here, but the T3 and T4 timeouts seem to be fixed. Since the issue specifically asked was fixed, I guess this will be the answer. I will probably make a new thread asking for help with the other issue I am having. I posted what I think my other issue is at the bottom of the thread. 
I will still keep this post here for archival purposes


The problem seems to be fixed now. For everyone reading this thread in the future, ill keep it brief&nbsp;
THE CAUSE: Water in the cable coming from the telephone pole
MY SOLUTION: Call a tech to replace the wire.&nbsp;
IN GREATER DETAIL:&nbsp;
A tech came to visit my house and was probably the best comcast tech ive had. His name was David and he was extremely professional and explained exactly what he was doing and why in great detail. Since I am going to school for computer info systems, I highly appreciated the opportunity to learn a little physical networking and his willingness to explain so I can understand. He spliced and replaced every end of every cable that was currently in use with brand new ends. After some testing and monitoring, he took a look at the line coming from the telephone pole to my drop. He showed me that animals have eaten through parts of the drop cable and the line from the pole. Once he cut the end off of the pole wire, he showed me water dripping like crazy out of the wire. He cut off the end of the drop cable that was bad and spliced a new end on it. He then replaced the entire wire coming from the pole with a new one and added some weather shielding device to the connection points. After he did this my upstream levels dropped from MIN 44.8, to a MAX of 39. Huge improvement. Especially since most of the time the average was about 54, and for the last few days it was stuck at 57.
It has only been a day, so I am not counting my chickens before they hatch, but me and the tech feel confident that the issue is solved now.&nbsp;
I will be seeing if it cuts out again for another week or so, but if I dont reply to this thread again, we can assume that the issue was completely fixed.&nbsp;
&nbsp;

Official Employee

Re: High upstream levels on modem + DNS errors. How do I fix this?

Hey malarky345!

 

Thanks for the update. I did receive your private message but figured I'd follow up here. I'm happy you had a good experience with the tech that came out for repairs. It's nice to know that he took his time, and was willing to educate you on the changes that were being made on your end so you could see how certain things could affect your services and why it is so important that we send techs to check on things like this. We appreciate the feedback and follow up. Hopefully, your experience will help others and encourage them to reach out if they are experiencing these types of issues as well. 

 

To make sure things are completely resolved, I'm going to reach out to you next week to check on the status of your services. Please feel free to reach out to me if you do begin to notice any more problems. I'd be happy to help.

 

I'll follow up with you next week, 5/29 after 2:30 PM MST when I get into the office. Chat with you soon! 

Frequent Visitor

Re: High upstream levels on modem + DNS errors. How do I fix this?

UPDATE: The internet has gone out again. However it was only for about 30 seconds. It has been raining here for a few days, so I am wondering if it is due to the weather.  I will be PMing ComcastChe to see if I can get more info. Will keep monitoring and will update thread with a reply if I figure anything out.

Frequent Visitor

Re: High upstream levels on modem + DNS errors. How do I fix this?

Another update. The issue is just flat out not resolved
The internet has been going out here and there ever since the visit. But for short periods of time. About 30 seconds, but still up to 5 times a day. I thought this was due to weather but that does not seem to be the case as it is now almost a week later and the issues are still here. Today was the last straw before I decided it was not fixed. The internet had been down for almost 30 minutes. The same length as before. I had sent a message to ComcastChe when the issue first popped up again, but have not received a reply in days. I hate that the tech was so good, but the problem is still not fixed. However I do not entirely blame the tech. He did say we may need a new drop, but he also said he was very confident his fix would do the trick. I declined the new drop as we have already had several drops put in over the years, but I did say that I would do it if its the last resort.  I am awaiting ComcastChe's PM so I can see what they think and decide what to do next.

Do not get me wrong, I am EXTREMELY appreciative of the support that the tech and ComcastChe have given me so far, but at this point I am now becoming impatient with this issue.

Official Employee

Re: High upstream levels on modem + DNS errors. How do I fix this?

HI @malarky345

 

Thanks for the update. I've been off since Wednesday so I was not able to reply. However, since your issues are still present, I am going to look further into this and will be replying to your private message with my findings and suggestions for the next step shortly. 

Frequent Visitor

Re: High upstream levels on modem + DNS errors. How do I fix this?

Thank you for getting back to me. I apologize if I seem rude, but I am truly at wits end. The issue is so sporadic that I can never pinpoint what the issue is or what should be done about it. I will PM you and update the thread with the latest updates. 

 

Thank you for your continued support

Official Employee

Re: High upstream levels on modem + DNS errors. How do I fix this?

No need to apologize! I understand your frustration. I'm going to keep our private message open a bit longer so I can continue to work with you after your updates.  

Frequent Visitor

Re: High upstream levels on modem + DNS errors. How do I fix this?

Another update. 

 

I have come to an interesting find after experimenting with the internet for a few days. It did not go down for a few days, but as soon as I opened my laptop to use it, not even 5 minutes later it was down again. It went down another 2 times after that. However, I decided to try to leave my laptop off for another few days. Ever since then, my internet has yet to go down again. Do you guys think this has anything to do with my issue? My laptop has been completely formated just a month ago and I dont have any new software on it (I use the laptop for school and I have not used it since the semester ended). 

 

I am not sure what issue this is causing but, I do not think I am having any T3 T4 errors, so I guess the main reason this thread exists is solved. Though I am still having issues, the T3 and T4 seem to be gone. 

 

For anyone reading the thread looking to fix these specific errors, the answer is get in contact with an employee and set up a tech visit. Mine was free because the Timeouts where cause by an issue with the main line on the telephone pole, not my personal devices. 

Official Employee

Re: High upstream levels on modem + DNS errors. How do I fix this?

Hi @malarky345

 

I've just replied to your private message. It sounds like the laptop could be an issue. Please reply at your convenience and we can proceed from there. 

Frequent Visitor

Re: High upstream levels on modem + DNS errors. How do I fix this?

ask them to verify their is no signal ingress or water ingress on other connections between you and the local street box (where the overheads terminate).

 

in our area we had 4 years of odd tv issues - turned out to be interference from marine radios - the signal was able to ingress onto the wired due to cracked outer shielding and connections.  I believe they add to replace quite a lot of our local cable on the overheads to fix it....