NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
WNDR4300v2 and Chromecast
Anyone else having issues with Chomecast and the v2 version of this router? All Chromecast compatible apps are missing the cast button until I reboot the Chromecast. It stays functional for about 5 m...
@minions08 wrote:
Chromecast are the one releasing list of devices which are compatible with their device. So far it is still not compatible with WNDR4300v2.This information is incorrect. Not to be that guy if you are going to give users misleading information on the forums please attempt to back it up.
Now onto the problem. I did a Wireshark trace and I noticed the router is not transmitting the multicast packets sent by the chromecast. This problem is entirely on Netgear and so far they have neglected this router. Its been out for almost a year and is still on its inital firmware release that contains vulnerabilites. To top that off my Nest doesnt work correctly with this router as well. the heartbeats are not making it to Nest servers and its contantly offline but is pingable from inside the network. Netgear is just passing the buck onto Nest.
I have been able to fix the Chromecast issue by tinkering on my own.apply the following setting. FIX: Uncheck "disable IGMP Proxy".
Netgear support was never able to fix this and the supposed engineers offered zero solutions. I dont think I'll ever buy another Netgear product again based off what I experienced with this company. The hours of phone calls and promises to contact me that were never met... I do hope the fix that I found works for the unfortunate people like myself who purchased this router.
Chromecast are the one releasing list of devices which are compatible with their device. So far it is still not compatible with WNDR4300v2.
@minions08 wrote:
Chromecast are the one releasing list of devices which are compatible with their device. So far it is still not compatible with WNDR4300v2.
This information is incorrect. Not to be that guy if you are going to give users misleading information on the forums please attempt to back it up.
Now onto the problem. I did a Wireshark trace and I noticed the router is not transmitting the multicast packets sent by the chromecast. This problem is entirely on Netgear and so far they have neglected this router. Its been out for almost a year and is still on its inital firmware release that contains vulnerabilites. To top that off my Nest doesnt work correctly with this router as well. the heartbeats are not making it to Nest servers and its contantly offline but is pingable from inside the network. Netgear is just passing the buck onto Nest.
I have been able to fix the Chromecast issue by tinkering on my own.apply the following setting. FIX: Uncheck "disable IGMP Proxy".
Netgear support was never able to fix this and the supposed engineers offered zero solutions. I dont think I'll ever buy another Netgear product again based off what I experienced with this company. The hours of phone calls and promises to contact me that were never met... I do hope the fix that I found works for the unfortunate people like myself who purchased this router.
The information I have provided is correct based on the KB article from NETGEAR which I have posted in the 1st page. On the said KB article there is a note stating "Information on this article came from a Google Chromecast help page". If you happen to make it work for your router then this would be helpful to other users and also for Chromecast as not all routers and other brands works with their units based on their page. Chromecast can include your workaround as they have provided workarounds for other routers/brands.
http://kb.netgear.com/app/answers/detail/a_id/24510/~/chromecast-netgear-router-compatibility
https://support.google.com/chromecast/table/6207416?hl=en
@minions08 wrote:The information I have provided is correct based on the KB article from NETGEAR which I have posted in the 1st page. On the said KB article there is a note stating "Information on this article came from a Google Chromecast help page". If you happen to make it work for your router then this would be helpful to other users and also for Chromecast as not all routers and other brands works with their units based on their page. Chromecast can include your workaround as they have provided workarounds for other routers/brands.
http://kb.netgear.com/app/answers/detail/a_id/24510/~/chromecast-netgear-router-compatibility
https://support.google.com/chromecast/table/6207416?hl=en
Again, you are incorrect and have not provided any information that proves otherwise. Networking 101 would tell you that unless the devices were sending malformed packets that its on the router side when it comes to what data traverses beyond it. Wireshark didnt reveal any error frames and the threeway handshakes revealed nothing. There was a broadcast sent and the router dropped it. There is no specific programming for models of routers contained in a device like Chromecast. It conforms to 802.11 and that pretty much it. Not to be that guy but you keep being adament that your are correct as your community reputation is at stake. I can understand that but your knowledge in this particular area is rudimentary.
Also if this was truely the case that it was on Google then why does it work fine with the WNDR4000? It should not work as its not on the compatible list. Why does Google refer you back to Netgear?
Futhermore Netgear has finally released firmware 1.0.0.32. Fixes include SOAP security issue, KCode NetUSB security vulnerability issue. Ive tested this firmware and can confirm there have been additional undocumented changes that resolved both Chromecast and Nest issues for this router.
srsbsns I apologize for any inconvenience this may have caused you.
We at NETGEAR strive to provide the best service possible for our customers.
For the vulnerability, here's a link of our statement when it comes to the ReadySHARE vulnerability.
Regarding the Nest, which Nest device do you have?
How is the Nest connected to the router? Wired or wireless? Which signal you're connecting it to (2.4Ghz or 5Ghz)?Again, I apologize for any inconvenience.
ElaineM wrote:srsbsns I apologize for any inconvenience this may have caused you.
We at NETGEAR strive to provide the best service possible for our customers.
For the vulnerability, here's a link of our statement when it comes to the ReadySHARE vulnerability.
Regarding the Nest, which Nest device do you have?
How is the Nest connected to the router? Wired or wireless? Which signal you're connecting it to (2.4Ghz or 5Ghz)?Again, I apologize for any inconvenience.
Elaine ,
Thank you for the post. Netgear has released a firmware 1.0.0.32 that resolved the security vulernabilites and Chromecast/Nest issues. Can you explain why the link you provided for the ReadySHARE vulnerability says there is no problem with the WNDR4300v2 and no fix is needed yet 2 days ago Netgear posts firmware with a changelog that contains the following bug fix notes? That link has been provided anyone asking about the vulnerabilities saying there is no problem. One could conclude users have been mislead until now. I know you are providing what information you have but somebody has not been telling the whole truth at Netgear.
Bug Fixes
- Fixes the SOAP security issue.
- Fixes the KCode NetUSB security vulnerability issue
