Connected, but no internet access.

A long time ago, during a nasty thunderstorm, a lightning strike fried my integrated network card. Ever since then, LAN port 1 hasn't shown any signs of life. I eventually bought a dedicated network card—plugged everything in, and it worked perfectly fine via LAN port 3. Everything was running smoothly until yesterday.

Then, out of nowhere this past Friday, LAN port 1 on the router suddenly lit up, and for some reason, everything functioned flawlessly. Fast forward to yesterday: I boot up my PC, everything looks fine on the surface, but the browser tells me there's no internet connection. I tried accessing the modem settings via 192.168.5.1, but I can't even get in—it just keeps giving me a "timed out" error. Oddly enough, the Wi-Fi is working perfectly fine.

I've exhausted every possible troubleshooting step I could find online, and nothing has helped. I even went as far as performing a system restore to a point from two weeks ago, but still, nothing. I called Comcast, and they're insisting the issue isn't on their end. What do you all think?

Justin Harris75 said:What are your thoughts on this?

Open the Run dialog (Win + R)
type "cmd"
then type ping 192.168.5.1
If packet loss is 0, the issue is on their end. If not, the problem is definitely with your setup.

ruggedpanther2 said:Open the Run dialog (Win + R)
type "cmd"
then type ping 192.168.5.1
If packet loss is zero, the fault lies with them—not you. If not, look at your own setup.

I did. Initially, I was getting "Request timed out." But then it shifted to this
"Jay-Z: Sent=4, Received=0, Lost=4 (100% loss)

Justin Harris75 said:Yeah. At first, I was just getting "Request timed out." But then this popped up:
"Jay-Z: Sent=4, Received=0, Lost=4 (100% loss)

What’s your computer's IP address?
Are you running on DHCP, or did you set it manually?

If your router is sitting at 192.168.5.1, your machine needs to be on that same subnet—meaning it should have a 192.168.5.x address with a 255.255.255.0 mask.
Obviously, your specific address can't be the exact same as the router's. (Which, let's be real, it probably isn't.)

Also, your default gateway has to point back to the router at 192.168.5.1.

This thread can be considered resolved/closed. It turns out the router was simply malfunctioning.

Justin Harris75 said:We can consider this thread closed. Turns out my router was just acting up.

Thanks for the heads-up.