Unable to access remote desktop when using Verizon MiFi
Reported by
uncledon...@gmail.com,
Aug 1 2017
|
||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS x86_64 9460.73.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.134 Safari/537.36 Platform: 9460.73.1 (Official Build) stable-channel edgar Example URL: N/A Steps to reproduce the problem: 1. Chrome Remote Desktop running as host on Windows 7 PC 2. On 64 bit Chromebook, connect to Internet via Verizon MiFi 3. Run Chrome Remote Desktop and attempt connection to registered host 4- Enter remote password when requested What is the expected behavior? Connection to remote desktop What went wrong? Connection not made and error returned indicating potential network configuration error Did this work before? N/A Chrome version: 59.0.3071.134 Channel: stable OS Version: 9460.73.1 Flash Version: When connecting to internet via non Verizon MiFi, remote session works perfectly
,
Aug 3 2017
Update - Verizon replaced my jetpack with an older model (Aircard 791L) and the problem no longer exists. Therefore the issue needs to be updated to say that the connection error occurs on the Verizon jetpack model MIFI7730L only.
,
Aug 8 2017
Can you send us client logs. To find them: * 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. Copy/paste the logs into this bug and we'll take a look.
,
Aug 9 2017
Unfortunately, I cannot. Verizon replaced the 7730MiFi with a different model and the problem has been rectified. I cannot reproduce the error with my current model.
D
From: jamiewa… via monorail <monorail+v2.2556384244@chromium.org>
To: uncledon999@gmail.com
Sent: Tuesday, August 8, 2017 6:21 PM
Subject: Issue 751247 in chromium: Unable to access remote desktop when using Verizon MiFi
,
Aug 15 2017
Since this appears to be an isolated report and will be difficult for us to investigate, I don't think there's much we can do here. |
||
►
Sign in to add a comment |
||
Comment 1 by mmenke@chromium.org
, Aug 3 2017