It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
avatar
HereForTheBeer: Log on to the modem status page (usually one of the 192.169.xxx.xxx addresses) and watch the status when it's having a period of trouble.
avatar
johnki: Generally, it's 192.168.0.1 . Any other of the addresses (192.168.0.2, 192.168.0.3, etc) are all generally computers on the network.
Or 192.168.1.1.
avatar
CymTyr: Knee, turning your modem on and off won't work.

What you have is a dying modem. To get it to behave until you get a modem replacement, you have to power cycle. You need to shut your pc completely off, and completely unplug the power from the modem for 2 minutes.

Power the modem back on, wait for all the lights to fire up, and then when it's completely on, turn your pc back on.

This is a make-shift fix until the modem gets replaced.
avatar
KneeTheCap: That is a good theory, but..

I have another modem, brand new. It doesn't work either.
Okay, now reading into the thread more you have a router, which would be what's failing. I assumed it was the modem because you had said earlier you didn't have a router.

Switching ether ports will fix the issue if the issue is a bad port. If the router itself is going bad, you will need a new router. FEAR NOT! They are very cheap.
Check the cabling. I had a similar issue last week, and it turned out to be interference caused by all the cables being tangled together. Since untangling them, I've had no issues whatsoever.
It could still be a hardware issue with your modem/router device. Have you tried checking each of the hardware ports? Check also your cables also, like use a spare if you can to determine if there's some damage on it.

My router would reboot after some use and it turns out to be some configuration I had on the firewall that was tripping up the firmware and causing it to crash. If yours started to work fine all of a sudden, then it's probably not a configuration issue though.