Frequent Visitor
•
10 Messages
"Dynamic Range Window violation"
Router - Google Nest Wifi
Cable Modem - Arris SB8200
Brought my house 7 years ago, and enjoyed perfect internet up until 10ish days ago. Since then I have been getting constant timeouts and random complete disconnections from comcast Service.
On multiple machines wired and wireless continous pings to google.com, comcast gateway, work-vpn and my google wifi gateway; once a timeout happens it would occur on everything at the exact sametime except the ping to my wifi gateway; I believe this tells me everything is good upto the cablemodem, far as interference goes.
Overnight my conitunious pings (with time stamps) come back perfect up until about 8:30am and then constant drops until 11pm, even on weekends. I had 3 different comcast technicions come to my house to check everything but nothing was ever resolved. According to the Techs everything was great, whilst I am still getting timeouts every 10-15 seconds across the board on multiple computers.
My Google Wifi is brand new, and I also purchased an Arris SB33 to validate if my cable modem wasnt the problem. Problem persits on any hardware configuration, even when plugging a laptop directly into the cable modem.. Confirmed it has nothing to do wiht my internal network.
The Xfinity Network Engineer has been checking my node for interference and he says everything is good, and he doesnt see any noise.. and there isnt anything else for him to do. There is no esculation path..
Googling my issue I stumbled onto people with the same Cablem Modems experiencing the same problem, and see the same events displaying in my cablemodems event log. They never show their resolution to the issue other than Comcast or Cox stepping in to resolve.
I have read a hard reset helps with the Dynamic Range Window Vilation, but even after hardreset it comes back.. After a hard reset on my cablemodem and these events came back.. Someone who is more familar with this, are my numbers looking ok? or is there anything else I can do to help my connection?
Please help, this is impacting my kids connections into school, my connection into work, and my gaming connections aftewards.. as mentioned my connection was perfect up unto 2 weeks ago, now an utter nightmare up unto 11pm at night.
Thanks
Accepted Solution
Mausama
Frequent Visitor
•
10 Messages
4 years ago
Closing the Loop on this.. that PAD power reducer seemed to smooth out my connection. Thanks for pointing me in the right direction.
0
0
EG
Expert
•
111.4K Messages
4 years ago
Can't see your pics. Since you are a new poster, they need to be approved by a Forum Admin. That could take some time. In the interim, you could try hosting them at one of those free third-party pic hosting sites like Imgur or Photobucket and post the link to them here.
Or copy all of the text of the status page and paste it into the body of your next post here.
0
0
Mausama
Frequent Visitor
•
10 Messages
4 years ago
Current System Time: Sat Jan 30 16:15:59 2021
0
0
Mausama
Frequent Visitor
•
10 Messages
4 years ago
More logs:
Date Time Event ID Event Level Description
0
0
EG
Expert
•
111.4K Messages
4 years ago
The downstream power is on the high side and it may be intermittently fluctuating even higher out of spec . That can cause random disconnects, spontaneous re-booting of the modem, speed, packet loss, latency problems, and the un-bonding of channels.
Is there an amplifier or a powered splitter on the coax line leading to the modem ? If so, try bypassing it and see.
0
0
Mausama
Frequent Visitor
•
10 Messages
4 years ago
I also have T3 Timeouts, and here are pings to www.comcast.net -t
Reply from 23.6.175.55: bytes=32 time=13ms TTL=57
Request timed out.
Reply from 23.6.175.55: bytes=32 time=16ms TTL=57
Reply from 23.6.175.55: bytes=32 time=182ms TTL=57
Reply from 23.6.175.55: bytes=32 time=12ms TTL=57
Reply from 23.6.175.55: bytes=32 time=50ms TTL=57
Reply from 23.6.175.55: bytes=32 time=26ms TTL=57
Reply from 23.6.175.55: bytes=32 time=12ms TTL=57
Reply from 23.6.175.55: bytes=32 time=21ms TTL=57
Reply from 23.6.175.55: bytes=32 time=31ms TTL=57
Reply from 23.6.175.55: bytes=32 time=15ms TTL=57
Reply from 23.6.175.55: bytes=32 time=14ms TTL=57
Reply from 23.6.175.55: bytes=32 time=14ms TTL=57
Request timed out.
Reply from 23.6.175.55: bytes=32 time=14ms TTL=57
Reply from 23.6.175.55: bytes=32 time=13ms TTL=57
Reply from 23.6.175.55: bytes=32 time=27ms TTL=57
Reply from 23.6.175.55: bytes=32 time=16ms TTL=57
Reply from 23.6.175.55: bytes=32 time=11ms TTL=57
Reply from 23.6.175.55: bytes=32 time=19ms TTL=57
Reply from 23.6.175.55: bytes=32 time=12ms TTL=57
Reply from 23.6.175.55: bytes=32 time=17ms TTL=57
Reply from 23.6.175.55: bytes=32 time=13ms TTL=57
Reply from 23.6.175.55: bytes=32 time=13ms TTL=57
Reply from 23.6.175.55: bytes=32 time=16ms TTL=57
Reply from 23.6.175.55: bytes=32 time=13ms TTL=57
Reply from 23.6.175.55: bytes=32 time=13ms TTL=57
Reply from 23.6.175.55: bytes=32 time=20ms TTL=57
Reply from 23.6.175.55: bytes=32 time=25ms TTL=57
Reply from 23.6.175.55: bytes=32 time=19ms TTL=57
Reply from 23.6.175.55: bytes=32 time=18ms TTL=57
Request timed out.
Request timed out.
Reply from 23.6.175.55: bytes=32 time=20ms TTL=57
Reply from 23.6.175.55: bytes=32 time=33ms TTL=57
Reply from 23.6.175.55: bytes=32 time=13ms TTL=57
Reply from 23.6.175.55: bytes=32 time=14ms TTL=57
Reply from 23.6.175.55: bytes=32 time=37ms TTL=57
Reply from 23.6.175.55: bytes=32 time=29ms TTL=57
Reply from 23.6.175.55: bytes=32 time=21ms TTL=57
Reply from 23.6.175.55: bytes=32 time=62ms TTL=57
Reply from 23.6.175.55: bytes=32 time=20ms TTL=57
Reply from 23.6.175.55: bytes=32 time=14ms TTL=57
Reply from 23.6.175.55: bytes=32 time=25ms TTL=57
Reply from 23.6.175.55: bytes=32 time=11ms TTL=57
Reply from 23.6.175.55: bytes=32 time=13ms TTL=57
Reply from 23.6.175.55: bytes=32 time=17ms TTL=57
Reply from 23.6.175.55: bytes=32 time=21ms TTL=57
Reply from 23.6.175.55: bytes=32 time=17ms TTL=57
Reply from 23.6.175.55: bytes=32 time=17ms TTL=57
Reply from 23.6.175.55: bytes=32 time=14ms TTL=57
Request timed out.
Reply from 23.6.175.55: bytes=32 time=26ms TTL=57
Reply from 23.6.175.55: bytes=32 time=16ms TTL=57
Reply from 23.6.175.55: bytes=32 time=29ms TTL=57
Reply from 23.6.175.55: bytes=32 time=17ms TTL=57
Reply from 23.6.175.55: bytes=32 time=55ms TTL=57
Reply from 23.6.175.55: bytes=32 time=55ms TTL=57
Reply from 23.6.175.55: bytes=32 time=24ms TTL=57
Reply from 23.6.175.55: bytes=32 time=36ms TTL=57
Reply from 23.6.175.55: bytes=32 time=14ms TTL=57
Reply from 23.6.175.55: bytes=32 time=23ms TTL=57
Reply from 23.6.175.55: bytes=32 time=29ms TTL=57
Reply from 23.6.175.55: bytes=32 time=57ms TTL=57
Reply from 23.6.175.55: bytes=32 time=54ms TTL=57
Reply from 23.6.175.55: bytes=32 time=13ms TTL=57
Reply from 23.6.175.55: bytes=32 time=30ms TTL=57
Request timed out.
Reply from 23.6.175.55: bytes=32 time=19ms TTL=57
Reply from 23.6.175.55: bytes=32 time=16ms TTL=57
Reply from 23.6.175.55: bytes=32 time=47ms TTL=57
Reply from 23.6.175.55: bytes=32 time=31ms TTL=57
Reply from 23.6.175.55: bytes=32 time=123ms TTL=57
Reply from 23.6.175.55: bytes=32 time=22ms TTL=57
Request timed out.
Request timed out.
Reply from 23.6.175.55: bytes=32 time=15ms TTL=57
Reply from 23.6.175.55: bytes=32 time=19ms TTL=57
Reply from 23.6.175.55: bytes=32 time=24ms TTL=57
0
0
Mausama
Frequent Visitor
•
10 Messages
4 years ago
There is no amps, but 1 splitter splitting to the cable TV.. I bypassed the splitter and the cable from outside is directly plugged into the cable modem. It looks like the downstream power increased... How can we adjust or dampen this power output?
0
0
Mausama
Frequent Visitor
•
10 Messages
4 years ago
Someone Mentioned using a Pad are those sold locally at any store?
0
0
EG
Expert
•
111.4K Messages
4 years ago
0
0