NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
CM2200 on 192.168.100.1
I just bought a CM1100 and am extremely annoyed to find that its IP address is fixed at 192.168.100.1. The network I am installing it on uses the 192.168.2.xxx subnet, which means that the cable mod...
> [...] I want to have the same capability with the CM2200. Quite
> simple, actually.
Yes, it is. Make a new bookmark for "192.168.100.1". When you use
that (special) address in your web browser, your (unspecified) "a
Linksys WAP/router" will see that address, notice that it's not on its
own LAN, and send it off toward your ISP. That is, to the CM1100, which
will intercept it, and respond appropriately. There's no need to do
anything different/special on your ("192.168.2.*") LAN to make that
work.
> [...] I have even (gasp!) downloaded the manuals for the new boxes.
> [...]
Did you see anything in any of them which suggested (let alone
demanded) that you "reconfigure [your] network to 1.92.168.100.xxx !"?
> [...] I do enough to get by and then I stop.
That's fine, if you know where "enough" ends.
> Don't go looking for trouble where there is none?
Still my advice.
"Make a new bookmark for "192.168.100.1". When you use
that (special) address in your web browser, your (unspecified) "a
Linksys WAP/router" will see that address, notice that it's not on its
own LAN, and send it off toward your ISP. That is, to the CM1100, which
will intercept it, and respond appropriately. There's no need to do
anything different/special on your ("192.168.2.*") LAN to make that
work."
Thanks. That's exactly what I was looking for. It would have been nice to get it without the snotty attitude, but I'll take it either way. Since that is an unroutable IP I'm surprised the tip works. I would have expected the Linksys to refuse to forward it, but apparently not -- assuming you have actually made/seen this work.
> [...] I would have expected [...]
Exactly. Hence:
> It does? Did you actually try it, or are you basing your complaint
> on how you expect this stuff to work? What, exactly, did you do?
In the words of the philosopher Williams, "If you don't think too
good, don't think too much."> [...] the Linksys to refuse to forward it, but apparently not -
I'd expect that your ISP would "refuse to forward it", if that's any
consolation.> [...] assuming you have actually made/seen this work.
Everyone who owns a cable modem has (or could have) seen this work.
> [...] It would have been nice to get it without the snotty attitude,
> but I'll take it either way. [...]
Fix your own attitude, and that of others may follow, with no extra
effort on anyone's part. Screaming about all "this stupidity" which
you're being forced to endure, rather than _asking_ about how the simple
procedures in the various User Manuals could possibly work, for example,
might have been a better start. Just a thought.Deciding whether the original problem involved "stupidity" someplace,
or just a smattering of ignorance (which is normally a simpler obstacle
to overcome), is left as an exercise for the reader."192.168.100.1 is a fixed address for a reason and can not be changed. Its the address of the modems web page for user access."
In all hardware I have set up except this box, my experience is that the port 80 access address is easy to change. For example, I have set my DSL box (that I am now changing out) to use 192.168.2.251. I just set the LinkSys WAP/router that is replacing it to also use 192.168.2.251, replacing the 192.168.1.1 default. My two NAS boxes use 192.168.2.223 and 224, hard addresses that I have set. IIRC they defaulted to DHCP.
> In all hardware I have set up except this box, my experience is that
> the port 80 access address is easy to change. [...]Welcome to the world of the DOCSIS cable modem.
> [...] My two NAS boxes use 192.168.2.223 and 224, hard addresses that
> I have set. IIRC they defaulted to DHCP.Almost everything these days defaults to using DHCP. When you say
"hard address", do you mean a static address (configured on the device
itself), and not a reserved dynamic address (configured on the (DHCP
server on the) router)? If you're using static addresses, then my
advice would be to shrink the DHCP pool, so that the router is never
tempted to grant any of your static addresses to some DHCP client
device.You could, for example, change the DHCP pool from its (likely)
default range of ".2" - ".254" to, say, ".2" - ".199". You could then
safely use ".200" - "254" in any way you want, without fear of the DHCP
server causing a conflict.
Around here, almost all my devices have static or reserved addresses,
all outside the DHCP pool. (Static for the antique computers which
don't handle DHCP well, if at all; reserved for almost everything else.
My DHCP pool is only 16 wide. A Roku box uses it.)