Chromebit, managed and in kiosk mode, not able to connect to wireless

  • 1
  • Problem
  • Updated 2 years ago
We've been running a dozen and a half ASUS chromeboxes in kiosk mode, managed, mostly without issue for just over two years.  I decided to test using the ASUS Chromebit which seemed promising until it goes to boot into kiosk mode and wireless simply will not connect.  Anybody else run into a similar issue?  We're running Meraki APs and the SSID I'm connecting to is pretty plain jane WPA2-PSK with no splash page, etc. same as works for the few Chromeboxes we don't have hard wired.
Photo of Larry Askew

Larry Askew

  • 182 Points 100 badge 2x thumb

Posted 2 years ago

  • 1
Photo of Robb

Robb, Official Rep

  • 76,676 Points 50k badge 2x thumb
Sorry Larry, since we do all of our testing on Windows and Linux, I haven't seen this issue myself. Hopefully someone from the Community can chime in!
Photo of Andrew

Andrew

  • 294 Points 250 badge 2x thumb
I had a similar issue with my one Chromebit. After a call to Google Support I completely factory reset the Chromebit and it has been fine since.

Through our GAFE admin panel I created an Organizational Unit for my Chromebit, and all future Chromebits, with it's own dedicated WiFi network. The WiFi had a broadcast SSID, WPA/WPA2 security, restricted to Chromebooks, and Apply network "by device". 

My WiFi network was added through our Aruba Web Interface and is WPA2 Personal with a passphrase. I have MAC authentication disabled. IP assignment is through our network DHCP server.
Photo of Robb

Robb, Official Rep

  • 76,676 Points 50k badge 2x thumb
Thanks for that Andrew!

Larry, any chance you could follow what Andrew did and see if it solves your issue?