component:Services>Chromoting Connection Errors
Reported by
l...@doreydesigns.com,
Jan 18 2018
|
||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36 Steps to reproduce the problem: Can't host a session using Gsuite e-mail account, however personal e-mail account works. Error listed when sharing via code said to report to developers. Possibly related to Issue 722372 though it doesn't quite fit. What is the expected behavior? That I could host a remote desktop session, based on error reports it seems to be some kind of authentication conflict. What went wrong? I'm trying to use remote desktop to access my computer from a chrome book and having issues if I use my GSuite account, vs my personal gmail. If I change the chrome browser over to my regular user account and login it's magical and it works, but I'd really prefer if I could get it to work from the gsuite. I've gone through this to make sure I wasn't limiting it: https://support.google.com/chrome/a/answer/2799701?hl=en I've uninstalled / reinstalled the extension...the windows installer... rebooted... etc... Going through the debug consol I get the following errors when trying to connect to the session from the same computer (something that works fine on my personal). When I try to access a shared host. Message box: Unable to reach host. This is probably due to the configuration of the network you are using. Consol Errors: [0118/152335.540410:ERROR:jingle_session.cc(464)] session-initiate request timed out. Connection failed: ERROR_P2P_FAILURE client_session.js:671 If I try to share via remote assistance: I get a "Unexpexted Error Occured. Please Report this problem to the developers." Consol errors are: console_wrapper.js:115 [2018-01-18T15:38:24.709Z] register-support-host request timed out. ../../remoting/host/register_support_host_request.cc:162 console_wrapper.js:115 SIGNALING_TIMEOUT it2me_host_facade.js:299 Sharing error: ERROR_UNEXPECTED host_screen.js:279 Full cut and past of consol log files attached Did this work before? N/A Chrome version: 63.0.3239.132 Channel: stable OS Version: 10.0 Flash Version: Error message indicates report to developers otherwise I'd probably have stuck to the Chrome Help Forms since it feels more like an account problem, but some more info in the error messages would be nice so I could track down what exact is the problem...
,
Jan 19 2018
cc'ing dev for further triage
,
Jan 19 2018
Relabling this as ChromeOS issue as the description actually explains that the user is trying to use Chrome Remote Desktop from a Chromebook.
,
Jan 19 2018
Note error is in Windows host, intended client is Chromebook but no clients can conbect,including the same computer.
,
Jan 19 2018
Ah so the server is causing the problem not the client? Anyways I think the Chromoting team is the right one to respond so they should notice it based on the label and respond.
,
Jan 21 2018
Removing Enterprise label for now as this does not seem to be related to enterprise policies / mangement.
,
Jan 23 2018
Can you send us host logs as well? For Windows, this is a bit involved, but here are the instructions:
* Run cmd.exe elevated:
right-click on cmd.exe shortcut and choose "Run as administrator".
* Start the trace:
logman create trace -ets "chromoting" -p {2db51ca1-4fd8-4b88-b5a2-fb8606b66b02} 0xffffffff 5 -o %TEMP%\chromoting.etl
* Attempt to connect to the host.
* Stop the trace:
logman stop -ets "chromoting"
* Send us the file %TEMP%\chromoting.etl
,
Jan 24 2018
As requested, I started the log. Tried to share a key, tried to connect to host from host computer, stopped the log. Liam
,
Jan 30 2018
,
Aug 16
Sorry for not responding sooner, I just saw this bug. The ETL file attached only has two lines: VERBOSE 13488 6048 12:06:44-809 0 Sending heartbeat stanza to remoting@bot.talk.google.com VERBOSE 4328 5940 12:07:08-099 0 Reading policy from the registry is disabled. If this is still a problem, can you try to grab another ETL, but this time capture the host startup and connection repro? Steps: 1.) Open elevated cmd window on host 2.) In elevated window, run 'net stop chromoting' 3.) Start logging (per steps in comment #7) 4.) In elevated window, run 'net start chromoting' 5.) Wait for host to come online 6.) Attempt to connect to host 7.) Stop logging and attach ETL file |
||||||||||
►
Sign in to add a comment |
||||||||||
Comment 1 by krajshree@chromium.org
, Jan 18 2018Labels: Needs-Triage-M63