Closed GoogleCodeExporter closed 8 years ago
Please describe as to why you need to access to Chromecast on another network.
What is your use case?
Original comment by na...@google.com
on 24 Jul 2015 at 6:23
Imagine we are in a shared office, shared meeting room, or hotel's meeting
room, which a chromecast and a TV is provided, for presentation use.
If we are not in the same wifi network, we could not select that chromecast.
If we are in shared office, most likely we are in different network (office and
owner)
If we are in hotel, which usually wifi of cell phone is different from the
chromecast one (cell phone one may require web login).
Also, if we are in a place which a lot of chromecast is in same network in
close area (e.g. university hostel / classroom). We may select a wrong
chromecast for display. And so, separate networks, and select chromecast using
PIN is preferred in this case.
Original comment by seventhm...@gmail.com
on 25 Jul 2015 at 7:26
For scenario one, ideally you should be able to connect to a Chromecast through
Guest Mode provided you are within the wifi rage (wifi the Chromecast is on).
You can troubleshoot for Guest Mode here:
https://support.google.com/chromecast/troubleshooter/2995236?hl=en
For scenarios two and three, please note the Chromecast that you are trying to
connect to should have Guest Mode enabled and also you should be within the
wifi range (typically within 35 feet). More on Guest Mode here:
https://support.google.com/chromecast/answer/6109286?hl=en&ref_topic=6109288&rd=
1
Original comment by na...@google.com
on 27 Jul 2015 at 5:13
Sorry, wifi rage is typically 25 feet. Please note that your use case can be
facilitate through the existing Guest Mode. Hope that helps.
Original comment by na...@google.com
on 27 Jul 2015 at 5:17
No.
The "near by devices" option is shown only if there is no cast device in the
same network.
If there is one, I cannot choose "near by devices".
However, I want the near by devices available even there is cast device in same
network.
Original comment by seventhm...@gmail.com
on 30 Jul 2015 at 10:15
Original issue reported on code.google.com by
seventhm...@gmail.com
on 24 Jul 2015 at 8:25