Computer Issues

Rezz

Mr. Poopybutthole
4,875
4,280
Shot in the dark, but can you log into the comcast router? If it has persistent logging enabled(since you rebooted it) and see if there was an update pushed by Comcast to it between when you could access the sites and when you couldn't. Or if it rebooted during that same period before you manually rebooted and see if some update that was pushed to it previously was applied.

It's not exactly a common thing to happen, but I've seen similar issues with feature enhancing updates from ISPs that have default settings that don't line up exactly with the client's security layout. Especially at smaller companies that don't have a dedicated IT team so the update may just sit in the queue for months+ before a power blip gets it applied unknowingly to the company itself.

If anything that could help narrow your search. I'm with Neranja tho; it's unlikely that your server settings changed randomly without manual intervention (and especially with you being the only 'computer guy' at the company) it sounds like Comcast is doing something on their end. If you haven't, I would reach out and just explain the problems to them. While I always promote people trying to learn more about computers in this age where everything is becoming a FRU, like you said it isn't your job. Part of your bill from Comcast is going to their support team - it's definitely worth reaching out to them.
 

Void

BAU BAU
<Gold Donor>
10,242
12,514
Shot in the dark, but can you log into the comcast router? If it has persistent logging enabled(since you rebooted it) and see if there was an update pushed by Comcast to it between when you could access the sites and when you couldn't. Or if it rebooted during that same period before you manually rebooted and see if some update that was pushed to it previously was applied.

It's not exactly a common thing to happen, but I've seen similar issues with feature enhancing updates from ISPs that have default settings that don't line up exactly with the client's security layout. Especially at smaller companies that don't have a dedicated IT team so the update may just sit in the queue for months+ before a power blip gets it applied unknowingly to the company itself.

If anything that could help narrow your search. I'm with Neranja tho; it's unlikely that your server settings changed randomly without manual intervention (and especially with you being the only 'computer guy' at the company) it sounds like Comcast is doing something on their end. If you haven't, I would reach out and just explain the problems to them. While I always promote people trying to learn more about computers in this age where everything is becoming a FRU, like you said it isn't your job. Part of your bill from Comcast is going to their support team - it's definitely worth reaching out to them.
Yeah I can log into the router, and have, but I am unsure where I'd find anything about a previous update. I'm happy to poke around in it and look, but I didn't see anything obvious last week when I was looking at it.

Aside from an update doing hidden stuff, is there anything specific that might have changed that I could check? Like a setting suddenly being flipped or something? I just don't know enough about this shit to be confident of randomly trying different settings for fear of screwing everything up somehow.

EDIT: So I just logged in again, and I don't see anything really in the Event Log other than a bunch of WifiRadio Up/Down messages.
In the Firewall Logs I don't see anything that really stands out either, but I do see a bunch of shit like this:

FW.IPv6 INPUT drop , 27640 Attempts, 2025/6/12 02:48:14Firewall Blocked
Should I be concerned about that stuff? I turn off IPv6 on every new computer because they absolutely will not connect to the domain unless I do.

I don't see anything about updates being applied, but maybe I'm not looking in the right place. I'm looking in the logs for the last month, but nothing is jumping out at me.

All Content Filtering is turned off from what I can see as well.
 
Last edited:

Rezz

Mr. Poopybutthole
4,875
4,280
If it's got multiple ports or you don't mind having the network disconnected, you could rule out the router mostly completely by just plugging in a laptop to the router and updating it in the whitelist to get through, and see if it's having the same issues. No issues - if you don't have a bunch of custom rules set up would rule out the router completely and the ISP as well; if you do have custom rules then it could be those rules that are F'n things up (goes back to my idea about an update or something being pushed). If you have the same issue, then you can remove the server from the equation at least to narrow down what you're focusing on leaving router/settings/ISP.

Every router is a little different and I'm not really familiar with the comcast specific ones (been using Netgear and D-Link routers for decades; never do the provided method) but typically you could look at the version and if there's no specific log data about it (usually there's an advanced admin tab and then administrative logs. Usually~) you could see if that update coincides with when you noticed the changes. Many routers when you look at the version will tell you what the date it was updated to was, but yeah not sure if it would be easily viewable.

You should see power events either directly or by inference in the logs (ie, if it doesn't have power/status events enabled/visible, you can look for gaps in traffic that match the time frame in which you rebooted it manually, and see if those gaps line up with the change in accessibility you're noticing).

Also, just look at the logs and see if any admins logged in aside from times you know you were in there. Not everyone at your place may be a computer guy but maybe someone who would know the password/login might have logged in to fix a problem they thought they had and inadvertently pressed the wrong button. Happens a little more than most people think.

As for any specific changes - if you weren't actively administrating it before it's probably pretty hard to determine if anything specifically changed, aside from going through any firewall settings and see if there are some custom rules being applied that might be restricting traffic and then mapping them to the pages you're not able to load on the network. Stuff like "unallow x.x.x.x" etc. in the ACL if it's not setup as a whitelist
 

Void

BAU BAU
<Gold Donor>
10,242
12,514
If it's got multiple ports or you don't mind having the network disconnected, you could rule out the router mostly completely by just plugging in a laptop to the router and updating it in the whitelist to get through, and see if it's having the same issues. No issues - if you don't have a bunch of custom rules set up would rule out the router completely and the ISP as well; if you do have custom rules then it could be those rules that are F'n things up (goes back to my idea about an update or something being pushed). If you have the same issue, then you can remove the server from the equation at least to narrow down what you're focusing on leaving router/settings/ISP.

Every router is a little different and I'm not really familiar with the comcast specific ones (been using Netgear and D-Link routers for decades; never do the provided method) but typically you could look at the version and if there's no specific log data about it (usually there's an advanced admin tab and then administrative logs. Usually~) you could see if that update coincides with when you noticed the changes. Many routers when you look at the version will tell you what the date it was updated to was, but yeah not sure if it would be easily viewable.

You should see power events either directly or by inference in the logs (ie, if it doesn't have power/status events enabled/visible, you can look for gaps in traffic that match the time frame in which you rebooted it manually, and see if those gaps line up with the change in accessibility you're noticing).

Also, just look at the logs and see if any admins logged in aside from times you know you were in there. Not everyone at your place may be a computer guy but maybe someone who would know the password/login might have logged in to fix a problem they thought they had and inadvertently pressed the wrong button. Happens a little more than most people think.

As for any specific changes - if you weren't actively administrating it before it's probably pretty hard to determine if anything specifically changed, aside from going through any firewall settings and see if there are some custom rules being applied that might be restricting traffic and then mapping them to the pages you're not able to load on the network. Stuff like "unallow x.x.x.x" etc. in the ACL if it's not setup as a whitelist
I can see the times I logged into the router and no others. And trust me, it is more likely that everything MFF posts is true than ANYONE here knowing how to log into the router, much less give it commands. This is a blue collar company where they only know the term "IP Address" because I've said that's why the printer isn't working, for example. Anything beyond an Excel file is magic to them, seriously.

I looked up various IP addresses for imgur and tried a traceroute from inside the router troubleshooting section, and they failed. Perhaps those IP addresses are wrong so it isn't really conclusive, but 8.8.8.8 works correctly.

I'll try to call them later if I have time. Thanks for your suggestions, I appreciate it.
 
  • 1Like
Reactions: 1 user

Void

BAU BAU
<Gold Donor>
10,242
12,514
So did I do something while fucking around with the router? Or did the internet just magically heal during that time? Imgur itself is still down, but it is listing an internal over capacity error, which I get even when logging into my computer at home and checking it, but other sites now work like they are supposed to. To answer my own question, I didn't do anything but check logs and settings, so it clearly wasn't anything I did. Perhaps it was just an area-wide Comcast thing after all, but it lasted for well over a week, which doesn't seem possible with all the people that would be affected. But I don't know how it could have just magically cleared up here.

Fucking internet.
 

Rezz

Mr. Poopybutthole
4,875
4,280
All signs point to Comcast~

Could have been a proxy setup like Neranja mentioned, or they had a primary gateway experiencing issues upstream from you and they just got around to restarting it/fixing the issue.

For the ipv6 errors, it's probably nothing to worry about since your firewall blocked them. If you can, I'd just disable ipv6 in the router so it's not eating up cpu cycles to block vs. just dropping them on receipt. Might not be able to because I know some of the vendor specific ones remove the option, but if you can I would.
 
  • 1Like
Reactions: 1 user