Lenovo chromebook internet connectivity issue
- Mark as New
- Bookmark
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
14-10-2022 11:19 AM
Familiy members chromebook connects to Vodafone WiFi hub THG3000 but reports no internet connectivity. It is running lastest firmware and actually fails upgrade rather than saying no update available. After upgrading ChromeOS to latest via Wifi Hotspot from my smartphone still not working and still not wirking after hub reset.
Oddly internet connectivity dies work via WiFi from powerline extender connected to Same hub connected via cable at the master powerline extender. I can also browse internet when running as guest, can ping the router gw on 192.168.1.1 from chromsh. Connects fine to a talktalk Huwawei router/modem. Attached is chrome connectivity debug which suggests hub is nopt responding to 3 TCP packets correctly so ChromeOs deems it to provide no internet. Really needs Hub firmware expert or possible google chrome expert to investigate
Test Name: HTTP Captive Portal Test
Test ID: 5
Test verdict: Potential problem detected
CRITERIA
HTTP captive portal test returns a no problem verdict if all of the HTTP requests return a 204 HTTP status code
HTTP captive portal test returns a potential problem verdict if there are network stack problems more than the following percent of HTTP requests:
HTTP captive portal test returns a problem verdict if any of the HTTP requests do not return a 204 HTTP status code
DETAILS
Wed Oct 12 2022 11:21:21 GMT+0100 (British Summer Time) - Setting TCP timeout length (msec): 10000
Wed Oct 12 2022 11:21:21 GMT+0100 (British Summer Time) - Creating a TCP socket, number/host/port: 34 / tfhdeluc-ccd-testing-v4.metric.gstatic.com / 80
Wed Oct 12 2022 11:21:21 GMT+0100 (British Summer Time) - TCP connection established with host/port/status code: tfhdeluc-ccd-testing-v4.metric.gstatic.com / 80 / 0
Wed Oct 12 2022 11:21:21 GMT+0100 (British Summer Time) - TCP connection established successfully with host/port: tfhdeluc-ccd-testing-v4.metric.gstatic.com / 80
Wed Oct 12 2022 11:21:21 GMT+0100 (British Summer Time) - Preparing to send data with size (bytes): 231
Wed Oct 12 2022 11:21:21 GMT+0100 (British Summer Time) - Successfully sent data with size (bytes): 231
Wed Oct 12 2022 11:21:31 GMT+0100 (British Summer Time) - Error in request #/error status: 0 / -118
Wed Oct 12 2022 11:21:31 GMT+0100 (British Summer Time) - Error reading TCP data. Error code: -100
Wed Oct 12 2022 11:21:33 GMT+0100 (British Summer Time) - Setting TCP timeout length (msec): 10000
Wed Oct 12 2022 11:21:33 GMT+0100 (British Summer Time) - Creating a TCP socket, number/host/port: 35 / ztcsivqy-ccd-testing-v4.metric.gstatic.com / 80
Wed Oct 12 2022 11:21:33 GMT+0100 (British Summer Time) - TCP connection established with host/port/status code: ztcsivqy-ccd-testing-v4.metric.gstatic.com / 80 / 0
Wed Oct 12 2022 11:21:33 GMT+0100 (British Summer Time) - TCP connection established successfully with host/port: ztcsivqy-ccd-testing-v4.metric.gstatic.com / 80
Wed Oct 12 2022 11:21:33 GMT+0100 (British Summer Time) - Preparing to send data with size (bytes): 231
Wed Oct 12 2022 11:21:33 GMT+0100 (British Summer Time) - Successfully sent data with size (bytes): 231
Wed Oct 12 2022 11:21:43 GMT+0100 (British Summer Time) - Error in request #/error status: 1 / -118
Wed Oct 12 2022 11:21:43 GMT+0100 (British Summer Time) - Error reading TCP data. Error code: -100
Wed Oct 12 2022 11:21:45 GMT+0100 (British Summer Time) - Setting TCP timeout length (msec): 10000
Wed Oct 12 2022 11:21:45 GMT+0100 (British Summer Time) - Creating a TCP socket, number/host/port: 36 / rkqtzegi-ccd-testing-v4.metric.gstatic.com / 80
Wed Oct 12 2022 11:21:45 GMT+0100 (British Summer Time) - TCP connection established with host/port/status code: rkqtzegi-ccd-testing-v4.metric.gstatic.com / 80 / 0
Wed Oct 12 2022 11:21:45 GMT+0100 (British Summer Time) - TCP connection established successfully with host/port: rkqtzegi-ccd-testing-v4.metric.gstatic.com / 80
Wed Oct 12 2022 11:21:45 GMT+0100 (British Summer Time) - Preparing to send data with size (bytes): 231
Wed Oct 12 2022 11:21:45 GMT+0100 (British Summer Time) - Successfully sent data with size (bytes): 231
Wed Oct 12 2022 11:21:55 GMT+0100 (British Summer Time) - Error in request #/error status: 2 / -118
Wed Oct 12 2022 11:21:55 GMT+0100 (British Summer Time) - Error reading TCP data. Error code: -100
Sorry cannot attach log so had to paste the log.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
14-10-2022 06:31 PM
Sounds like this could be a WPA issue - Vodafone fudging the introduction of WPA 3 anyone?
If that's what it is then:
Temporarily turn off the extender.
In the Wifi Settings on the Chromebook, get it to forget the network.
Reconnect to the network.
When it's working turn the extender back on!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
14-10-2022 06:51 PM - edited 14-10-2022 06:53 PM
@katech I think the best (and easiest option is to use your own router.
@CrimsonLiar I'm thinking not wpa3. I'm thinking the lenovo only has 2.4Ghz wifi and is suffering the growing 2.4Ghz problem we're seeing more of.
I get the impression technicolor have made a change to the hardware and vf don't yet have a firmware for the changes - especially as there hasn't been a new firmware release since November.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
14-10-2022 07:10 PM
Thanks for comment family member is using the chromebook and has no problem with their talktalk Huwawei modem so not an urgent issue for me. The lenevo supports 5Ghz WiFi but did not check which it picked for sure. 5GHz was used in connection with S10 access point (hotspot) however. Still interested to see if their is a fix or indeed if vf issue one.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
15-10-2022 08:01 AM - edited 15-10-2022 08:06 AM
Band Steering won't work if you can't connect to the 2.4. The easy fix is to go into the router's ui (192.168.1.1 by default) and split the bands giving each band it's own ssid. Then just connect the lenovo to the 5Ghz band.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
23-10-2022 10:19 AM
Thanks I have now split 2.4G and 5G so I can more easily force connection band if needed and can use steering or boost as the vf calls it on 5G. Not convinced it will fix original problem as hub and chromebook were in same room but I will update when next I get hands on the chromebook.
Rgds
katech
