New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 705695 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Mar 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

elm: Chrome Remote Desktop doesn't connect to shared host

Project Member Reported by djkurtz@chromium.org, Mar 27 2017

Issue description

Chrome Version: 
Chrome OS Version: Known bad: 9202.54.0 / 57.0.2987.115 & 9331.0.0 / 58.0.3027.0 
Chrome OS Platform: Elm

Steps To Reproduce:
(1) On host, open Chrome Remote Desktop Web App
(2) Under "Remote Assistance", click "Share"
(3) Note the provided Number.
(3) On Elm, open Chrome Remote Desktop Web App
(4) Under "Remote Assistance", click "Access"
(5) Enter the number from (3)
(6) On the Host, click "Share"

Feedback reports:
[1] https://feedback.corp.google.com/product/208/neutron?lView=rd&lReport=54561543646
Chrome remote desktop does not connect keeps saying connecting
9331.0.0 / 58.0.3027.0

[2] https://feedback.corp.google.com/#/Report/55927240665
my chrome remote desktop is not working. I can open it up and see my desktop but I cannot get it to do anything afgter that.Please help me to get this back up and running as it did when I first got my chromebooks
9202.54.0 / 57.0.2987.115

[3] https://feedback.corp.google.com/#/Report/52671165223
... update from 55 to 56 and since then I cannot get my acer chromebook r13 to be able to connect to the chrome remote desktop app.
8872.76.0 / 55.0.2883.105 [presumably feedback was sent after recovering to the working stable M-55 release]

Expected Result:

Host desktop is viewable and controllable from Elm.

Actual Result:

Elm shows: "Unable to reach the host.  This is probably due to the configuration of the network you are using."

Note, however, that the opposite direction *does* work (e.g., a linux host can view/control Elm's shared desktop), even when both devices are connected to the same network.

How frequently does this problem reproduce? (Always, sometimes, hard to
reproduce?)

Always, however, it is reported that this used to work on earlier versions.

What is the impact to the user, and is there a workaround? If so, what is
it?

Cannot use Chrome Remote Desktop to connect to a remote host.

Please provide any additional information below. Attach a screen shot or
log if possible.
 
Full CRD "Access" attempt failure Console log attached.

Corresponding error messages from file:///var/log/ui/ui.LATEST seem to be:

[0327/215150.031140:ERROR:pepper_packet_socket_factory.cc(243)] Failed to bind UDP socket to [fe80::76c6:3bff:fe6b:8df1]:0, error: -10
[0327/215150.076740:WARNING:stunport.cc(385)] Jingle:Port[0x3e5b6360::0:0:stun:Net[mlan0:fe80:0:0:x:x:x:x:x/0:Unknown]]: StunPort: stun host lookup received error 0
[0327/215150.077900:WARNING:stunport.cc(385)] Jingle:Port[0x3ee2f8b8::0:0:stun:Net[mlan0:fe80:0:0:x:x:x:x:x/0:Unknown]]: StunPort: stun host lookup received error 0
[0327/215150.079320:WARNING:stunport.cc(385)] Jingle:Port[0x3e5b0010::0:0:stun:Net[mlan0:2620:0:1000:x:x:x:x:x/0:Unknown]]: StunPort: stun host lookup received error 0
[0327/215150.079820:WARNING:stunport.cc(385)] Jingle:Port[0x3e5b04c0::0:0:stun:Net[mlan0:2620:0:1000:x:x:x:x:x/0:Unknown]]: StunPort: stun host lookup received error 0
[0327/215159.655440:ERROR:stunport.cc(89)] Binding request timed out from 192.168.254.x:54661 (mlan0)

console_wrapper.js:115 Connection failed: ERROR_P2P_FAILURE client_session.js:657

crd_elm_fail_log.txt
28.5 KB View Download
Status: Untriaged (was: Assigned)
I can repro on Hana 9000.82.0 / 56.0.2924.87.
Status: WontFix (was: Untriaged)
Oh, never mind the logs in #1 & #2.
I think there was a policy in place that was not allowing me to share from that host/user account combo.

I tried again sharing desktop using a test gmail accounts between hana (9000.82.0/56.0.2924.87) <-> elm (9334.18.0/58.0.3029.31), and it works in both directions.

Sign in to add a comment