Forum Discussion
Reread your post and realized I missed some points the first time through.
Darkatt's post sounds spot on to me, as it doesn't sound like Cox, your modem, or Google router is the constraint.
If you still have the Google WiFi app, it will tell you exactly what speed it is seeing to each hub. You probably know the Google apps can be very helpful as they will tell you network speed, mesh speed, and speed to each connected device. The variation in device speeds is quite notable. In my home, more than 100 to 1 from fastest to slowest device. Sample shots of the process provided for reference as well as to give you a point of reference.
If you have an simple unmanaged switch, I would suggest plugging it into your primary Google, then bringing all of your hubs into the same room and connecting them to the switch to do a basic hub and spoke. Then, I bet you'll see each one is at least 400 - 500 mbps. If you don't have a switch, daisy chain them and check. I don't think it will be a lot slower, but it will be some.
If all that works, then you'll know that the modem and routers are all good. The constraints will be your mesh speed which will depend on hardwired vs wifi and the relative signal strength. If you are using just wifi, try to maintain something close to line-of-sight between pairs of routers. The network will optimize. I used to use wi-fi to go from the office, to a hub above the china cabinet so I could run ethernet into the back of my Verizon/Samsung mini-cell. My recollection was that would run 200-300. I've since pulled Cat6 and redeployed that unit.
A good wifi analyzer is your friend, helping ensure you get consistent coverage. I'll note that I prefer Speedtest to Fast, but prefer the Google app over either. My wife and I can both get can get 400 - 500 mbps on Fast on our newer Samsung phones when within 6 - 10 feet of a first gen Google router, so that should give you a point of reference.
Thanks again guys. Here's another update. After taking the actions below, I've come to the conclusion that I have probably dealing with more than one problem, but the one causing the most pain is, as you suspected, the physical layout of my network. I think I've been expecting WAY too much out of the mesh system. Although I only have a 1900 sq ft townhouse and try to cover it with five mesh pucks, the primary router is all the way at one end of the house. Nowhere near line of sight and certainly not within 10 feet of each other.
So this week I am changing my layout. I'm moving the Cox coax from the office to a location in the primary living quarters. There are 12' ceilings and a very open floorplan. The modem and primary router will reside on a ledge about 9' from the floor and have line of sight to two of the three TVs we use as well as three of the four wifi pucks. I've ordered a 100' run of Cat 6 ethernet cable to run back to the office for my desktop.
Now for the action I took:
* I connected my desktop directly to the modem via a new 24" Cat 5e cable and booted in safe mode. I ran the speed test and speeds jumped from 250 to nearly 500! Encouraged by that, I did a system refresh and reinstalled Windows 10. Probably a good thing to do, but it didn't yield any further improvement.
* I went through the house using the Google Home app to see which point devices were actually connecting as suggested. This was an issue. Many/most of my devices were connecting to points which were clearly not the nearest to them. Some of this may have been caused by me troubleshooting. I was taking points on and off line a lot and devices may have connected to a distant point when the closer points were off line... and then they just didn't change their connection when the entire network came back up. But that was only a part of the problem because I'm still seeing them make odd connections. I'll just keep an eye on it and see if the problem fixes itself when the new layout is in place and stable. At this point though, I have gone to each device and forced it to connect to the closest point.
* I brought all four points into the office with the main router and brought them on line. I felt this would ensure they were operating in a spoke and hub arrangement. Then, using first my phone and then my Chromebook, I forced connection to each puck in turn and ran speed tests (speedtest.net). My phone saw download speeds consistently in the 300 to 450 range... although my Chromebook reported somewhat slower speeds they were still near 200. My five mesh points are a mix of newer and older. I did not run this testing using ethernet backhaul connections. Firmware on each of the pucks is current. The primary router continued to report seeing ~850 mps from the modem.
So at this point I'm optimistic that I'll be able to reconfigure things into a much more functional solution. We'll see what kind of speeds I see once things are stable, but a couple of mysteries remain at this point.
* Why is my desktop only seeing 500 mps (at best) when connected directly to the modem using a short Cat 5e cable?
* Even when in the same room, my points only seemed to provide speeds of <450 mps. I will run a couple of tests using backhaul connections on the three pucks which accept it to see what happens but I haven't done that yet.
Thanks again and I will report back once everything is together.
Rick
- Darkatt2 years agoHonored Contributor
It's possible that based on the hardware, you may be topping our your desktop. This comes to mind especially since you stated the router see's 850 from the modem. The fact that it jumped from 250 to 500 DOES show that when running in safe mode, the software in the background slows the computer ½ of the speed that it sees in safe mode. let me know if I can provide any further info!
- Lovemylab2 years agoContributor III
Thanks for the update! I think you'll have a system that works well when you are done. As a reminder, my first gen units run about 500 mbps - 590 mbps point to point when hardwired. My understanding is the new Nest WiFi Pro is supposed to support wired backhaul and gigabit speeds, but I don't have any first hand experience. I think you'll find that you have plenty of capacity when you complete your planned changes. I will confirm that getting devices to connect as you want can be a challenge. My understanding, which could be wrong, is when you perform a network restart, most devices will connect to the first acceptable signal they get, which is often the primary since it comes up (effectively) first. If I see that on a device where I really want maximum speed, I wait until the network is fully up and then reboot my higher performance devices that aren't hardwired. Phones will hit 500 +, All of the better Google cameras/Nest consoles/Chromecast devices will do better than 250.
- RickO2 years agoNew Contributor II
Hi Guys, Well, sadly, all of the changes I outlined above have failed to make any difference at all. After rerouting the incoming Cox coax to a VERY centrally located location in my 1900 sq ft townhouse, I'm still getting horrible performance and speed test results as low as 20mps while sitting in clear view of mesh points only 15' away. I did a factory reset on my Arris modem this morning and then copied the event log below after it completed the restart. I Googled the results and several folks claim this is an indication that the signal coming in from the street is bad. Any further thoughts? I should mention that part of my recent troubleshooting efforts included replacing my Google mesh with my old D-Link DIR 880L and the performance got worse if anything.
Event LogThe table below contains the log of events that the SB8200 has detected. This log can be important to the service provider to help diagnose and correct problems, if any should occur.
Date Time Event ID Event Level Description 04/10/2023 07:42 67061601 6 "US profile assignment change. US Chan ID: 8; Previous Profile: 13; New Profile: 9 13.;CM-MAC=f8:79:0a:93:f6:b9;CMTS-MAC=00:29:c2:01:ee:3f;CM-QOS=1.1;CM-VER=3.1;" 04/10/2023 07:42 2436694061 5 "Dynamic Range Window violation" 04/10/2023 07:42 82001200 5 "RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=f8:79:0a:93:f6:b9;CMTS-MAC=00:29:c2:01:ee:3f;CM-QOS=1.1;CM-VER=3.1;" 04/10/2023 07:42 2436694061 5 "Dynamic Range Window violation" 04/10/2023 07:42 82001200 5 "RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=f8:79:0a:93:f6:b9;CMTS-MAC=00:29:c2:01:ee:3f;CM-QOS=1.1;CM-VER=3.1;" 04/10/2023 07:42 2436694061 5 "Dynamic Range Window violation" 04/10/2023 07:42 82001200 5 "RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=f8:79:0a:93:f6:b9;CMTS-MAC=00:29:c2:01:ee:3f;CM-QOS=1.1;CM-VER=3.1;" 04/10/2023 07:42 67061600 6 "DS profile assignment change. DS Chan ID: 33; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=f8:79:0a:93:f6:b9;CMTS-MAC=00:29:c2:01:ee:3f;CM-QOS=1.1;CM-VER=3.1;" 04/10/2023 07:42 67061600 6 "DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=f8:79:0a:93:f6:b9;CMTS-MAC=00:29:c2:01:ee:3f;CM-QOS=1.1;CM-VER=3.1;" 04/10/2023 07:41 73040100 6 "TLV-11 - unrecognized OID;CM-MAC=f8:79:0a:93:f6:b9;CMTS-MAC=00:29:c2:01:ee:3f;CM-QOS=1.1;CM-VER=3.1;" 04/10/2023 07:41 68000300 5 "DHCP WARNING - Non-critical field invalid in response ;CM-MAC=f8:79:0a:93:f6:b9;CMTS-MAC=00:29:c2:01:ee:3f;CM-QOS=1.1;CM-VER=3.1;" 01/01/1970 00:02 2436694066 6 "Honoring MDD; IP provisioning mode = IPv4" 01/01/1970 00:01 85000200 3 "UCD invalid or channel unusable;CM-MAC=f8:79:0a:93:f6:b9;CMTS-MAC=00:29:c2:01:ee:3f;CM-QOS=1.1;CM-VER=3.1;" 01/01/1970 00:01 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=f8:79:0a:93:f6:b9;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;" 01/01/1970 00:01 84020200 5 "Lost MDD Timeout;CM-MAC=f8:79:0a:93:f6:b9;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;" 01/01/1970 00:00 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=f8:79:0a:93:f6:b9;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
Related Content
- 26 days ago
- 3 months ago
- 2 months ago
- 9 years ago