 msmisfit
join:2004-09-13
Lawrenceville, GA
kudos:2 | reply to cork1958
Re: Can't access Zoom modem config page Maybe they are working on the system where you are, and for some reason are disabling that function temporarily as needed? Or maybe just inadvertently testing/making changes that cause customer owned modem accessibility to be inoperative for awhile? |
|
| Has to be what it is, as again this morning, I can not access modem page using any of the links above.
Guess I just ride it out. As long as modem is connecting, I don't really care, but it is irritating not being able to access when I want to!
Thanks folks 
--
The Firefox alternative.
»www.mozilla.org/projects/seamonkey/ |
|
4 edits | Duh!! 
Just figured out my issue with connecting to modem page.
I had forgotten that I had entered static IP addresses in my routers config page for testing purposes a day or 2 before I started having this issue. Changed it back to default and modem page snaps right up!! Since my IP address changed though, I find this address is working best now, »192.168.100.1/rf_index.asp and not the one I used to always use.
Man, I hate those brain fart moments!! 
Thanks to all who replied
Edit:
Jesus petes, that's NOT the issue as I can't use ANY of the links on this page again!! WTH?! 
--
The Firefox alternative.
»www.mozilla.org/projects/seamonkey/ |
|
kruserPremium
join:2002-06-01
Eastern MO | Hey Cork,
Maybe as it is happening so much, try plugging a single computer into the Zoom directly and power cycle the zoom and then keep trying the 192 address for a while and see if it does it. Set the computer to get IP auto.
That would rule out everything else on your network as the culprit other then the modem itself and the computer you use for the test.
If it still does it, it won't tell you if the modem is failing or charter is doing something though but at least you will know it's not any of your other stuff on your network that is causing the problem.
Just a suggestion in case you had not tried this yet. |
|
| reply to cork1958
What IP range are you using on your LAN? If your modem's diagnostic interface falls within that subnet, you're bound to have connection issues with it as the router typically doesn't route LAN traffic through the WAN interface.
I had similar issues in the past and resolved it by changing my LAN IP range so it doesn't include the modem's diagnostic interface. |
|
| @kruser:
Thanks! Hadn't thought of that and will try it tomorrow morning, if I can remember to get on the computer that is closest and easiest to mess with wires.
@passerby:
My LAN's traffic is in the 192.168.1.2 - 192.168.1.113 range, set statically and always has been.
--
The Firefox alternative.
»www.mozilla.org/projects/seamonkey/ |
|
|
|
