Forum Discussion
A router is an equal-opportunity sharer. Since you can't isolate the modem, you want everything disconnected from a router except the testing device. If your phone is measuring 437 Mbps on WiFi, I think you may be getting good bandwidth to your house. One problem may be with your desktop.
- Is the wireless NIC on the desktop, if applicable, disabled during tests?
- Have you tried a different port on the router?
- Sometimes disabling and re-enabling the NIC helps.
- While you're in the NIC, any updates available for its drivers?
I kinda unsure if you have a second problem. "My Gigablast service was working at an acceptable service level until the beginning of December 2021. Since then, the Netspeed test...is showing 899.1 mbs."
What's wrong with 899 Mbps? What were you previously showing?
I'll look into your bulleted items but to answer your last question, the 899 value came only between my Cox online account speed test utility and the Cox test server, both devices on the same net. My desktop SpeedTest to a Cox server in Phoenix right now produces 147, and I'm located near Tucson. I would love to have 899 again from my desktop.
- Bruce3 years agoHonored Contributor III
So before December 2021, your desktop was measuring 899 Mbps via your Cox account?
Do you recall what you were measuring at your desktop via Fast and Speedtest also before December 2021...or had you only used your Cox account to test?
If you're measuring 437 Mbps on another device, it just seems your desktop is now getting a smaller slice of your bandwidth. Perhaps something had changed in its network settings, although it'd be weird for a wired connection.
I don't know your OS but you could check if Window Auto-Tuning is enabled.
- OtherBill3 years agoNew Contributor II
Before December I was typically running at 910 anywhere I went to measure it from my desktop or browser or Cox online account. Now, only the online account sees gagabit speeds. I'll check the Windows Auto-Tuning.
- OtherBill3 years agoNew Contributor II
My problems started in December when a Microsoft Flight Simulator download (4 Gig) failed. In one of the MS FS forums, there was a suggestion of disabling something Windows was doing that negatively impacted large downloads. I issued that CLI command in hopes of fixing the failing MS download. It didn't fix the problem and, apparently, disabled Auto-tuning. After a month of continued download failures, I discovered that the first failure left remnants of files that caused subsequent downloads to fail. After some careful file cleanup the download succeeded, but my speeds had been diminished considerably.
I re-enabled Auto-Tuning and thanks to Bruce, Mouth, and Ben for your time and knowledge for I am now running full speed on the desktop & browser.
Related Content
- 6 years ago
- 8 years ago
- 2 years ago
- 4 years ago