![]() What we are looking for is -10 to +10 with SNR >34 on the downstream signal logs and <53 for upstream I prefer to see it between 35 and 45, though it will work up to 53 by the DOCSIS 3.0 extended standard which I will assume any large MSO has deployed by now since the DOCSIS 4.0 standard was released about 2 months ago. Go to IPconfig and note the gateway IP, try going to that IP in a web browser and that should get you to a login screen next you have to look up the login usually admin and password but not always. If its a gateway device (does routing, wireless, and modem in one device) it may be different depending on the company. If you own the modem or you are SURE its just a modem then its usually obtained by going to 192.168.100.1 which does not usually need a login and only works from your LAN. Some of this stuff you may need to look up at a cox faq but what I want to know is what are your signal levels at the modem, and what are the error logs. I do not work for Cox, but I work for another major cable company. If anyone has any advice on how to fix this issue on my own I would appreciate it very much, if not maybe just tell me how to get past the cannon fodder of s****y call center representatives that is Cox support. I ran a PingPlotter and would just like if someone can interpret the results and maybe confirm or deny if my assumptions are correct. I have tested multiple computers connected straight into my modem, used differnt modems, and even purchased a new router and the issue is still occuring. I have tried everything possible on my end and the issue seems to persist. ![]() The issue I am having is my ping will spike anywhere from 60-400ms every 5-10 seconds and makes using the internet troublesome and playing video games virtually impossible (I play competitive online games at a high rank so any ping spikes at all can ruin a match for me). I disagree as every test I have ran seems to point to the issue being out of our control and on their end but I digress. use the following name for the HK server, or for the ANZ server. So where the LAN subnet is 192.168.100.0/24, and the link between router A and LTE modem is 192.168.0.xx, PingPlotter shows the first hop as. If packet loss on a network node that is at 100 is showing this is not necessarily a. They can not solve the issue on their own and even tried charging me for the visit saying that it was our fault for the issue. But today, on a LAN that is behind router A, which in turn is downstream from an LTE modem/router B, PingPlotter skips the router A gateway address, and shows router B's gateway address as the first hop. I've called Cox about 12-13 times at this point and have had 3 tech visits with the boss coming out once himself. Hey guys, I've been having issues with my ping for about 6 months now (moved out for college so it wasn't an issue for 4 months).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |