"network communication" enrollment error |
|||||||
Issue descriptionChrome Version: ToT What steps will reproduce the problem? (1) Go through Chromad enrollment flow (2) When AD credential are requested, enter a username with a typo in the domain part What is the expected result? The error message should mention the possibility of a misspelling of the domain. What happens instead? The error message blames it on the network: "A network communication problem occurred ..."
,
Jun 19 2017
,
Jun 19 2017
Problem is, prior to join we need to figure out the workgroup. net ads workgroup spits out the exact same error message in case 1) there's no network and 2) the realm is misspelled. Thus, authpolicyd can't decide what the problem is. I'd suggest Chrome adjusts its error message based on whether it has connectivity at the moment of join, e.g. 1) Could not contact server. Please check your network connection. 2) Could not contact server. Please check user name and domain.
,
Jun 19 2017
I don't think we can reliably distinguish between network problems (trouble might not stem from the first hop) and misspelled domain name. Therefore I'd suggest something along the lines of "Could not contact server. Please check your network connection and the spelling of the domain." (Misspelling of the user name should be a different error code, right?)
,
Sep 22 2017
Fixed here: https://chromium-review.googlesource.com/c/chromium/src/+/567007
,
Jan 22 2018
,
Jan 23 2018
,
Feb 22 2018
Verified, in case of a typo in the domain part, there is an error message: "Oops! There was a problem contacting the logon server. Please check your network connection and the domain name, then try again." (see attached screenshot). Chrome OS: 10323.39.0 Chrome: 65.0.3325.89 Device: Kip |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by igorcov@chromium.org
, Jun 19 2017