Issue metadata
Sign in to add a comment
|
Chromebox won't return pings, but is alive and functioning on network
Reported by
jsm...@stillwaterschools.com,
Sep 26
|
||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36 Platform: 10895.56.0 (Official Build) stable-channel tidus Example URL: Steps to reproduce the problem: This MAY be a kiosk-mode-only problem. 1. Run a kiosk app on a chromebox. 2. Ping said Chromebox. See no returning pings. Request timed out. 3. Confirm Chromebox is indeed online, on the network, functioning normally. Scratch head. 3. Traceroute DOES work. Occasionally a solitary ping packet will get through, resetting my poor PRTG sensor, but it's generally not returning IMCP packets at all. What is the expected behavior? Ping should get a response. It USED to, reliably. What went wrong? Ping doesn't return a response. Did this work before? Yes 68 Chrome version: 69.0.3497.95 Channel: stable OS Version: 10.0 Flash Version: no clue without looking, don't care; Firmware version Google_Tidus.6301.109.17 This was working prior to 69, I know. This Chromebox is running the RiseVision app v2018.8.28.8208. They say nothing should have changed in their app that would break ping.
,
Oct 1
Solved: Chromebox had flipped to wifi when the LAN dropped momentarily. I suspect the routing got confused when it dropped back to the LAN connection. Disabling wifi entirely resolved the issue; it now successfully pings across the network.
,
Jan 15
|
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by morlovich@chromium.org
, Sep 26