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

Issue 882919 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner: ----
Closed: Sep 24
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

no devices found under cast option

Reported by dustinco...@gmail.com, Sep 11

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36

Steps to reproduce the problem:
1.Select cast to open devices to cast to.  Nothing found
2. 
3. 

What is the expected behavior?
My 3 devices, Google mini 1, Google mini 2, Chromecast Ultra should be shown as available devices to cast to.

What went wrong?
No matter what i do no devices are found.  

Did this work before? Yes 68.0.3440.106

Chrome version: 69.0.3497.81  Channel: n/a
OS Version: 10.0
Flash Version: 

My laptop with version 68 ####### still see all devices.  Ran a dns locate script from windows 10 cmd line and windows sees the devices.  Chrome is the bottle neck.  Enabled chrome flag for allowing all IP. nothing working.....
 
Components: Internals>Cast
My laptop with version 68 ####### still see all devices.  Ran a dns locate script from windows 10 cmd line and windows sees the devices.  Chrome is the bottle neck.  Enabled chrome flag for allowing all IP. nothing working.....

Google mini 1, Google mini 2, Chromecast Ultra
Windows 10 PC, 
Asus Router, hardlined to pc, wireless to rest.  

Labels: Needs-Feedback
Thanks for the bug report. Could you please help us gather more information by doing the following on the machine that couldn't find any devices:

- Right click on the cast icon and select report an issue. Then, include this bug number (882919) in the feedback and make sure the "Send debug logs" is checked.
- Could you please go to chrome://inspect and see if devices show up there? If so, please attach a screen shot.
Done and submitted
[image: image.png]
Project Member

Comment 7 by sheriffbot@chromium.org, Sep 11

Cc: imch...@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
Cc: -imch...@chromium.org
Components: -Internals>Cast Internals>Cast>Providers
Owner: imch...@chromium.org
Status: Assigned (was: Unconfirmed)
Cc: dustinco...@gmail.com
Labels: Needs-Feedback
Thank you. I received the feedback report, but it looks like the screenshot didn't get attached properly. Nonetheless, from the feedback it looks like the attempts to connect to the three devices kept timing out. This looks like a network issue. Could you try connecting to those devices on port 8009, which is the port used for Cast devices? (using telnet or similar)
I will try once i get home from work today.  However i can tell you that i
can cast from my laptop to the devices and from both phones within the
house.
Here is the requested screen shot.

[image: image.png]
Status: Unconfirmed (was: Assigned)
Owner: ----
Project Member

Comment 13 by sheriffbot@chromium.org, Sep 24

Cc: imch...@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
Labels: Needs-Feedback
Hi Dustin,

If the problem still persists, please let us know if you're having trouble connecting to the devices directly per comment #9.
I could telnet into devices from my laptop (not effected) but i couldnt
from the PC.  After a lot of trial and error, I had to force an IP change
to my PC.  After doing that I was able to telnet into devices
successfully.  Once that happened and with a reinstall of chrome i was able
to see the devices under cast option within chrome.  I remapped my
streaming services and was able to get things working correctly.

Thank you gentlemen for all the help and feed back with this issue.
Status: Fixed (was: Unconfirmed)
Thanks Dustin, closing this bug. 

Sign in to add a comment