This is a previous report on CBC - this one involved a Mac
https://productforums.google.com/forum/?utm_medium=email&utm_source=ba_notification#!topic/chromebook-central/NVZ5hZtAAlI

A third event involved two Windows 7 Pro computers. I tested personally with a Chromebook - I could connect to the problem laptop and a second Windows desktop PC that I regularly connect to, but the laptop could not connect to that desktop PC.

#CBC-RS/TC-watchlist

Hi,

  Not finding a way to edit this ticket, but i would think it should go in Service/chromoting instead of what i selected.

**Adding information. In my windows event viewer, I see an event telling me my user has been rejected. What i find strange is the version reported. I have 51.0.2704.7 and it's reporting 50.0.2261.22.

Also tested on Ubuntu with Chrome and with 51.0.2704.7 installed on both machines, I get rejected both ways. Win 10 to Ubuntu rejected and Ubuntu to Win 10 rejected.

Thanks

Deleted: chrome RD error.jpg 54.7 KB

	chrome RD error.jpg 54.7 KB View Download

An additional report on CBC
https://productforums.google.com/forum/#!topic/chromebook-central/sJXO8wXd154;context-place=forum/chromebook-central

Can you send us the logs from the client? To find them, follow these instructions:

* With the app running, visit chrome://extensions
* Ensure that the "Developer Mode" checkbox at the top right of the page is checked.
* Scroll down to the Chrome Remote Desktop extension.
* Click the main.html link.
* Select the Console tab.

Try to connect and then copy/paste the logs here.

I have supplied these instructions (plus a bit more detailed steps) in the applicable CBC threads.

Thanks.

This is the log I have.

Emails have been modified.

Chrome Remote Desktop version: 51.0.2704.7 (v2)
ui_mode.js:122 App mode: home
host_controller.js:20 Host version: 50.0.2661.22
ui_mode.js:122 App mode: home.client.unconnected
ui_mode.js:122 App mode: home.client.connecting
dns_blackhole_checker.js:155 DNS blackhole check succeeded.
fallback_signal_strategy.js:339 FallbackSignalStrategy progress: xmpp succeeded
main.html:1 [0502/200230:INFO:chromoting_instance.cc(609)] Connecting to yyzru....@gmail.com/chromotingFAC19FD7. Local jid: pdum...@asturiat...
client_session.js:402 [2016-05-02T20:02:30.731Z]Sending Iq: <iq xmlns="jabber:client" to="yyzru....@gmail.com/chromotingFAC19FD7" type="set" id="7790695290830172812"><jingle xmlns="urn:xmpp:jingle:1" sid="2785961112600664364" action="session-initiate" initiator="pdum...@asturiatechnologies.com/chromotingC1421A5D"><content name="chromoting" creator="initiator"><description xmlns="google:remoting"><standard-ice/><control transport="mux-stream" version="3"/><event transport="mux-stream" version="2"/><video transport="stream" version="2" codec="vp9"/><video transport="stream" version="2" codec="vp8"/><audio transport="mux-stream" version="2" codec="opus"/><audio transport="none"/><authentication supported-methods="third_party_spake2_curve25519,third_party,pair_spake2_curve25519,spake2_pair,spake2_curve25519,spake2_hmac"/></description></content></jingle></iq>
client_session.js:402 [2016-05-02T20:02:30.754Z]iq send id=4054244492014180847 get google:jingleinfo
client_session.js:620 Connecting as pdum...@asturiatechnologies.com
client_session.js:435 [2016-05-02T20:02:30.927Z]iq receive id=4054244492014180847 result google:jingleinfo
  stun 'stun.l.google.com' udp:19302; 'alt3.stun.l.google.com' udp:19302; 'alt4.stun.l.google.com' udp:19302; 'alt1.stun.l.google.com' udp:19302; 'alt2.stun.l.google.com' udp:19302; 
  relay 'relay.google.com' udp:19305 tcp:19305 tcpssl:443;  token: CAESKAofcGR1bW9udEBhc3R1cmlhdGVjaG5vbG9naWVzLmNvbRCMksymxyoaEMNgBEwZE+qxyP4kHVn1Lbw=
client_session.js:435 [2016-05-02T20:02:31.298Z]iq receive id=7790695290830172812 result (empty)
client_session.js:435 [2016-05-02T20:02:31.328Z]Receiving Iq: <iq xmlns="jabber:client" to="pdum...@asturiatechnologies.com/chromotingC1421A5D" type="set" id="11892716647469880401" from="yyzru....@gmail.com/chromotingFAC19FD7"><jingle xmlns="urn:xmpp:jingle:1" sid="2785961112600664364" action="session-terminate"><reason><incompatible-parameters/></reason></jingle></iq>
client_session.js:402 [2016-05-02T20:02:31.340Z]iq send id=11892716647469880401 result (empty)
console_wrapper.js:115 Connection failed: ERROR_INCOMPATIBLE_PROTOCOL client_session.js:640remoting.ConsoleWrapper.recordAndLog_ @ console_wrapper.js:115remoting.ClientSession.notifyStateChanges_ @ client_session.js:640remoting.ClientSession.setState_ @ client_session.js:558remoting.ClientSession.onConnectionStatusUpdate @ client_session.js:484remoting.ClientPluginImpl.handleMessageMethod_ @ client_plugin_impl.js:233remoting.ClientPluginImpl.handleMessage_ @ client_plugin_impl.js:166
ui_mode.js:122 App mode: home.client.connect-failed.it2me

Let me know if you need something else

Thank You
Pierre

Forgot to tell you I'm connecting to a Remote Desktop on Ubuntu. Like stated in this thread comment #2, the latest test I did was with the same versions and machines.

What version is the host you're connecting to (note: this may be different to the version of the Chrome app you're running)? The easiest way to check is to have the remote user open the console following the instructions in #5. There will be a log line near the top telling us the host version (in your log file it reads host_controller.js:20 Host version: 50.0.2661.22). This is logged as soon as you run the app--there's no need to try to make a connection.

application.js:86 Chrome Remote Desktop version: 51.0.2704.7 (v2)
ui_mode.js:122 App mode: home
host_controller.js:20 Host version: 50.0.2661.22

Is that what you are looking for?

Trying to connect an Asus C100P Chromebook to an Acer Aspire 5570 running Windows 10 using CRD (version 51.0.2704.7) - I was asked to capture a log file and paste it here - from the Chromebook:
------------------------------------------------------------------------------
Chrome Remote Desktop version: 51.0.2704.7 (v2)
Native Message port disconnected host_daemon_facade.js:221
Host version not available.
App mode: home
Native Message port disconnected host_daemon_facade.js:221
Pairing registry not supported by host.
Native Message port disconnected host_daemon_facade.js:221
Pairing registry not supported by host.
App mode: home.client.unconnected
App mode: home.client.connecting
DNS blackhole check succeeded.
FallbackSignalStrategy progress: xmpp succeeded
[0502/201922:INFO:chromoting_instance.cc(609)] Connecting to sj200aa@gmail.com/chromoting7DFE9ECA. Local jid: sj200aa@gmail.com/...
[2016-05-02T20:19:22.964Z]Sending Iq: <iq xmlns="jabber:client" to="sj200aa@gmail.com/chromoting7DFE9ECA" type="set" id="8312073021101533677"><jingle xmlns="urn:xmpp:jingle:1" sid="2479970124441656926" action="session-initiate" initiator="sj200aa@gmail.com/chromoting0CDBCB61"><content name="chromoting" creator="initiator"><description xmlns="google:remoting"><standard-ice/><control transport="mux-stream" version="3"/><event transport="mux-stream" version="2"/><video transport="stream" version="2" codec="vp9"/><video transport="stream" version="2" codec="vp8"/><audio transport="mux-stream" version="2" codec="opus"/><audio transport="none"/><authentication supported-methods="third_party_spake2_curve25519,third_party,pair_spake2_curve25519,spake2_pair,spake2_curve25519,spake2_hmac"/></description></content></jingle></iq>
[2016-05-02T20:19:22.982Z]iq send id=16193925727876350694 get google:jingleinfo
Connecting as sj200aa@gmail.com
[2016-05-02T20:19:23.058Z]iq receive id=16193925727876350694 result google:jingleinfo
  stun 'stun.l.google.com' udp:19302; 'alt3.stun.l.google.com' udp:19302; 'alt2.stun.l.google.com' udp:19302; 'alt4.stun.l.google.com' udp:19302; 'alt1.stun.l.google.com' udp:19302; 
  relay 'relay.google.com' udp:19305 tcp:19305 tcpssl:443;  token: CAESGgoRc2oyMDBhYUBnbWFpbC5jb20Qk5CKp8cqGhCvX8Gu8G+NNd/sYIPBs9nA
[2016-05-02T20:19:23.231Z]iq receive id=8312073021101533677 result (empty)
[2016-05-02T20:19:23.564Z]Receiving Iq: <iq xmlns="jabber:client" to="sj200aa@gmail.com/chromoting0CDBCB61" type="set" id="7694701936014961865" from="sj200aa@gmail.com/chromoting7DFE9ECA"><jingle xmlns="urn:xmpp:jingle:1" sid="2479970124441656926" action="session-terminate"><reason><incompatible-parameters/></reason></jingle></iq>
[2016-05-02T20:19:23.572Z]iq send id=7694701936014961865 result (empty)
Connection failed: ERROR_INCOMPATIBLE_PROTOCOL client_session.js:640
App mode: home.client.connect-failed.it2me
App mode: home
App mode: home.client.unconnected
App mode: home.client.connecting
DNS blackhole check succeeded.
FallbackSignalStrategy progress: xmpp succeeded
[0502/202124:INFO:chromoting_instance.cc(609)] Connecting to sj200aa@gmail.com/chromoting7DFE9ECA. Local jid: sj200aa@gmail.com/...
[2016-05-02T20:21:24.224Z]Sending Iq: <iq xmlns="jabber:client" to="sj200aa@gmail.com/chromoting7DFE9ECA" type="set" id="11273787972379671760"><jingle xmlns="urn:xmpp:jingle:1" sid="8339322915158443392" action="session-initiate" initiator="sj200aa@gmail.com/chromoting19C6AD89"><content name="chromoting" creator="initiator"><description xmlns="google:remoting"><standard-ice/><control transport="mux-stream" version="3"/><event transport="mux-stream" version="2"/><video transport="stream" version="2" codec="vp9"/><video transport="stream" version="2" codec="vp8"/><audio transport="mux-stream" version="2" codec="opus"/><audio transport="none"/><authentication supported-methods="third_party_spake2_curve25519,third_party,pair_spake2_curve25519,spake2_pair,spake2_curve25519,spake2_hmac"/></description></content></jingle></iq>
[2016-05-02T20:21:24.233Z]iq send id=7585410961709884136 get google:jingleinfo
Connecting as sj200aa@gmail.com
[2016-05-02T20:21:24.311Z]iq receive id=7585410961709884136 result google:jingleinfo
  stun 'stun.l.google.com' udp:19302; 'alt4.stun.l.google.com' udp:19302; 'alt1.stun.l.google.com' udp:19302; 'alt2.stun.l.google.com' udp:19302; 'alt3.stun.l.google.com' udp:19302; 
  relay 'relay.google.com' udp:19305 tcp:19305 tcpssl:443;  token: CAESGgoRc2oyMDBhYUBnbWFpbC5jb20QuMORp8cqGhDjp4BYFBh/oJNPME99Eymv
[2016-05-02T20:21:24.527Z]iq receive id=11273787972379671760 result (empty)
[2016-05-02T20:21:24.563Z]Receiving Iq: <iq xmlns="jabber:client" to="sj200aa@gmail.com/chromoting19C6AD89" type="set" id="13627103069419843796" from="sj200aa@gmail.com/chromoting7DFE9ECA"><jingle xmlns="urn:xmpp:jingle:1" sid="8339322915158443392" action="session-terminate"><reason><incompatible-parameters/></reason></jingle></iq>
[2016-05-02T20:21:24.570Z]iq send id=13627103069419843796 result (empty)
Connection failed: ERROR_INCOMPATIBLE_PROTOCOL client_session.js:640
App mode: home.client.connect-failed.it2me

I've been able to repro this locally. It only affects IT2Me (remote support) and only if the host is on M50 and the client is on M51.

Repro steps:

* Install M50 host package.
* Install M51 Chrome app.
* Share host.
* Connect to host on same machine.

This should give the "hall of mirrors" effect, but instead gives the incompatible protocol error.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/5c5aec85e2efd5777723c61b3b13b59f6f235331

commit 5c5aec85e2efd5777723c61b3b13b59f6f235331
Author: jamiewalch <jamiewalch@chromium.org>
Date: Tue May 03 01:21:11 2016

Fix IT2Me protocol error connecting to old hosts.

This is a revert of the client-side changes introduced in https://codereview.chromium.org/1799293002.
Pre-M51 IT2Me hosts do not support anything except spake2-plain, so M51 and later clients cannot
connect to them

BUG= 607643 

Review-Url: https://codereview.chromium.org/1944553002
Cr-Commit-Position: refs/heads/master@{#391140}

[modify] https://crrev.com/5c5aec85e2efd5777723c61b3b13b59f6f235331/remoting/protocol/negotiating_authenticator_base.cc
[modify] https://crrev.com/5c5aec85e2efd5777723c61b3b13b59f6f235331/remoting/protocol/negotiating_authenticator_base.h
[modify] https://crrev.com/5c5aec85e2efd5777723c61b3b13b59f6f235331/remoting/protocol/negotiating_client_authenticator.cc
[modify] https://crrev.com/5c5aec85e2efd5777723c61b3b13b59f6f235331/remoting/protocol/negotiating_host_authenticator.cc

Requesting merge to M51. This change only affects Chrome Remote Desktop.

What are the implication for us? Do we need to wait for the next version to be available in chrome store? 

If so do you have an approximate date?

Thank you

I've turned off the roll-out of the web-app, but if you've already got the new version, it won't revert. If you remove it and reinstall it from the web store, then you might get the old version, I'm not sure. The other option is to update the host component. Depending on the platform, you can use one of the following URLs:

Windows: http://redirector.gvt1.com/edgedl/chrome-remote-desktop/chromeremotedesktophost-51.0.2704.7.msi

Mac: http://dl.google.com/dl/chrome-remote-desktop/chromeremotedesktophost-51.0.2704.7.dmg

We will be releasing a new Chrome app that fixes the problem ASAP.

I replaced the host with the link you gave me for windows. It's working fine now. Will test reinstalling on another computer tomorrow and see if it's working.

Thank you very much for your help
Pierre

I was able to test by uninstalling and reinstaling from the web store. Did not work.

Would be nice to have an option to have 1-2 older version available on the web store for problems like that.

Thanks 

Your change meets the bar and is auto-approved for M51 (branch: 2704)

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/eaf2e629ca99893cca93dfafe1e7e7338cd2907e

commit eaf2e629ca99893cca93dfafe1e7e7338cd2907e
Author: Jamie Walch <jamiewalch@chromium.org>
Date: Wed May 04 00:33:54 2016

Fix IT2Me protocol error connecting to old hosts.

This is a revert of the client-side changes introduced in https://codereview.chromium.org/1799293002.
Pre-M51 IT2Me hosts do not support anything except spake2-plain, so M51 and later clients cannot
connect to them

BUG= 607643 

Review-Url: https://codereview.chromium.org/1944553002
Cr-Commit-Position: refs/heads/master@{#391140}
(cherry picked from commit 5c5aec85e2efd5777723c61b3b13b59f6f235331)

Review URL: https://codereview.chromium.org/1950813002 .

Cr-Commit-Position: refs/branch-heads/2704@{#368}
Cr-Branched-From: 6e53600def8f60d8c632fadc70d7c1939ccea347-refs/heads/master@{#386251}

[modify] https://crrev.com/eaf2e629ca99893cca93dfafe1e7e7338cd2907e/remoting/protocol/negotiating_authenticator_base.cc
[modify] https://crrev.com/eaf2e629ca99893cca93dfafe1e7e7338cd2907e/remoting/protocol/negotiating_authenticator_base.h
[modify] https://crrev.com/eaf2e629ca99893cca93dfafe1e7e7338cd2907e/remoting/protocol/negotiating_client_authenticator.cc
[modify] https://crrev.com/eaf2e629ca99893cca93dfafe1e7e7338cd2907e/remoting/protocol/negotiating_host_authenticator.cc

Any word on when a v52 will be released including this patch? As far as I can tell at the moment the only available host versions for Mac and Linux are v50 and the only client is v51, so effectively all interop with Mac and Linux hosts is broken.

You can get M51 for Mac from https://dl.google.com/dl/chrome-remote-desktop/chromeremotedesktophost-51.0.2704.7.dmg. Linux is not available publicly yet.

However, we have rolled back the web-app release, so you shouldn't be seeing this any more. If you are, please let us know the version number of the client (check chrome://extensions)

What is the status for Windows users?

Both links are in comment #17, but my point about the web-app applies to all platforms. If you're still seeing this, please let us know the web-app version on the client.

Thanks - I misunderstood.

You asked if someone was still having issues. I am. Clicking Send Ctrl-Alt-Del was not working at all.

- CRD client version is 51.0.2704.40.
- I have installed version 51.0.2704.7 on Windows Server 2012.
- ChromeOS
  Version 51.0.2704.42 beta (64-bit)
  Platform 8172.28.0 (Official Build) beta-channel gandof
  Firmware Google_Gandof.6301.155.9

I got around the issue by turning off the requirement for it on the Windows server. 

This sounds like  bug 611251 . We have a fix pending.

Verified Fixed in 51.0.2704.53