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.
Have you tried using an IP address or a specific name to reach the router? DNS problems usually affect both Wi-Fi and Ethernet, so that's unlikely here. If something is wrong with the ethernet connection, you should see messages in Event Viewer. A blank slot on your computer could mean a cheap PCIe ethernet card was added, but I don't think just one site breaking while others work well points to hardware failure alone.
I used the internal IP address 192.168.0.1. I checked Event Viewer and saw two errors: one from DHCPv6-Client about losing the lease to my IP, and another from NetBT saying the driver device couldn't be created because initialization failed. Both of these happened before the power outage and I didn't have connection problems at that time. Then I looked at other logs and found a lot of warnings from DNS Client Service saying it timed out getting names for many addresses like firebase, steam, microsoft sites, dns.google, and a few more. That tells me it is definitely a DNS problem for Windows. Later I also saw errors from DHCP-Client about "Nack" being received on interface 4, which wasn't there before the power outage or in my kernel log after the unexpected shutdown. Since my motherboard is a Mini-ITX, there are no empty PCIe slots left to test. If the problem really is with my NIC, I'll have to use a USB adapter until I get a new one. Honestly, I am really confused by all of this; nothing makes sense and I ran out of ideas on what else to try, even though I got a working solution for now, even if it isn't the perfect one I wanted.
I looked into this Nack message a little bit and saw some forums where people said it might cause DNS problems. Turns out it's just telling my computer that the DHCP server (which is actually my modem) isn't giving me an IP address yet, and there seems to be a NIC-modem issue here. This matches what I found when testing things too. Also, someone mentioned this could happen because of a change in the MAC address. Since the MAC address can live in the flash memory of my network card and getting power out might damage that flash, it makes some sense. It feels like a good idea so far, so I'll try resetting the DHCP server to forget my old connection, hoping that will fix my problem.
I'm not sure why DHCP isn't working well for me. First, I'll try turning off IPv6 on the network interface. This can cause some weird problems on its own anyway. The best way to test if there are any issues is to set a fixed IP address in your IPv4 settings for that nic (network card). You technically need to give an IP outside of what your router usually gives out, but something like 192.168.0.250 usually works better than trying the default ones. You want to make sure you aren't assigning the same IP address to two different devices in your house. Generally speaking, NACK means the computer is trying to reuse an old IP, and the router says no because that IP isn't available anymore. When this happens normally on a PC, it just releases that old IP and asks for a brand-new one instead.