Issue 344372 in chromium: Chrome Remote Desktop "unable to reach host"

[chro...@googlecode.com]

Status: Unconfirmed
Owner: ----
Labels: Cr-Internals-Network Pri-2 Via-Wizard Type-Bug OS-Windows

New issue 344372 by farac...@gmail.com: Chrome Remote Desktop "unable to
reach host"
http://code.google.com/p/chromium/issues/detail?id=344372

UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML,
like Gecko) Chrome/32.0.1700.107 Safari/537.36

Example URL:

Steps to reproduce the problem:
1. Open chrome remote desktop
2. Attempt to connect to remote desktop
3. Enter in pin

What is the expected behavior?

What went wrong?
Instead of connecting I get the message "Unable to reach the host. This is
probably due to the configuration of the network you are using."

Did this work before? No

Chrome version: 32.0.1700.107 Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 12.0 r0

My other computers on this network are able to connect to the remote
desktop which resides on a separate network.

Here is some javascript console output when the error occurs:

[0217/112530.309] Receiving Iq: <cli:iq
to="fara...@gmail.com/TalkGadget03C457C5" type="error"
id="3B7B33B00598536B" from="remo...@bot.talk.google.com"
xmlns:cli="jabber:client"><rem:log xmlns:rem="google:remoting"><rem:entry
browser-version="32.0.1700.107" connection-error="p2p-failure"
event-name="session-state" mode="me2me" os-name="Windows" os-version="6.1"
role="client" session-duration="33.174" session-id="c6K5ZdeUnCyA4NiF4604"
session-state="connection-failed"
webapp-version="32.0.1700.99"/></rem:log><cli:error code="500" type="wait"
err:stacktrace="com.google.buzz.shared.gateway.packet.Stanza.buildError(Stanza.java:882)
| com.google.buzz.shared.gateway.packet.Stanza.buildError(Stanza.java:790)
|
com.google.buzz.bot.StandardBot.handleForwardStanzaHelper(StandardBot.java:478)
| com.google.buzz.bot.StandardBot.handleForwardStanza(StandardBot.java:434)
| com.google.buzz.bot.Bot$3.runInContext(Bot.java:201) |
com.google.tracing.TraceContext$TraceContextRunnable$1.run(TraceContext.java:453)
| com.google.tracing.TraceContext.runInContext(TraceContext.java:740) |
com.google.tracing.TraceContext$DoInTraceContext.runInContext(TraceContext.java:717)
|
com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedContextNoUnref(TraceContext.java:308)
|
com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedContext(TraceContext.java:300)
|
com.google.tracing.TraceContext$TraceContextRunnable.run(TraceContext.java:450)
| java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) |
java.util.concurrent.FutureTask.run(FutureTask.java:237) |
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:151)
|
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:264)
|
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
|
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
| " xmlns:err="google:rich-errors"><undefined-condition
xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/></cli:error></cli:iq>


Attachments:
net-internals-log.json 562 KB

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[chro...@googlecode.com]

Updates:
Labels: Needs-Feedback

Comment #1 on issue 344372 by sday...@chromium.org: Chrome Remote

Desktop "unable to reach host"
http://code.google.com/p/chromium/issues/detail?id=344372

can you please install chrome version 33.0.1750.117 channel:stable and try
the same scenario and let me know if u facing same issue.Is your network
using only chrome ?is it working fine with Firefox or any other browser?

[chro...@googlecode.com]

Comment #2 on issue 344372 by sday...@chromium.org: Chrome Remote

Desktop "unable to reach host"
http://code.google.com/p/chromium/issues/detail?id=344372

can you please install chrome latest version 33.0.1750.117 channel:stable

and try the same scenario and let me know if u facing same issue.Is your

network using only chrome ?is that with other sources ,remote access is
working fine?

[chro...@googlecode.com]

Comment #3 on issue 344372 by sday...@chromium.org: Chrome Remote

Desktop "unable to reach host"
http://code.google.com/p/chromium/issues/detail?id=344372

can you please install chrome latest version 33.0.1750.117 channel:stable
and try the same scenario and let me know if u facing same issue.Is your
network using only chrome ?is that with other sources ,remote access is

working fine?can you give me in detail information, if u are getting same
issue.

[chro...@googlecode.com]

Comment #4 on issue 344372 by farac...@gmail.com: Chrome Remote

Desktop "unable to reach host"
http://code.google.com/p/chromium/issues/detail?id=344372

Using 33.0.1750.117 I'm getting the same problem.

Here's the javascript console output:

[0226/082006.917] iq receive id=220 set session-terminate
sid=975690497916502866
reason=general-error client_session.js:794
[0226/082006.928] iq send id=220 result (empty) client_session.js:740
Enqueueing log entry: log_to_server.js:180
role: client, event-name: session-state, session-state:
connection-failed, connection-error: p2p-failure, mode: me2me, os-name:
Windows, os-version: 6.1, browser-version: 33.0.1750.117, webapp-version:
33.0.1750.125, session-id: sDFkDxa3kZfuay6SJ27Q, session-duration: 33.207
server_log_entry.js:200
Sending 1 log entry to the server. log_to_server.js:185
Client plugin reported connection failed: ERROR_P2P_FAILURE
session_connector.js:438
Connection failed: ERROR_P2P_FAILURE client_screen.js:156
App mode: home.client.connect-failed.me2me ui_mode.js:120
2
Refused to evaluate a string as JavaScript because 'unsafe-eval' is not an
allowed source of script in the following Content Security Policy
directive: "script-src 'self' https://*.talkgadget.google.com".

iq?access_token=ya29.1.AADtN_XfZrA_EPusJ3WXqAygD5kIBdBgUzaFMp8MKgLHS1YRNdCpe8KYUIgYqX_HTg_oQ2Dpvw:9
[0226/082007.148] Receiving Iq: <cli:iq
to="fara...@gmail.com/TalkGadget8F335D43" type="error"
id="952CEDC0C6616AC5" from="remo...@bot.talk.google.com"

xmlns:cli="jabber:client"><rem:log xmlns:rem="google:remoting"><rem:entry

browser-version="33.0.1750.117" connection-error="p2p-failure"

event-name="session-state" mode="me2me" os-name="Windows" os-version="6.1"

role="client" session-duration="33.207" session-id="sDFkDxa3kZfuay6SJ27Q"
session-state="connection-failed"
webapp-version="33.0.1750.125"/></rem:log><cli:error code="500" type="wait"

err:stacktrace="com.google.buzz.shared.gateway.packet.Stanza.buildError(Stanza.java:882)
| com.google.buzz.shared.gateway.packet.Stanza.buildError(Stanza.java:790)
|
com.google.buzz.bot.StandardBot.handleForwardStanzaHelper(StandardBot.java:478)
| com.google.buzz.bot.StandardBot.handleForwardStanza(StandardBot.java:434)
| com.google.buzz.bot.Bot$3.runInContext(Bot.java:201) |
com.google.tracing.TraceContext$TraceContextRunnable$1.run(TraceContext.java:453)
| com.google.tracing.TraceContext.runInContext(TraceContext.java:740) |
com.google.tracing.TraceContext$DoInTraceContext.runInContext(TraceContext.java:717)
|
com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedContextNoUnref(TraceContext.java:308)
|
com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedContext(TraceContext.java:300)
|
com.google.tracing.TraceContext$TraceContextRunnable.run(TraceContext.java:450)
| java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) |
java.util.concurrent.FutureTask.run(FutureTask.java:237) |
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:151)
|
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:264)
|
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
|
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
| " xmlns:err="google:rich-errors"><undefined-condition
xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/></cli:error></cli:iq>

I'm not sure what you mean by "Is your network using only chrome ?" I am
able to connect with chrome remote desktop to my home network from this
network (not my home network) using a different Windows 7 computer. I have
also attempted to connect from the problem computer after disabling Windows
Firewall but this did not change the outcome.

[chro...@googlecode.com]

Updates:
Status: Assigned
Owner: w...@chromium.org
Labels: Cr-Services-Chromoting

Comment #5 on issue 344372 by cben...@chromium.org: Chrome Remote

Desktop "unable to reach host"
http://code.google.com/p/chromium/issues/detail?id=344372

(No comment was entered for this change.)

[chro...@googlecode.com]

Updates:
Labels: -Cr-Internals-Network

Comment #6 on issue 344372 by cben...@chromium.org: Chrome Remote

[chro...@googlecode.com]

Comment #8 on issue 344372 by farac...@gmail.com: Chrome Remote

Desktop "unable to reach host"
http://code.google.com/p/chromium/issues/detail?id=344372

A status update: I have upgraded the host computer (home) to windows 8
(previously windows 7) with a fresh install. I am still UNABLE to access
it on my work desktop and still ABLE to access on other computers on my
work network as well as from computers on other networks.

[chro...@googlecode.com]

Comment #9 on issue 344372 by jamie...@chromium.org: Chrome Remote

Desktop "unable to reach host"
http://code.google.com/p/chromium/issues/detail?id=344372

To clarify the situation, are you saying that you have several computers on
one network, and that all but one of them is able to connect to another
computer on a different network? In that case, it suggests that the problem
is with the one computer that can't connect. Is there any firewall software
running on the computer?

[chro...@googlecode.com]

Comment #10 on issue 344372 by farac...@gmail.com: Chrome Remote

Desktop "unable to reach host"
http://code.google.com/p/chromium/issues/detail?id=344372

Yes, that is the situation. It does seem to be an issue with that specific
computer. It has Windows Firewall but I have tried disabling it entirely
to no avail.

[chro...@googlecode.com]

Comment #11 on issue 344372 by jamie...@chromium.org: Chrome Remote

Desktop "unable to reach host"
http://code.google.com/p/chromium/issues/detail?id=344372

Can you provide us with the full Javascript logs for a connection attempt?
Also, what are the characteristics of the client and host networks?
Specifically, how are they connected to the internet.

[chro...@googlecode.com]

Comment #14 on issue 344372 by farac...@gmail.com: Chrome Remote

Desktop "unable to reach host"
http://code.google.com/p/chromium/issues/detail?id=344372

I've included the full log in a file in which I have masked the client ip
address and email.

Attachments:
js_log.txt 30.5 KB

[chro...@googlecode.com]

Comment #17 on issue 344372 by jamie...@chromium.org: Chrome Remote

Desktop "unable to reach host"
http://code.google.com/p/chromium/issues/detail?id=344372

Judging by your logs, it looks like that's still the case. Our working
theory is that we have a bug that means this case is not handled correctly,
in which case changing the IP address of one end of the connection should
work around the problem.

[chro...@googlecode.com]

Comment #18 on issue 344372 by farac...@gmail.com: Chrome Remote

Desktop "unable to reach host"
http://code.google.com/p/chromium/issues/detail?id=344372

Well... Wouldn't you know, I do still have the same static IP on this new
Windows 8 install. I now vaguely recall assigning it to my mac address
from my router at some point. So yeah, same local IP on host and client.

[chro...@googlecode.com]

Comment #19 on issue 344372 by farac...@gmail.com: Chrome Remote

Desktop "unable to reach host"
http://code.google.com/p/chromium/issues/detail?id=344372

I have done further testing to attempt prove the theory.

1. Testing is performed with the previously mentioned client/host situation
reversed. The client I couldn't connect with is now the host for the
test. The host I couldn't connect to is now the client.
2. Attempting connection to host results in same inability to connect.
3. Changed local IP address of client to something else.
4. Attempting connection now works fine.

This behavior appears to support your theory.