NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
I bought CAX30 from Costco 3 days ago and it is giving me nightmare.
I probably replying old tread but I am facing same issues.
I bought CAX30 from Costco 3 days ago and it is giving me nightmare. I recently upgraded my internet service that needs DOCSIS 3.1 so ...
What Ip address range did you set. I use 192.168.0.100 to .150 range.
What browser are you using?
For a printer, why not set a static IP address ON the printer that's out side of the above range. I do that for my 3 printers I have.
I set 192.168.1.2 to 40 range. Does your CAX30 allow you to set IPs in 100 to 150 range? I changed as you described but no luck.
I use Firefox, Chrome, MS Edge, MS Edge Beta on macOS and Windows. Safari and Chrome on iOS and iPadOS.
There is no option to set a static IP address on my entry level HP Wireless Printer. Although it is possible to do for printer, I had been manually assigning IP addresses to my devices on Netgear routers that I owned in the past including C3000, and C7000v2. I wish I can do this on CAX30.
I don't have a CAX30 however my CAX80 does. This is the range I always set and using on any modem or router I use.
Had you tried a factory reset and setup from scratch and immediately go in and set 192.168.0.1 then set the IP address range to .100 to .200 apply and let the modem reboot. Then power ON the printer and let it connect, then set a IP address reservation for the printer. Save the setting then select the APPLY button after saving the setting. There should be a long pause or the modem might reboot. After the modem is back to ready, check the IP address on the printer. Try a reboot of the printer. It should have the reserved IP address.
Yes, I did. And I got the replacement from Costco and new CAX30 (I updated with firmware 1.4.10.10) does same.
I lost hope. Switched back to C7000v2 and everything runs fine.
In the future, if someone find a way to fix CAX30 or Netgear provided new firmware that resolve the issue, please comment.
I'll pass this on to NG for review.