Wlecome @rodegg,

 

Hmmm, doing a quick google search, that seems to be a very common problem with Chromebooks -- regardless of the networking equipment used.  I don't actually have a Chromebook to test with. But all of my linux / android / kindle devices work fine (as does Windows, iOS, etc.).

 

Is this a new setup?

 

Things to try:

1) delete the SSID from the device and re-add

2) create a new, different SSID and try that

3) It sounds like you have band steering turned off -- which is good.  Separate SSID's per radio 2.4 & 5.8

4) Make sure to use 20MHz only on 2.4GHz

5) Make sure to use 2.4GHz channels 1, 6, or 11.

6) Check you WPA settings.  Maybe these devices don't support one of the WPA types the TP-Link equipment (configured in SDN/OC-200) is offering?

For example, they may not support WPA3.

 

I take it these Chromebooks don't have 5.8GHz support?

 

-Jonathan

@JSchnee21 Thanks for your input Jonathan. I've tried most of the things you suggested without luck. One of the APs was using channel 3 so I changed that but again it did not make a difference.

 

I did google this and also saw this is a common issue. Before setting up Omada, I had a tplink deco mesh system and they would not connect either. At this point I'm close to giving up.

I gave up. I moved the kids chromebooks so they get a usable 5ghz signal. Tplink 2.4ghz just does not work with chrome os.

@rodegg, @CoKro 

 

I am not running into this issue, but I am very interested.  Has anyone gotten a packet capture of this?

 

At first blush, I would guess that it is a legacy situation where the Chromebooks require some old 802.11b artifact to be enabled, and the new TP-Link stuff doesn't do it by default anymore.  That could at least explain why 5GHz would work and 2.4GHz wouldn't.  No 802.11b on 5GHz.

 

Just a thought.  I would love to see a PCAP.

@Questionmark  I don't know what a packet capture is. I'd be interested in learning.

 

I just turned on a chromebook that has not been turned on in months and had Chrome OS 79.0.3945. The chromebook successfully connected to a 2.4Ghz wifi. As soon as I updated Chrome OS to the current version, it was no longer able to connect.

 

 

Hi @CoKro,

 

Thank you for keeping us up to date.  Many people have had issues with Chromebooks and TP-Link (and other MFG) Wifi hardware.  

 

I'll be very interested to find out the root cause of the issue.

 

Thanks,

Jonathan

@JSchnee21 

 

Hi there, I have the same issue with an Archer C60. It works fine with most of devices, from older to newer but not with my brand new Samsung Chromebook. The laptop connects to the 5Ghz signal, but no way to establish a connection to the 2,4ghz signal. Tried many things and suggestions, without success.

 

However, the Chromebook connects fine to other 2,4 WiFi nets, such as the hotspot from my phone and to the netgear very old range extender I have.

 

The only way to make a 2,4 connection directly to the Tp Link router, was to activate the guest wifi net without any authentication. Only in that case it worked. Clearly, this is something I do not want to do, but maybe it is of help to know, just to understand better why this issue is happening and possibly to solve it.