This is an old repetitive story but it's happening again now at new place after 6 months of almost flawless internet connection and speed. The problem now is I've lost/forgotten the nuanced Windows command-line steps (ping? tracert?) I used to troubleshoot or prove to myself or Comcast Xfinity what the culprit is. In the past it's sometimes been weird random radio interference but usually it's come down to modem T3 timeout issues caused by something before reaching my modem or anything directly connected to it, like with some pre-existing wall wire or connector or outside box. Right now of course Comcast Xfinity is saying they're seeing no problem and they just run me through the typical troubleshooting steps and things generally work at the time then get intermittent again randomly. When it's happening though typically the disconnects are frequent. Speed tests usually look OK, but sometimes up/down looks too low.
When I checked my modem logs in past weeks (it's been going on for maybe a month, I saw nothing significant. Now I see a full page of T3 timeouts about every few days... which matches the past experiences at my last place. I don't remember what to look at for power levels or error corrections etc... that's maybe a Comcast tech question. My modem is non-leased and maybe 5 years old but I haven't found anything to say it's failing.
Before fighting with a higher-level tech, I'd like to gather proof of where the problem is actually happening. While I vaguely remember to try ping and tracert, and I think I ran 4 command-line windows of them concurrently per Windows computer (wireless and wired) to track what was failing (connection to modem/router or internet), I don't remember exactly what I did, but I did gather enough last time to show the tech that the problem was not the modem/router. There were some failures with the WiFi pings/whatever, but it was miniscule compared to the internet failures (beyond my modem).
So far I've tried some things based on online search: ipconfig (to get my Default Gateway), pinging DNS servers - 1.1.1.1 (CloudFlare) and 8.8.8.8 (Google though I've read this isn't reliable anymore) - with and without the `-t` option (got random timeouts there), tracert on various websites (google.com, microsoft.com, yahoo.com, etc), and while I'm seeing timeouts and other odd behavior, I'm just not sure what I'm looking at yet nor how to prove to myself or a Comcast tech where the problem is.
Anyway, do you know what I'm talking about? Do you know the particular commands I should be running concurrently to gather up timeouts/errors/etc to show where the majority of the problem is happening? I thought I posted here but I'm not finding it now, so it must have been deleted or on an old account.
When I checked my modem logs in past weeks (it's been going on for maybe a month, I saw nothing significant. Now I see a full page of T3 timeouts about every few days... which matches the past experiences at my last place. I don't remember what to look at for power levels or error corrections etc... that's maybe a Comcast tech question. My modem is non-leased and maybe 5 years old but I haven't found anything to say it's failing.
Before fighting with a higher-level tech, I'd like to gather proof of where the problem is actually happening. While I vaguely remember to try ping and tracert, and I think I ran 4 command-line windows of them concurrently per Windows computer (wireless and wired) to track what was failing (connection to modem/router or internet), I don't remember exactly what I did, but I did gather enough last time to show the tech that the problem was not the modem/router. There were some failures with the WiFi pings/whatever, but it was miniscule compared to the internet failures (beyond my modem).
So far I've tried some things based on online search: ipconfig (to get my Default Gateway), pinging DNS servers - 1.1.1.1 (CloudFlare) and 8.8.8.8 (Google though I've read this isn't reliable anymore) - with and without the `-t` option (got random timeouts there), tracert on various websites (google.com, microsoft.com, yahoo.com, etc), and while I'm seeing timeouts and other odd behavior, I'm just not sure what I'm looking at yet nor how to prove to myself or a Comcast tech where the problem is.
Anyway, do you know what I'm talking about? Do you know the particular commands I should be running concurrently to gather up timeouts/errors/etc to show where the majority of the problem is happening? I thought I posted here but I'm not finding it now, so it must have been deleted or on an old account.