NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Add a trusted device
Hi. I have a CG3000Dv2. My mobile phone is listed as a trusted device when I look at the MAC filtering tab. The phone says it's connected to my wifi...but it is not able to load webpages. This just happened. I also have a network extender for my mobile phone. How can I add the network extender to the list of trusted devices? I have its MAC address, but the Netgear router is somehow blocking it, I believe. Thank you. DaleFactory Default Reset is MESSED UP on N450 CG3000Dv2
I was using my N450 with Time Warner, then switched so I decided to sell it. I tried resetting it to factory default, but when it finished, the result was a completely different SSID than the one printed on the side, and of course the pass key didn't work. The sticker on the side says the factory default ssid should be D3DA66, with password (key) 3HW143WE019AE (same as the serial #). But after repeated attempts at resetting it (including holding it down for 30 seconds with no power and then for 30 more seconds after plugging it in), it keeps going to ssid CG3000DV260. anyone... know why it's doing this? how to get it to return to the settings printed on the side? a default password key for ssid CG3000DV260, if one exists? i'd be happy with an answer to any of the questions above.Comcast customers: will Firmware V3.01.14 fix my N450 (CG3000Dv2) connectivity issues?
For the past half a year, my N450 (CG3000Dv2) cabel modem router has been completely unreliable. It regularly drops connection. Sometimes restarting helps, sometimes it doesn't. I've rebooted the box a couple times, and that helps for maybe a day, sometimes less. This connectivity issue seems to be a common complaint for N450, and also seems to be tied to the V3.01.06 firmware (makes sense to me, based on when my problems started). I see that V3.01.14 has been pushed by Comcast to its customers. Any Comcast N450 customers on here who had connectivity issues with V3.01.06? And if so, did those problems go away with V3.01.14? I have Spectrum, which is still using V3.01.06. It's really frustrating to be experiencing this problem, especially since I had suffered through the same issue over a year ago. That time, the probably spontaneously resolved, presumably when the Firmware was updated. I think it happened around the same time as the Time Warner Cable merger with Charter, and this time the problem seems to correspond with the mergers with Spectrum.