Skip to main content

Mine is the SB8200 model. Yesterday I could access the “web manager” through my computer which has a router and a switch in between the modem. I called the support line and he tried to tell me I had to have a computer connected to the modem directly (I don’t think this is true as I did it yesterday, not directly connected). The line went, it might have been me, I get a lousy signal at my house (thanks tmble) 

 

One problem, that seemed not to be an issue yesterday. Is that my home network is 10.0.0.0/24 not the 192.168. I’m not a networking expert, but if it worked yesterday… what changed. I’m not comfortable, that the providers only authorize certain equipment. The “manager” doesn’t let you do anything but view … which is something...but for a device that I own, is much less than I would expect. Especially in this newer model.

 

I hope that my provider doesn’t have too much control over the modem. Because it’s only been “activated/provisioned” a short time, I wonder if they pushed something down. I believe they have more controls over the modem than I do. I know they can reboot and configure...something...which scares me, when I can’t even reboot through the console and I’m assuming it has no ssh capability. I wonder, as I didn’t try and log in till after it was “provisioned’ and they rebooted it. When I did, there was no login as in the manual and here

 

I may try a reset. Hopefully, that would wipe anything they did. If someone understands this better, please let me know, the “manual” is virtually useless.

 

A few thoughts:

The ISP may push firmware, but that should not cause the issues you are seeing. I would reboot the modem manually, then reboot the router. I’m assuming you have an unmanaged switch so you should not need to do anything. There may have been an issue with the router establishing a new connection after the router updated.

Once the reboots are complete, see if it works. If not, I would:

  1. Ping 192.168.100.1 and see if that completes.
  2. If the Ping does not work, try a tracert and see if it goes to your router (probably 192.168.1.1) and then on to 192.168.100.1. Important to see where the traffic is stopping.
  3. If you just can’t get to the modem at all, then connect your PC via ethernet directly to the modem, bypassing everything. Reboot the modem and then the PC to reestablish DHCP addressing. See if you can connect to 192.168.100.1. 

I have an SB8200, connected to a Google router, connected to a pair of switches, which feed wired devices and additional Google routers acting as extenders/access points. From what I’m reading, your setup sounds appropriate and the ISP should not be doing anything to the modem that blocks access to the admin console. The only time I’ve run into an issue was when I tried running Google One VPN on my PC. It doesn’t recognize 192.168.100.1 as actually being within the local network and treats it as an external connection, which doesn’t work. Had to turn off the VPN every time I wanted to access the modem.

Let us know what you find!

 

Terms & ConditionsCookie settings