https://ibb.co/NVcv4Lyhttps://ibb.co/7XZF7ZXhttps://ibb.co/jrxktyMhttps://ibb.co/BCMx1kbhttps://ibb.co/MVkPf29https://ibb.co/x8bPc81https://ibb.co/XF1HBDy
Average packet loss around 4-9 percent , once an hour jumps to 90 percent loss for minute or two , then goes back to "normal" 5-9 % loss. Started 4-5 months ago. How can we fix it? Henderson NV 89074
here is my server pings for couple of minutes
--- 8.8.8.8 ping statistics ---
947 packets transmitted, 904 received, 4.54065% packet loss, time 1915ms
rtt min/avg/max/mdev = 11.962/17.887/38.131/4.950 ms
root@serv:~#
jonathan, something tells me that this guy already knows what he is doing, if he is pingplotting amazonaws compute cloud servers. Know what im saying? :)
The goto blanket responses offered by the moderators here actually have some merit. You'd be surprised how the amount of times I've seen experienced techs get their butt kicked by Layer 1 (myself included). I troubleshot a similar latency issue for a few days, swapping/bypassing infrastructure only to find a bad 90° F connector that I had kept dismissing because "passive devices don't go bad".
Goofy Layer 1 issues is why most techs immediately swap all the F connectors on every cable between the DMarc and the modem.
Also, most people with network experience don't necessarily have knowledge of headend/coax infrastructure and residential coax can be a nightmare due to the homeowner DIYer going to WalMart and buying the wrong coax cable for their house.
The best course of action is for "rustem" to run a brand new piece of RG6 from his DMarc (if possible) straight to his modem and hook directly to it with his PC/console, whatever and see what happens. Completely bypass the entire house infrastructure and network. If he still has issues connected directly to the DMarc, then he has enough ammo to attack Cox until they fix it.
Source: I'm an IT guy that also used to maintain/service TV headend/distribution.
