![]() |
Accessing the config page
Hi All,
I have used VM for the past two years at two addresses (20mb Ambits), and at both I have had the same problem - as soon as I connect the supplied Netgear router, I can no longer access the modem config page. Internet access and such remains fine. When I connect a system directly to the modem, I can once again view the page at http://192.168.100.1. This is the case with the Netgear at complete factory settings. Anyone got any ideas? Thanks. |
Re: Accessing the config page
It's because the modem is acting in bridged mode
you'll probably find that if you disconnect the coax, you'll still be able to log into the modem from behind your router. the question really is - Why would you want to log into your modem in the first place? |
Re: Accessing the config page
Then how do other people access it from behind their routers?
Taking the coax out would defeat the purpose - I wish to monitor signal levels. Can't really do that without a coax! |
Re: Accessing the config page
What are you using for the IP range on your LAN? (drop to a command promt, type "ipconfig"(no quotes), tell us what you get for ip address, subnet mask and default gateway.
When you request the modem's diagnostics/config page, the bridge sniffs it's own address and rather than passing them on to the UBR it responds itself. So for some reason i think your likely to have an IP range conflict, the cable modem doesn't seem to be receiving the request for http://192.168.100.1 ..................Standing by to be corrected by Broadbandings though! |
Re: Accessing the config page
Nothing to correct Jon!
|
Re: Accessing the config page
Quote:
|
Re: Accessing the config page
Currently in the 192.168.2.x range - with devices littered all over it.
Nothing running in .1.x; Quote:
Quote:
|
Re: Accessing the config page
Your using a 255.255.0.0 subnet, this is going to stop the 192.168.100.1 request being passed through to the router.
Basically by using a 255.255.0.0 subnet, your telling the router that the first two octets of the IP address intentify the network, and the last two describe hosts on your network. In your case, when you call up 192.168.100.1, your router is not passing the request on to it's WAN port because it thinks the device is on the LAN side of your network. |
Re: Accessing the config page
For peets sake, can't believe I didn't spot that - even after staring at the routing table for an hour!
Cheers Jon |
| All times are GMT. The time now is 17:49. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2026, vBulletin Solutions Inc.
All Posts and Content are © Cable Forum