Open GoogleCodeExporter opened 9 years ago
Almost all enterprise networks block packets that are required for discovery
(due to the size of such networks and the amount of traffic that would be
added, or security reasons, etc) and as a result, even if we add such feature,
it will not make chromecast useful in such environment. We are looking into
other approaches to address these types of environments; no timeline is set or
known at this time though.
Original comment by anad...@google.com
on 1 Aug 2014 at 6:03
My home network uses WPA2 enterprise.
Original comment by ste...@stevenroddis.com
on 19 Aug 2014 at 4:02
using WPA2 enterprise at home.
Original comment by htenbe...@gmail.com
on 24 Aug 2014 at 5:06
Also using WPA2 Enterprise at home, need support.
Original comment by joe.wilc...@gmail.com
on 21 Sep 2014 at 3:35
WPA2 Enterprise here. No filtering between source and the chromecast on this
network.
Original comment by mpcat...@gmail.com
on 22 Oct 2014 at 7:12
I've secured our office network with radius and wpa2 enterprise on 802.1x, now
we can no longer use the chromecast.
Original comment by vru...@gmail.com
on 6 Nov 2014 at 4:11
The statement that most enterprise networks block the packets needed for
discovery is no longer true. Most of the enterprise VOIP phone solutions these
days require multicast to discover the call manager, and for point to point
calling. Consequently these networks now allow those multicast discovery
packets, where they once were blocked. Were enterprise WPA2 authentication
added to chromecast, it would, in fact, be commonly useful in those
environments.
Original comment by dot...@gmail.com
on 11 Nov 2014 at 6:16
Now that Chromecast supports guest mode
(https://support.google.com/chromecast/answer/6109286) which presumably uses a
different discovery mechanism to broadcast packets, the original response to
this issue is no longer valid.
Original comment by victor.r...@jmss.vic.edu.au
on 11 Dec 2014 at 10:48
Also using WPA2 Enterprise at home, please add support.
Original comment by ralph...@gmail.com
on 13 Dec 2014 at 8:06
This is clearly not a defect. The reason for closing the enhancement is an
assumption that is wrong.
I suggest you or your strategy team do a bit of market research on what
business this feature would enable. I can easily envision a new office / school
segment where screen casting would be enabled by using chromecast devices
plugged into projectors or large tv's in conference rooms or class rooms.
There is a market - if google wants it or not i don't know - this was the
intended use for me so my chromecast is useless. No big deal - i guess i will
have a look the apple tv instead.
Original comment by 3h.nils...@gmail.com
on 24 Jan 2015 at 11:18
Issue 497 has been merged into this issue.
Original comment by anad...@google.com
on 29 Jan 2015 at 11:45
It would be super if CC would support WPA2/Enterprise... I can't use CC at the
office, and this issue is preventing me from deploying Enterprise at home.
Original comment by a...@riverbed.com
on 12 Feb 2015 at 8:30
Even if an enterprise were to block packets from the internet, it says nothing
to the screen mirroring option. This would allow for using Chromecast for
presentations and meetings. The possible uses are many and it is a shame that
it seems that WPA2 Enterprise would not be developed for such an arguement as
"They might block these packets".
Original comment by despade...@gmail.com
on 16 Mar 2015 at 6:09
We're trying to keep our enterprise network on a single SSID, and don't want to
provision another just for chromecast! We're using VLANs over wifi for
students/staff etc. We'll build ACLs for the protocols.
Please just allow the option.
Original comment by simon.pa...@colegsirgar.ac.uk
on 19 Mar 2015 at 3:07
Please, add support for WPA2 Enterprise! Nexus Player has the same problem.
Cannot use in the office or in class!!
Original comment by alexis.f...@gmail.com
on 14 Apr 2015 at 7:18
We don't have plans to support WPA2 Enterprise Encryption on Chromecast at this
time. We will continue to evaluate this as a feature request for the future.
Original comment by jonathan...@google.com
on 30 Apr 2015 at 11:22
Original issue reported on code.google.com by
rougeg...@gmail.com
on 10 Jul 2014 at 4:37