Several of us have run the new'ish ChromeOS Diagnostics app 'Connectivity' tests and have arrived at the same results, reporting: 'Can't contact gateway', see the image below -
We've tried it using ChromeOS on Google (Pixelbook, Pixel Slate) and non-Google (Acer, ASUS, etc.) devices and even on a ChromeOS Flex device and are getting the same error.
Many of us are using a Google Nest mesh router and points so it seems to indicate that it could be a Mesh router issue but we're not at all sure. Signing-in with the Guest account instead of a Gmail account does not help.
It's been reported that the test doesn't run at all on an AUE Acer R11 Chromebook.
Some Chromebook help forum users have run into this also, see below:
I don't know how the tests are done and if there are other things we can look at like logs, etc. to figure out what's going on. When saving and looking at the 'session_log.txt' it shows the following:
9/7/22, 9:27:05 AM - GatewayCanBePinged - Started
9/7/22, 9:27:09 AM - GatewayCanBePinged - Failed
9/7/22, 9:45:07 AM - GatewayCanBePinged - Started
9/7/22, 9:45:11 AM - GatewayCanBePinged - Failed
Some can ping the gateway from a crosh session or a shell session and some cannot so we're getting mixed results with that and can't be sure if it's a bug with the Diagnostics app or not.
We've also tried Google name servers but there's been no difference.
If anyone knows more about this or has any ideas please chime in.
Thanx,
~DennyL
P.S. If this needs to be instead reported as a crbug or on the IssueTracker I can do that too.