Cable modem status page (ntl 250)

Mat-d-rat · 20-03-2007, 15:56

Ok, so the status page for this modem (replacement for 3com cmx) is 192.168.100.1 which I can see with a direct connection. However once connected to my router (Buffalo Airstation) although everything works I can't get to the status page any more. My home network is on 192.168.0.* with a mask of 255.255.255.0, so I changed the mask to 255.255.0.0 (on my pc and router) but I still can't see it. Any ideas?

Deathmaker · 20-03-2007, 16:52

What browser are you using to access the modem and do you have a manual proxy specified?

I ask as I can't access my modem or router with Firefox if I'm going through one of VM's proxies but can if I directly connect to the 'net. :S

AbyssUnderground · 20-03-2007, 21:19

Quote:

Originally Posted by Deathmaker

What browser are you using to access the modem and do you have a manual proxy specified?

I ask as I can't access my modem or router with Firefox if I'm going through one of VM's proxies but can if I directly connect to the 'net. :S

Thats normal since the modem is local to you when you're directly connecting to the internet but if you're not then its not local to you anymore.

Mat-d-rat · 20-03-2007, 23:27

No proxy, and used IE6 (old pc) direct link and could see status page. Can you change the Ip of the cable modem?

stormrider · 09-05-2007, 15:46

Happened across this thread while looking for the cable modem status page address and there doesn't appear to any answer to Mat-d-rat's question.

A router basically separates your network into your LAN - your PC (or PCs), and WAN - cable modem and rest of the world.
Now, anything on your LAN is addressed and routed using 192.168.x.x. Everything else is routed onto the WAN.
So basically your router doesn't send requests for 192.168.100.1 to the cable modem.

Now the tricky part. If you want to talk to the modem you have to tell the router to route any requests to 192.168.100.1 to the WAN side. Since I have no idea how your router configuration works, you're on your own there.
On my D-link, it was a matter of setting up a custom routing rule for ip address 192.168.100.1 with a subnet mask of 255.255.255.255 (ie only route this SINGLE address).

As for Deathmakers problem, you just need to add 192.168.0.0/16 to the exceptions list ("No proxy for:") in the network configuration of firefox