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

Issue 866557 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Oct 2
Cc:
█ krajshree@chromium.org
susan.boorgula@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

crd_main.js:132 Pairing registry not supported by host.

Reported by rajender...@gmail.com, Jul 23 
UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36

Steps to reproduce the problem:
when i access chrome rdp i get the below error 

What is the expected behavior?
crd_main.js:132 Pairing registry not supported by host.

What went wrong?
below is the messages from console

console_wrapper.js:115 Native Message port disconnected host_daemon_facade.js:221
remoting.ConsoleWrapper.recordAndLog_ @ console_wrapper.js:115
remoting.HostDaemonFacade.onDisconnect_ @ host_daemon_facade.js:221
EventImpl.dispatchToListener @ extensions::event_bindings:403
publicClassPrototype.(anonymous function) @ extensions::utils:138
EventImpl.dispatch_ @ extensions::event_bindings:387
EventImpl.dispatch @ extensions::event_bindings:409
publicClassPrototype.(anonymous function) @ extensions::utils:138
dispatchOnDisconnect @ extensions::messaging:378
host_controller.js:27 Host version not available.
ui_mode.js:123 App mode: home
console_wrapper.js:115 Native Message port disconnected host_daemon_facade.js:221
remoting.ConsoleWrapper.recordAndLog_ @ console_wrapper.js:115
remoting.HostDaemonFacade.onDisconnect_ @ host_daemon_facade.js:221
EventImpl.dispatchToListener @ extensions::event_bindings:403
publicClassPrototype.(anonymous function) @ extensions::utils:138
EventImpl.dispatch_ @ extensions::event_bindings:387
EventImpl.dispatch @ extensions::event_bindings:409
publicClassPrototype.(anonymous function) @ extensions::utils:138
dispatchOnDisconnect @ extensions::messaging:378
crd_main.js:132 Pairing registry not supported by host.
console_wrapper.js:115 Native Message port disconnected host_daemon_facade.js:221
remoting.ConsoleWrapper.recordAndLog_ @ console_wrapper.js:115
remoting.HostDaemonFacade.onDisconnect_ @ host_daemon_facade.js:221
EventImpl.dispatchToListener @ extensions::event_bindings:403
publicClassPrototype.(anonymous function) @ extensions::utils:138
EventImpl.dispatch_ @ extensions::event_bindings:387
EventImpl.dispatch @ extensions::event_bindings:409
publicClassPrototype.(anonymous function) @ extensions::utils:138
dispatchOnDisconnect @ extensions::messaging:378
crd_main.js:132 Pairing registry not supported by host.

Did this work before? Yes same veriosn

Chrome version: 67.0.3396.99  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: 

Please help

Comment 1 by rajender...@gmail.com, Jul 23 

below is additional messages

[0723/174340.914690:ERROR:pepper_packet_socket_factory.cc(399)] Received error when reading from UDP socket: -101

main.html#:1 [0723/174340.948070:ERROR:pepper_packet_socket_factory.cc(399)] Received error when reading from UDP socket: -101

main.html#:1 [0723/174340.948960:ERROR:pepper_packet_socket_factory.cc(399)] Received error when reading from UDP socket: -101

main.html#:1 [0723/174341.483580:ERROR:pepper_packet_socket_factory.cc(399)] Received error when reading from UDP socket: -101

main.html#:1 [0723/174342.448070:ERROR:pepper_packet_socket_factory.cc(352)] Send failed on a UDP socket: -2

main.html#:1 [0723/174342.448370:ERROR:pepper_packet_socket_factory.cc(352)] Send failed on a UDP socket: -2

main.html#:1 [0723/174342.521060:ERROR:pepper_packet_socket_factory.cc(352)] Send failed on a UDP socket: -2

main.html#:1 [0723/174342.521460:ERROR:pepper_packet_socket_factory.cc(352)] Send failed on a UDP socket: -2

Comment 2 by cthomp@chromium.org, Jul 23

Components: Services>Chromoting
Labels: Needs-Feedback
I'm not sure what the security bug is here. Could you please provide more details on what is happening and how to reproduce this? Are you unable to initiate Chrome Remote Desktop connections, or is a security control failing to operate correctly?

Comment 3 by rajender...@gmail.com, Jul 23 

Thanks for the swift response. When I initiate the RDP I get the screen for PIN and when i enter the PIN. I get the above message such as "Received error when reading from UDP socket:" and "Send failed on a UDP socket: -2"

Further, This was working all well until yesterday and today i'm getting the above mentioned issue.. 

Any info to trace the root cause is greatly appreciated.
Project Member

Comment 4 by sheriffbot@chromium.org, Jul 23

Cc: cthomp@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 5 by cthomp@chromium.org, Jul 23

Cc: -cthomp@chromium.org
Labels: -Type-Bug-Security -Restrict-View-SecurityTeam Type-Bug
Thanks for the quick feedback as well.

Moving this out of the security bug queue and opening it up so that the Chromoting team can take a look and hopefully figure out what is wrong.

Comment 6 by krajshree@chromium.org, Jul 24

Labels: Needs-Triage-M67

Comment 7 by krajshree@chromium.org, Jul 24

Cc: krajshree@chromium.org
Labels: Triaged-ET Needs-Feedback
Unable to reproduce the issue on Win-10 using chrome reported version #67.0.3396.99 and latest canary #70.0.3500.0.
Attached a screen cast for reference.

Observed that able to access the remote desktop after entering the screen for PIN without any issues.
reporter@ - Could you please check the attached screen cast and please let us know if anything missed from our end.

Thanks...!!
866557.mp4
1.1 MB View Download

Comment 8 by rajender...@gmail.com, Jul 24 

Thank you.. Can you provide me the trace on when one would receive such error as listed below. Is this something related to network issue??

main.html#:1 [0723/174341.483580:ERROR:pepper_packet_socket_factory.cc(399)] Received error when reading from UDP socket: -101

main.html#:1 [0723/174342.448070:ERROR:pepper_packet_socket_factory.cc(352)] Send failed on a UDP socket: -2
Project Member

Comment 9 by sheriffbot@chromium.org, Jul 24

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 10 by jamiewa...@chromium.org, Jul 24 

That error is not fatal, it's just notifying that one particular feature is not supported on this platform. What are you trying to do, and what error message does the app display (not in the JavaScript console) when you try it?

Can you try our new website at remotedesktop.google.com and let us know if you have the same (or similar) problems?

Comment 11 by susan.boorgula@chromium.org, Jul 30

Cc: susan.boorgula@chromium.org
Labels: Needs-Feedback
Adding 'Needs-Feedback' label as per comment #10.

rajender.reddi@ Request you to retry the issue as per comment #10 and update the thread with the observations.

Thanks..

Comment 12 by jamiewa...@chromium.org, Oct 2

Status: WontFix (was: Unconfirmed)
►

Sign in to add a comment