11-15-2022 10:39 PM
Hello, i am having issues with my Google Wifi mesh. I am using the extender as a hub for ethernet to my computer. Whilst running a diagnostics test on Intels PROSet software i got these test results:
Cable Test Results [11/15/2022 10:24:05 PM] :
Cable Quality Status : Failed
Cable quality is poor or no cable is connected. Possible causes: Faulty cable, faulty connector, or a speed/duplex mismatch. Verify that the speed/duplex setting on the switch/hub is configured for auto-negotiation.
Cable Integrity Status : Failed
The test detected a bad connection. Distance to problem: 225 meters.
Any idea on how to fix any of these issues?
Thanks in advance.
11-16-2022 02:30 AM
Have you tried a different cable? Preferably cat5e due to cat6 and cat6a being stiffer and might cause a worse connection with Nest Wifi due to the tight cable routing.
Do you experience problems in day to day use, or is it just this test indicating problems?
11-17-2022 10:42 AM
I notice it specifically when downloading games, documents etc. When downloading you see huge spikes of lets say 20mb/s and then dropped down to less than 1mb/s
11-17-2022 01:59 PM
The cable is likely not the problem here. More likely QoS, double NAT, throttling or something along those lines.
11-17-2022 02:02 PM
Alrighty, can you elaborate on the meaning of that and and how i could possibly fix it? Firmware is up to date, including the extender itself & intel drivers on desktop.
11-17-2022 02:39 PM
About double NAT:
About QoS:
With game downloads with Steam for instance, it could also be the CPU bottlenecking you, as decompressing/ unpacking and integrity checking can be very CPU intensive.
Could be a lot of things, you'll just have to do some more digging, troubleshooting, searching and learning.
11-17-2022 02:48 PM
Thank you very much for the assistance. I will definitely do some more digging and research. Shouldn't be my CPU bottlenecking as i have an i712700k but **bleep** sure it will be bottlenecking when this 4080 arrives. Anyways thanks again.
11-28-2022 01:47 PM
Hey BillSmith241,
I just wanted to follow up real fast and see if you were able to figure out what was happening with your bottleneck and to see if you had any luck resolving things. If you're still needing some help, let us know.
Thanks,
Jeff
12-01-2022 01:59 PM
Hey BillSmith241,
I just wanted to follow up once more to see if you were still needing some help here. If so, just let us know.
Thanks,
Jeff
12-01-2022 06:26 PM
Hey thanks for reaching out again. This is the error i am receiving when running a 'Cable Test' in Intel PROSET Adapter Configuration Utility app. Here is the following error.
Cable Quality Status : Failed
Cable quality is poor or no cable is connected. Possible causes: Faulty cable, faulty connector, or a speed/duplex mismatch. Verify that the speed/duplex setting on the switch/hub is configured for auto-negotiation.
Cable Integrity Status : Failed
The test detected a bad connection. Distance to problem: 225 meters.
12-01-2022 06:27 PM
I know I'm simply repeating my above comment, but that is about as far as i have gotten. Not much i can do in regards to figuring it out. I haven't really taken any steps to fix it yet though such as purchasing a different cable.
12-05-2022 01:01 PM
Hey folks,
Thanks for lending a hand, @olavrb and @ Jeff.
@BillSmith241, have you already tried using a different cable to isolate the issue? Also, try connecting your Google Wifi point to your main Google Wifi router while your computer is connected to the LAN port of your Google Wifi point. Let us know if the issue persists. We’ll wait for your update.
Regards,
Abi
12-08-2022 01:45 PM
Hi there,
Chiming in to see if you still need assistance with this. Let us know if you have additional questions ― we'd love to help.
Best,
Mel
12-09-2022 01:54 PM
Hi everyone,
@BillSmith241just one quick final check in here since activity has slowed down. We'll be locking the thread in the next 24 hours, but if you still need help, I would be happy to keep it open. If there's more we can do, just let me know.
Thanks for lending a hand, olavrb, Jeff, Abi and Mel.
Regards,
Emerson
12-09-2022 05:20 PM
Thank you for the help so far. I will be doing some trouble shooting and will reach out in a new thread if needed.
Thanks!
12-11-2022 02:35 PM
Hey BillSmith241,
Awesome — looks like we can consider this one complete. I will lock the thread shortly unless I can help out with anything else.
Best,
Abi