No, can't reach those services right now after the power went out?
No, can't reach those services right now after the power went out?
The network interface is pretty simple. It doesn't really get what websites are about. In fact, it's so basic that it even doesn't know what an IP address means. It just works by using MAC addresses, while software inside the operating system handles everything else. Sometimes problems with a ethernet port happen because of packet loss, which makes things work slower on all sites. It's strange how this affects different OSs like Ubuntu. Windows can be very dumb sometimes and decide that you're now connected to a public network. That causes it to set higher firewall rules so some stuff stops working. Another common thing that causes this is IPv6. I'm not sure why something would suddenly start happening, but I'll try turning off IPv6 in the network settings and see if that fixes things.
I know NICs only handle packets and addresses, but other devices are fine. Neither of my computers has issues before either. But Windows thought a new network appeared and I got worried. On fixing things: IPv6 was turned off, then back on again. The problem still came back. Turned off the firewall too, nothing worked. Restarted with those same settings, problems stayed and did not change anything. Did the exact same thing on Ubuntu, no fix there either. What stood out is that some apps like Steam, Discord, and websites don't work on both systems, but Telegram works on Ubuntu but not Windows.
I am not sure what the main difference between Steam or Discord is, since they don't use the same ports as HTML/HTML files. This doesn't explain why some websites might just stop working. Is this happening to all of them or only sometimes? You can check for this manually with commands like nslookup and ping. I should try running nslookup using both my default DNS and forcing it to use 1.1.1.1 or 8.8.8.8. Maybe the IP addresses they resolve to are different. You could also try pinging these IPs separately. It would be very strange if you were able to look up an IP with nslookup but then your browser failed when trying to ping it.
The websites and services are all broken, so I can't get into them at all. But Windows doesn't always tell me that the connection is failing. I also can't reach the internet on my own modem from my PC. So, I tried a few more tests: even with my wife's computer plugged in, nothing worked. Then I pulled out an old USB WiFi adapter and tested it, and everything actually turned up fine. That makes me think the problem is inside my network card or something like that. It feels weird to me though because when I'm cabled into the modem, I can get some sites working, but I still can't even check the modem's settings page.