Its a WRT54GS2 with latest FW, you probably wont recognize my ISP, I'm not in the US..
It's not a matter of BW or capacity, the problem comes from the router itself [just confirmed], and it doesn't matter if I'm using the internet at all, the problem will always show..
BW is 2Mbit up .256 down [yeah, I know it sucks]..
Sounds like the router isn't renewing the DHCP information from the modem after it restarts from a drop.... could be that the modem isn't pickup the new DHCP info from your cable company too.
Try this... after a drop, plug the cable modem directly in to your computer and see if you get net access (leave it powered on, but plug the network cable in)
If you do, then the DHCP release / renew is having issues at the router level.
If you don't have access, request a new modem from your cable company.
What I did last time it happened, was power cycling the modem first, which made no difference, Windows was still detecting a connectivity problem, I then rebooted the router and everything came back online..
By the way if you unplug the network cable from a cable modem and you plug it into a different NIC you MUST power cycle it [this is general law], as it works directly with the MAC address, it won't register the new NIC if you don't power cycle.. I don't know if it's the same with all modems, but that's how this one works [SB5100]..
The DHCP renewing makes a lot of sense, I'm looking for options within the router to see if there's indeed something that is forcing it to be static on detect..