NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
COX Says My Cable Modem Is to Blame
CMD31T. It was working fine until August 1. Then it seemed to take forever to resolve domain names (spinning activity widgets while "waiting for xxxx.com..." displayed in status bars). Speed tests...
QUESTION: What should the power be on both upstream and downstream channels? And is downstream power coming off the cable, while upstream power is supplied by the modem?
your DS power is very good (ideally 0 dB)
you US power is good as well (lower 40s ideally but max to higher 40s)
yes, DS is recieved power level whereas upstream power is coming from modem.
your problem may not modem itself. Modem does not process DNS packets. It is just a passthrough bridge.
Unless you are having too many T3/T4 timeouts which are causing disconnection, it should be a Router or network issue.
Your response is what I expected - it seems COX is just doing whatever it takes to make me go away rather than deal with the problem. (I still think it is their DNS servers, especially since they connected me to servers in a city much farther than was the case prior to this problem.) It is ridiculous that it takes 30 secs to 1 minute of "Looking for <insert domain name here> followed by "Waiting for <insert domain name here>" for email and web pages, and then waiting even more for the page to fill out all those inserted ads that come from other domains. And the change from responsive to "world-wide wait" happened literally overnight when I changed nothing - no software updates, same router, same modem.
Anywat, thanks for confirming that it I don't need to spend more money on a new modem or rental from COX.
wmc
you might want to do wireshark capture and check what is happening. if your DNS is slow, change to public DNS servers on your laptop such as 4.2.2.2 or 8.8.8.8 and see what happens.
