I am involved in a project that will potentially utilise Chromecasts out in the field.
Our main concern is that if the CC is attached to a publicly accessible WiFi AP, it can be tampered with, and inappropriate material cast to it.
Of course, we can create a private WiFi AP to use for the sole purpose of the CC, which is an acceptable solution.
But I'd like to know if there are other options available. I have seen there is a CC "ROM" that can be flashed to the device to replace the original firmware. Does this new firmware include any added security, or indeed offer the possibility to add extra security?
mr_pablo said:
I am involved in a project that will potentially utilise Chromecasts out in the field.
Our main concern is that if the CC is attached to a publicly accessible WiFi AP, it can be tampered with, and inappropriate material cast to it.
Click to expand...
Click to collapse
No added security in Eureka-ROM today.
You do not want to have Chromecast connected to a public network as on a properly-configured public network, AP isolation will be enabled, making Chromecast inoperable (unless you just want to see the screen saver).
Chromecast simply isn't designed for public use. Many of the design decisions including setup assumes a controlled, trusted home environment.
You can set up your own AP, but that's as close as you'll get, and someone who forces Chromecast to disconnect from the AP can still reconfigure it.
Sorry but what do you mean AP isolation will be enabled making CC unusable?
Also, if the CC is on a secured AP (hidden SSID) is it possible to make it disconnect then? Doesn't the attacker need to be on the same AP?
mr_pablo said:
Sorry but what do you mean AP isolation will be enabled making CC unusable?
Also, if the CC is on a secured AP (hidden SSID) is it possible to make it disconnect then? Doesn't the attacker need to be on the same AP?
Click to expand...
Click to collapse
When AP isolation is enabled, wireless clients cannot access other wireless clients on the network. Other devices would not discover Chromecast, and Chromecast would not receive any cast requests. So it would just sit there showing its wallpaper.
Last year Chromecast was Rickrolled. The fault is in the design of the setup - what makes it super simple to setup also makes it super simple to hijack if its connection to the WiFi network can be interrupted.
I read a bit about the RickPi.
Can it knock a Chromecast off a network without being on the same network itself?
If it can do that, does that mean it's possible to knock any wifi device off its network without being connected to the same initial network?
Related
Why Google you no like college students?
Hmmm this probably raises a good point, it's a bit hard to implement something like 802.1x though on a streamer device (where authentication is required per login of network prior to you having the ability to control the device).
I don't see this coming for awhile to be honest unless someone manages to hack it in - I just can't see Google releasing the ability to cache 802.1x network credential sets unfortunately due to the security implications.
Friend of mine had to buy his own router to plug in to the colleges ethernet ports in the dorm. Solved a variety of issues they were having.
Sent from my Nexus 5 using Tapatalk
fchowd0696 said:
Why Google you no like college students?
Click to expand...
Click to collapse
Beyond the lack of keyboard/interface, large networks in general fear multicast and UPnP because they have potential to easily clog the network.
Also remember that Chromecast in its current state has little security - it's designed for use within a trusted environment.
You probably don't want to be in the middle of Twilight with your girlfriend and suddenly your Chromecast switches over to SpongeBob SquarePants because someone else in the dorm decided BobsChromecast obviously wants to show SpongeBob...
Having your own router and local network will isolate your Chromecast to just your little piece of the campus network, though double-NAT might be an issue, and you should check with campus policy on use of personal WiFi router/AP hardware.
I've got a similar problem. I use a studentnet, were I can either plug in directly into the wall and log in once every day or setup a router with a PPTP-connection to automatically log into the student-network. I've got the latter set up and it works like a charm.
Thankfully I had a rootable CC so I could set it to use my ISP's DNS but I would love if it if I were able to use a different DNS (aka Unlocator/Unblock) to enjoy the US-version of Netflix, but every time I change the DNS-servers my internetconnection dies.
Is there any way to actually do fix my problem? I know this is more of a network-question than a CC-one, but CC is included in the problem
I use a Netgear WNR3500LV2 as my router.
Sent from my LG-D802 using Tapatalk
ninepoint said:
I've got a similar problem. I use a studentnet, were I can either plug in directly into the wall and log in once every day or setup a router with a PPTP-connection to automatically log into the student-network. I've got the latter set up and it works like a charm.
Thankfully I had a rootable CC so I could set it to use my ISP's DNS but I would love if it if I were able to use a different DNS (aka Unlocator/Unblock) to enjoy the US-version of Netflix, but every time I change the DNS-servers my internetconnection dies.
Is there any way to actually do fix my problem? I know this is more of a network-question than a CC-one, but CC is included in the problem
I use a Netgear WNR3500LV2 as my router.
Click to expand...
Click to collapse
First question is whether you can use a different DNS at all (or whether your ISP is blocking somehow).
Try doing a DNS lookup from another server on your phone/tablet via Ping & DNS or another app that lets you do that.
If that's successful, then it might work - go to the Eureka-ROM web panel at http://Chromecast_IP_addresss/ and turn off DHCP-supplied DNS, Apply, then select another DNS.
You will also need to force your phone/tablet to use the same DNS - otherwise your phone/tablet may be making requests from Mars, while Chromecast tries to retrieve stuff from Venus.
I took delivery if a Chromecast today and the setup is a breeze. As I'm in Europe I have changed some settings in order to access the American version of Netflix because if the extended selection of films and series. It runs fine on my Galaxy Note 8, iMac, and Xperia Z1. But it can't run on my TV. Every time I try to cast a film on it I get this error: "Whoops, something went wrong...Device Messaging Error. There was an unrecoverable error on your computer. Please reload the page to resume controlling your device."
I have done some searches and found various possible solutions, but none worked. This is what I've tried:
- Signed out of all devices in Netflix.
- Reset the Chromecast.
- Disabled WWM on the router.
I doubt it's an issue with Netflix as it works fine on all devices except on the TV. Sometimes I do see there is an error on my iMac saying that Microsoft Silverlight has crashed but that doesn't seem to affect anything. Is there anything else I could do to troubleshoot?
slonn said:
I took delivery if a Chromecast today and the setup is a breeze. As I'm in Europe I have changed some settings in order to access the American version of Netflix because if the extended selection of films and series. It runs fine on my Galaxy Note 8, iMac, and Xperia Z1. But it can't run on my TV. Every time I try to cast a film on it I get this error: "Whoops, something went wrong...Device Messaging Error. There was an unrecoverable error on your computer. Please reload the page to resume controlling your device."
Click to expand...
Click to collapse
Please tell us...
What make/model router do you have?
Can you describe how you "changed some settings" to access US Netflix?
Do YouTube and other services work?
If you use your normal DNS settings and access your local Netflix, does it work okay?
Chromecast is its own device and does its own DNS lookups and Internet requests after receiving the "go play this video" request, so if you're redirecting DNS on specific IPs/devices (rather than everything on your network), then you need to be sure the Chromecast IP/device is being redirected.
Otherwise your phone/tablet/computer is in Mens and Chromecast is in the Ladies and...
Phone/tablet/computer: "Excuse me, could you get my phone next to the urinal?"
Chromecast: "What's a urinal??"
bhiga said:
Please tell us...
What make/model router do you have?
Can you describe how you "changed some settings" to access US Netflix?
Do YouTube and other services work?
If you use your normal DNS settings and access your local Netflix, does it work okay?
Chromecast is its own device and does its own DNS lookups and Internet requests after receiving the "go play this video" request, so if you're redirecting DNS on specific IPs/devices (rather than everything on your network), then you need to be sure the Chromecast IP/device is being redirected.
Otherwise your phone/tablet/computer is in Mens and Chromecast is in the Ladies and...
Phone/tablet/computer: "Excuse me, could you get my phone next to the urinal?"
Chromecast: "What's a urinal??"
Click to expand...
Click to collapse
Thanks for your reply.
The router is a Cisco EPC3925.
I used the instructions from the Unblock-us website. Changed the DNS settings to 208.122.23.23 and 208.122.23.22 as instructed. But I also changed the DNS settings to that on the Cisco router - otherwise the US material would not show on my tablet and phone (only on the iMac).
YouTube and Plex work just fine when casting material to the TV.
When using the normal DNS settings from the local Netflix it works fine.
slonn said:
Thanks for your reply.
The router is a Cisco EPC3925.
I used the instructions from the Unblock-us website. Changed the DNS settings to 208.122.23.23 and 208.122.23.22 as instructed. But I also changed the DNS settings to that on the Cisco router - otherwise the US material would not show on my tablet and phone (only on the iMac).
YouTube and Plex work just fine when casting material to the TV.
When using the normal DNS settings from the local Netflix it works fine.
Click to expand...
Click to collapse
Netflix and hulu etc are having issues this morning if you are on a Uverse, if your redirect is a uverse one that may be the issue as well
slonn said:
Thanks for your reply.
The router is a Cisco EPC3925.
I used the instructions from the Unblock-us website. Changed the DNS settings to 208.122.23.23 and 208.122.23.22 as instructed. But I also changed the DNS settings to that on the Cisco router - otherwise the US material would not show on my tablet and phone (only on the iMac).
YouTube and Plex work just fine when casting material to the TV.
When using the normal DNS settings from the local Netflix it works fine.
Click to expand...
Click to collapse
Thanks for the info.
Seems like your core problem is that by default Chromecast uses the Google DNS servers regardless of what DHCP provides, so even though you've set your router so all its DHCP clients are being told to use the Unblock-us DNS, Chromecast still isn't. So all your devices are in the Mens, with the exception of Chromecast, which still goes to the Ladies, even though you tell it go to the Mens, thus it responds with "What's a urinal??" when you reference things in the Mens (US stuff).
Chromecast will fall back to using the DHCP-supplied DNS server(s) only if it doesn't get a response from Google's DNS.
Normally the ways around this would be to:
Route Google DNS requests to a bogus/non-existent gateway
Block Google DNS requests entirely
so Chromecast does not get a response from Google's DNS. Which one works depends on how your router handles the blocking/forwarding. You want a timeout or destination unreachable, rather than an outright refusal.
But... I looked in the manual for your router (seems to be a VoIP+modem+router combo) and unfortunately I couldn't find any way to add a static route, nor did I find a way to block or forward requests specifically for Google DNS.
So unless the ability to add static routes or the ability to block port requests for specific WAN destinations has been added, you may be a bit stuck. Definitely check through your router's config to see though, often times the manual lags far behind the current feature set.
However, if you don't have the necessary options in your router, that leaves you with these possibilities:
Add a router that can provide blocking or redirection via one of
static routes
IP-specific port-blocking
iptables rules
to provide network to Chromecast and devices controlling Chromecast (they need to be on the same subnet).
VPN - which is beyond my area of expertise for this usage.
Get a rooted Chromecast so you can use Eureka-ROM to enable use of DHCP-supplied DNS rather than Google DNS
If you go with option (a), you will have double-NAT, which can be problematic.
You would connect the new (filtering) router's WAN side to your existing router's LAN site. You cannot connect the two routers LAN-LAN as the new router will only filter/redirect traffic when it does the IP translation from LAN to WAN.
If your existing router has a Bridge option for its LAN connection, that would avoid double-NAT (bridge will connect the WAN side to LAN side transparently and disable all router NAT and filtering), but it's more likely that you would get a Static Route option before you get a bridge option.
Anyway, contemplate a bit, first check if there's Static Routes in your router's config. Sorry this has been such a verbose post.
bhiga said:
So unless the ability to add static routes or the ability to block port requests for specific WAN destinations has been added, you may be a bit stuck. Definitely check through your router's config to see though, often times the manual lags far behind the current feature set.
Anyway, contemplate a bit, first check if there's Static Routes in your router's config. Sorry this has been such a verbose post.
Click to expand...
Click to collapse
Many thanks for your detailed reply!!
I don't know much about modems/routers so would be a bit wary of setting up a new router. I checked in the setting on the modem/router provided by my ISP and there is an option to add static ip. Would that be a way to block Google's DNS?
slonn said:
Many thanks for your detailed reply!!
I don't know much about modems/routers so would be a bit wary of setting up a new router. I checked in the setting on the modem/router provided by my ISP and there is an option to add static ip. Would that be a way to block Google's DNS?
Click to expand...
Click to collapse
Unfortunately not - and don't change that - you'll lose Internet connection.
While you're there, though, can tell me what options you have in the Working Mode dropdown where it currently says Router Mode?
DON'T change it though - that's likely to break your Internet connection too.
bhiga said:
While you're there, though, can tell me what options you have in the Working Mode dropdown where it currently says Router Mode?
DON'T change it though - that's likely to break your Internet connection too.
Click to expand...
Click to collapse
There's Router Mode and Bridge Only in the dropdown.
slonn said:
There's Router Mode and Bridge Only in the dropdown.
Click to expand...
Click to collapse
Cool. If you decide to get another router, you should be able to switch that dropdown to Bridge Only and connect your existing router's LAN port to the new router's WAN/Internet port, and it should avoid double-NAT-ing.
Essentially your existing router would only be used as a modem (and VoIP, if you're using VoIP), and you'd disable old router's WiFi and do all your DHCP, WiFi, etc on your new router.
As a rule I try (best I can) to avoid Dual Purpose networking devices as I have found they do neither task very good....
Unfortunately ISPs are moving towards these all in one boxes (Modem/Router/WiFi) and it Wreaks havoc on those who have their own networking gear....
Whats worse is they are locking the configs of these devices so that you can't change them easily to get it to do what you want.
bhiga said:
Cool. If you decide to get another router, you should be able to switch that dropdown to Bridge Only and connect your existing router's LAN port to the new router's WAN/Internet port, and it should avoid double-NAT-ing.
Essentially your existing router would only be used as a modem (and VoIP, if you're using VoIP), and you'd disable old router's WiFi and do all your DHCP, WiFi, etc on your new router.
Click to expand...
Click to collapse
Sounds too simple to be true. I do have an extra router so perhaps I'll test it out at some stage during the week. Thanks for your help so far!
slonn said:
Sounds too simple to be true. I do have an extra router so perhaps I'll test it out at some stage during the week. Thanks for your help so far!
Click to expand...
Click to collapse
You can also try this simple test without the router to see if it works....
Connect your computer directly to the Modem/Router...
Set the Router to Bridge Only mode and if your PC gets an outside (Public) IP Address then you know it will work with an external Router.
The only issue you might face is sometimes if the ISP provided the Modem they program it not to accept that change without it coming from their side.
I connected a new router (ASUS RT-N56U) to the existing router/modem. The existing was set to Bridge Mode with DHCP off and it can connect to the internet but not cast any show (local or US) to the TV. Not sure what details are needed for you to help me getting it to work. I can cast local Netflix onto my phone and tablet. YouTube videos can cast to TV.
slonn said:
I connected a new router (ASUS RT-N56U) to the existing router/modem. The existing was set to Bridge Mode with DHCP off and it can connect to the internet but not cast any show (local or US) to the TV. Not sure what details are needed for you to help me getting it to work. I can cast local Netflix onto my phone and tablet. YouTube videos can cast to TV.
Click to expand...
Click to collapse
Not totally up on the settings screens for your new router but check to see what IP Address it has under the Internet settings.
Every Router has two IP Addresses, one local (192.168.x.x) and one Public (should be provided by the Modem in bridge mode),
If both are local IPs then your double NATing which will easily break Netflix. If one is a Public IP then check other settings in the new router most notably UPnP and Multicast.
Also ( sorry dumb question follows) but you did make sure to set up the CCast to connect to the NEW router not the old one?
Asphyx said:
Not totally up on the settings screens for your new router but check to see what IP Address it has under the Internet settings.
Every Router has two IP Addresses, one local (192.168.x.x) and one Public (should be provided by the Modem in bridge mode),
If both are local IPs then your double NATing which will easily break Netflix. If one is a Public IP then check other settings in the new router most notably UPnP and Multicast.
Also ( sorry dumb question follows) but you did make sure to set up the CCast to connect to the NEW router not the old one?
Click to expand...
Click to collapse
There are two IP addresses: 192.168.1.2, 192.168.1.254, first one local and the other public. I can't locate UPnP and Multicast in the router.
I made sure to set the Chromecast to the new network. The old one shows but it's not connected to the internet. It's in bridge mode.
slonn said:
There are two IP addresses: 192.168.1.2, 192.168.1.254, first one local and the other public. I can't locate UPnP and Multicast in the router.
I made sure to set the Chromecast to the new network. The old one shows but it's not connected to the internet. It's in bridge mode.
Click to expand...
Click to collapse
As I suspected...Your Double NATing is the problem....Your new Router is not actually breaching the Modem to the Internet.
This modem also has WiFi built in I bet....
The DHCP you shut off probably doesn't apply to anything directly plugged into the Modem. Just the WiFi.
You need to look for a setting that gives you the option of passing a local/internal (192.168.x.x) IP or Outside IP and set it to pass an Outside IP. (this is on the Modem BTW)
If the Router reports any IP that starts off 192.168 for Public then you are not set up correctly.
If you see the option to change from local IP to Outside IP but it is greyed out then your ISP locked it out and they must make the changes on their end.
Call and tell them your Modem is in Bridge mode but doing double NAT translation and you can't breach the Modem with your router.
slonn said:
There are two IP addresses: 192.168.1.2, 192.168.1.254, first one local and the other public. I can't locate UPnP and Multicast in the router.
I made sure to set the Chromecast to the new network. The old one shows but it's not connected to the internet. It's in bridge mode.
Click to expand...
Click to collapse
As @Asphyx said, there's double-NAT going on. This may be a problem, but the core problem at the moment is that new router's WAN and LAN are using the same subnet.
I recommend...
Turn off the WiFi on your old router, if you can.
Look for the stuff Asphyx mentioned.
If you get stuck, call your ISP
Ask them to enable Bridge mode and explain that you're looking for more robust routing and firewall features
Ask if there's a firmware update for your existing modem/router combo to provide this, if there is a different ISP-provided modem/router you can use that has better features, or if they can provide/recommend a modem-only device (if they don't/can't enable Bridge mode)
Ideally, you want to see is your new router getting a WAN address that is not 192.168.x.x
If you reach that point, you're done.
If not, you at least want your new router getting a WAN address that is in a different subnet from its local network.
On your new router, change the Local address to 192.168.2.2
That will switch things on the new router to the 192.168.2.x subnet. Now the new router and old router will be on different subnets.
Make sure any client devices (wired or wireless) that have static IPs set are changed to use IP 192.168.2.something and gateway 192.168.2.2
My network is double-NAT and I have not had issues with Chromecast, streaming, VPN, or anything else, but you definitely should avoid double-NAT whenever possible.
Sometimes when I lose connection and I try to reconnect, both my chromecast would show up in the Wireless Network Connection list of SSIDs. Why does that happen sometime? Whenever this happens and someone in the neighborhood happens to see it and clicks on it, can they connect to my internet?
siratfus said:
Sometimes when I lose connection and I try to reconnect, both my chromecast would show up in the Wireless Network Connection list of SSIDs. Why does that happen sometime? Whenever this happens and someone in the neighborhood happens to see it and clicks on it, can they connect to my internet?
Click to expand...
Click to collapse
This is normal behavior and Chromecast will stop broadcasting once it reconnects to your access point.
In Setup mode, Chromecast becomes an Access Point so the Chromecast app can connect to it and set the connection parameters for it to connect to your Access Point.
Since it is an unsecured AP, anyone can connect (and it supports multiple clients). However, whoever connects does not have access to your network or your Internet connection. They are connecting to that Chromecast and that Chromecast alone.
Worst-case scenario* is that someone configures your Chromecast to connect to their WiFi/WLAN and plays videos on your TV. They still won't have access to your network or your Internet connection, and since you still have the device, getting it back is as simple as doing a factory reset via the button (this clears the settings - it doesn't change the firmware/ROM).
* Rooted Chromecasts running Eureka-ROM v1.1 or earlier can potentially expose your WiFi credentials. This will be fixed in an upcoming Eureka-ROM update (and one is scheduled for very soon). To reduce the risk of attack, disable ADB, Telnet and SSH access in the web panel, and if you are going to turn off your WiFi, unplug your Chromecasts too.
Note that the core insecurity is Google's design, not Team Eureka's. So Team Eureka is actually working to add some security over Google's lack of security there. It's kind of like leaving your door unlocked and relying on the fact that your driveway is unmarked and difficult to spot... The added features of Eureka-ROM just make the driveway easier to spot, but that isn't an excuse for not locking your door.
bhiga said:
This is normal behavior and Chromecast will stop broadcasting once it reconnects to your access point.
In Setup mode, Chromecast becomes an Access Point so the Chromecast app can connect to it and set the connection parameters for it to connect to your Access Point.
Since it is an unsecured AP, anyone can connect (and it supports multiple clients). However, whoever connects does not have access to your network or your Internet connection. They are connecting to that Chromecast and that Chromecast alone.
Worst-case scenario* is that someone configures your Chromecast to connect to their WiFi/WLAN and plays videos on your TV. They still won't have access to your network or your Internet connection, and since you still have the device, getting it back is as simple as doing a factory reset via the button (this clears the settings - it doesn't change the firmware/ROM).
* Rooted Chromecasts running Eureka-ROM v1.1 or earlier can potentially expose your WiFi credentials. This will be fixed in an upcoming Eureka-ROM update (and one is scheduled for very soon). To reduce the risk of attack, disable/b] ADB, Telnet and SSH access in the web panel, and if you are going to turn off your WiFi, unplug your Chromecasts too.
Note that the core insecurity is Google's design, not Team Eureka's. So Team Eureka is actually working to add some security over Google's lack of security there. It's kind of like leaving your door unlocked and relying on the fact that your driveway is unmarked and difficult to spot... The added features of Eureka-ROM just make the driveway easier to spot, but that isn't an excuse for not locking your door.
Click to expand...
Click to collapse
Wow! Thanks BHIGA! That was very informative.
I have a Chromecast that will not make a connection to WiFi. You can see it on the network, but when going through the final steps I am told that it cannot communicate with the Chromecast and it times out. Can anyone provide some suggestions?
I am using modem for business class.
You may have tried this already, but did you try power cycling the modem?
Yes, tried everything!
is it possible to turn off AP isolation?
Something that may or may not apply to your situation but should be noted...
Comcast is currently (in some areas) running two Wireless Networks off the router they give you for your home service.
One is for their Public WiFi use (which I believe requires a Comcast login)
and the other for your own local network use.
Is it possible that you are trying to connect to the public SSID and not the local?
Do you see two different SSIDs available?
Otherwise the best suggestion is to call Comcast and let them walk you through it.
I personally never allow my ISP to control my wireless or router and insist they put their equipment into Bridge mode.
If you are having problems just connecting I can't imagine what kind of other issues you are going to face with settings needed for a good CCast experience.
Asphyx said:
One is for their Public WiFi use (which I believe requires a Comcast login)
and the other for your own local network use.
Click to expand...
Click to collapse
This explains the numerous open xfinitywifi APs I've been seeing lately... Glad I have my own modem.
bhiga said:
This explains the numerous open xfinitywifi APs I've been seeing lately... Glad I have my own modem.
Click to expand...
Click to collapse
Yes and also glad I have my own router with it's own security system so that the Modem the public might be connecting to can't possibly make a connection to the local network without a proper router priv.
One of the reasons why I always suggest people do not use the ISP router as their own and insist the ISP put it into Bridge mode so the only way anyone can possibly get a local IP is by going through my routers own security.
I have the xfinitywifi disabled on mine and changed a majority of the default settings.
death2all110 said:
I have the xfinitywifi disabled on mine and changed a majority of the default settings.
Click to expand...
Click to collapse
Anything related to...
AP Isolation (should be off)
Multicast (needs to allow multicast, but the on/off state depends on the exact setting)
IGMP (depends on the exact setting)
?
I'm not having any issues... but I did find this:
I couldnt really find anything regarding AP Isolation, But I know by default ICMP and Multicast are blocked. Theses need unchecked.
Gateway>Firewall>Custom Security
Uncheck 'Block ICMP' and Uncheck 'Block Multicast'
Edit: Setting the firewall to Low Security will also enable ICMP and Multicast
dpalmer76, is your comcast biz router a DPC3939? Its 'Incompatible'...
http://forums.businesshelp.comcast....omecast-with-Cisco-DPC3939B-Router/td-p/17168
death2all110 said:
I have the xfinitywifi disabled on mine and changed a majority of the default settings.
Click to expand...
Click to collapse
They let you into the Admin or did you just find your own way in?
Asphyx said:
They let you into the Admin or did you just find your own way in?
Click to expand...
Click to collapse
Comcast routers have a user accessible admin panel. They have the info for logging in on their site.
death2all110 said:
Comcast routers have a user accessible admin panel. They have the info for logging in on their site.
Click to expand...
Click to collapse
I'm actually shocked! LOL
Thank Thad
Here's how I got mine Chromecast to work after getting the "cannot communicate with Chromecast" error on the final step of setup:
Called Thad with Xfinity Customer Service, and he found a fix. Tell your support agent to
Factory reset the modem
Set security of the modem to WPA2AES
Enable UPnP and set the time to 30
Set hops (scale of 1 to 5) to 5
Enable Zero config
After resetting your Chromecast and going through setup, it should begin to work.
Chromecast
So you don't need to even call comcast for this and it'll save you time because they really just don't know.
Go to 10.1.10.1/ on your browser. The User is : Cusadmin and the pass word is: Highspeed. It may change on your region but comcast will give you that info.
On the left menu Click advanced, then under device discovery on the left you will find all the settings you need.
as twill said UPnP enabled. Advertisement period set to 30. Time to live/ hops 5 and zero config enabled
I already use Chromecast at home and know how this little piece of awesomeness work, what I need is to use it inside my work LAN, so here is the problem: We have 802.1X auth to our main SSID and a Web-based auth page to connect guest users. We use Cisco WLAN devices to do so along with Active Directory and etc. I also have other 2 ssid's inside my Cisco AP's despite of being said that I should use only 3 SSID's on a 2,4GHz AP and as Chromecast needs multicast we decided to drop the possibility to use Cisco to make this netowrk, it would be very complicated to do a simple job.
So after I have been through all of those options we decided to buy and use an simple Access Point (ill be using a DD-WRT enabled router to do so) to make the network for the CC's.
Here is where things got a little bit more complicated, I can use chromecast without a problem if I use it inside this newly created network, but I still need to control it from inside my work network. I have separated my VLANs more and less in this aspect:
0 for fixed IP's 90 for chromecast devices 100 for workstation 200 for servers All of the specified VLAN communicate to each other without a problem
The real purpose is to center some dashboards in a Chrome Browser in a Windows VM and show them in 10 different TV's in our environment (it is a mine, so it is very large territorial company).
But the key is that I don't want the workstations to be able to cast to the chromecast, in fact I'll be using only one virtual machine to control all of the Chromecasts, do you guys have any idea how can I do that?
http://www.reddit.com/r/Chromecast/comments/35v3le/connect_chromecast_to_specific_vlan_inside_my/
To block other clients on the network from seeing Chromecast you'll have to block its discovery protocol(s). It uses mDNS mainly now. You'll should be able to see it via Bonjour Browser or similar.