Forum Discussion
Can you show a tracert or use Pingplotter? That will show where the issue is happening. Also, use a server/IP you are having issue with as the target. Unless you are having issues with google DNS.
Also, anything under Troubleshooting > Logs > Event logs for around the time of the issue? My guess is it's T3 timeout errors, but the modem might not keep the logs. Maybe caused by the upstream being on the low side. Should be around 40-42dB and under 50dB. How does the coax get from the street/pole to the room the modem is? Any splitters/amp/filter? I wonder if a attenuator may help.
- rmgerrmann2 months agoNew Contributor II
I appreciate the reply. It's not just one service I have an issue with, it's a network wide problem that spikes. I'm having issues with every DNS. There is no specific time for the issue it just happens. Super annoying. I've started monitoring as of last night with Netprobe and it is just supper annoying. No constant 100% packet loss but enough to ruin things. Hope to hear from you again .
- WiderMouthOpen2 months agoEsteemed Contributor II
Is it just DNS traffic or all traffic? Hard to see the netprobe data because Cox doesn't allow you to click on a picture to zoom in anymore. Can you use Imgur? From what I can see though, packet loss is less then 1% and the tracert either doesn't show the issue or the issue wasn't happening when you ran the trace. Try using Pingplotter to monitor latency/packet loss over time. If you can't use Pingplotter for some reasons, winMTR is another choice, but not as good IMO.
Also, can you describe your network setup and config? Why do I see IMAP and POP traffic between 192.168.0.116 and 192.168.0.177? What is device is 177?
Last, to see if it's a router/gateway issue, try putting the gateway in bridge mode and see if there is a problem.
- rmgerrmann2 months agoNew Contributor II
Related Content
- 6 months ago
- 4 months ago
- 12 years ago
- 4 months ago