Question Internet breaks whenever power suddenly shuts off ?

[nimbosa]

Earlier this year I built my first PC. At some point while setting up my cables I accidentally unplugged the power and when I booted it back up I could not get through to the internet. I could connect to WiFi, but only locally, with a "No internet" message. Every other device in my house worked just fine on that network. Nothing I tried worked and I ended up reinstalling Windows, which fixed the problem.

A while later the power went out during a storm and when I booted the PC back up I was having the same issue. Again nothing I've tried has worked. I really don't want to have to go through reinstalling Windows and all my software again and again every time this happens. I'm considering buying a UPS since I don't have this issue when restarting or shutting down normally, but I really want to know why this is happening and if there's an easier fix.

My specs:
Modem: Can't find a model number anywhere, but it's Google Fiber
Router: Google WiFi Model GJ2CQ
MOBO: MSI PRO Z690-A WiFi DDR4 ProSeries
PSU: Thermaltake Toughpower GF1 850W 80+ Gold
CPU: Intel Core i5-13400F
OS: Windows 10 Pro N
Intel(R) Wi-Fi 6E AX211 160MHz - version 22.180.0.4u

Connected devices are my phone, Switch, Roku TV, printer, and most recently a work laptop, which I got after the PC started having trouble and which connected to the network with no issue.

Solutions I've already tried:

• Using ethernet
• Connecting to my phone's mobile hotspot (same connected but no internet problem)
• Resetting modem and router
• Network troubleshooter
• Reinstalling WiFi drivers from the disk that came with my motherboard
• Reinstalling WiFi drivers from Intel's website
• ipconfig /release
• ipconfig /renew
• ipconfig /flushdns

And probably some more stuff I can't remember at the moment.

 

[lordmogul]

I have one machine with about a 50/50 chance to not find my network on boot. My workaround was to just disable and enable the network adapter on login.

And recently I had the issue that one VM couldn't connect to the internet, but worked fine connecting to other VMs and local machines. In that case I fixed it by setting a different DNS (try google or cloudflare)

(...)
I'm considering a UPS since I don't have this issue when restarting or shutting down normally, but I really want to know why this is happening and if there's an easier fix.
(...)

That sounds more like something isn't properly shutting down and somehow gets stuck when the system boots back up.
Might be interesting if there is anytihng in windows event viewer that could give a hint.

 

[bill001g]

I would be suspect of something like a windows firewall issue or some other software thing. It is unlikely you get both wifi and ethernet interfaces actually broken.

Did you check the IP addresses you had with the IPCONFIG command or did you just reset them. Do actually get IP addresses from the router and can you ping the router IP.
Does it work to set a fixed IP address if it does not get IP from the router.

If you get IP from the router via dhcp then it means the very basic communications function is working and something else is blocking the traffic.

 

[nimbosa]

I have one machine with about a 50/50 chance to not find my network on boot. My workaround was to just disable and enable the network adapter on login.

And recently I had the issue that one VM couldn't connect to the internet, but worked fine connecting to other VMs and local machines. In that case I fixed it by setting a different DNS (try google or cloudflare)

That sounds more like something isn't properly shutting down and somehow gets stuck when the system boots back up.
Might be interesting if there is anytihng in windows event viewer that could give a hint.

Event viewer has some warnings and failures on startup

• An e2fexpress warning from Intel(R) Ethernet Controller (3) I225-V that the viewer can't find a description for. I don't have the ethernet cable plugged in so that may be it. (ID 27)
• Several DNS client timeout warnings: "Name resolution for the name wpad timed out after none of the configured DNS servers responded." (ID 1014)
• There's a series of WLAN events starting with a warning (ID 4003)

WLAN AutoConfig detected limited connectivity, attempting automatic recovery.​

​

Recovery Type: 4​

Error Code: 0x0​

Trigger Reason: 7​

IP Family: 0​

then another warning: (ID 10002)​

WLAN Extensibility Module has stopped.​

​

Module Path: C:\WINDOWS\System32\DriverStore\FileRepository\netwtw6e.inf_amd64_05bb65221939f713\IntelIHVRouter10.dll​

then an info-level event: (ID 10001)​

WLAN Extensibility Module has successfully started.​

​

Module Path: C:\WINDOWS\System32\DriverStore\FileRepository\netwtw6e.inf_amd64_05bb65221939f713\IntelIHVRouter10.dll​

• Several DistributedCOM warnings: "The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID..." that from what I can google I don't think are relevant? (ID 10016)
• Three Hyper-V VmSwitch errors that all say "Failed to connect NIC 95AABE2B-A98D-4B5A-8C9C-44837C363149--00AD49CE-10EF-543A-81E6-A8E47B58375F (Friendly Name: ) to port 86275E64-2651-4FE5-AAD6-27501B3AF47C (Friendly Name: ) on switch 20DCAA1D-CD47-4BE0-91B0-26AF8A8E8D2A (Friendly Name: ), status = Object Name not found.." exactly (ID 32) There are other Hyper-V VmSwitch events that succeed in connecting to different ports.

I would be suspect of something like a windows firewall issue or some other software thing. It is unlikely you get both wifi and ethernet interfaces actually broken.

Did you check the IP addresses you had with the IPCONFIG command or did you just reset them. Do actually get IP addresses from the router and can you ping the router IP.
Does it work to set a fixed IP address if it does not get IP from the router.

If you get IP from the router via dhcp then it means the very basic communications function is working and something else is blocking the traffic.

Tried disabling Windows firewall completely, didn't work either time. I can ping the router's IP (the one as default gateway, right?) as well as 127.0.0.1, but not localhost, don't know if that's just an alias issue or what.

It can connect to my printer over direct wifi, but not through my wifi network. The laptop on the wifi can't see it either, and it can't see the laptop, but the Google router shows up on both of them as OnHub. All network and sharing permissions are on for both machines and it's a private network on both.

 

[bill001g]

If you can ping the router then you have a network connect at the basic level.

Try to ping 8.8.8.8

If that works then it is likely a DNS issue. Try to manually set the DNS in the IPv4 settings to 8.8.8.8

 

[nimbosa]

If you can ping the router then you have a network connect at the basic level.

Try to ping 8.8.8.8

If that works then it is likely a DNS issue. Try to manually set the DNS in the IPv4 settings to 8.8.8.8

Nope, can't ping 8.8.8.8

 

[bill001g]

That is very strange. Normally if you can ping the router the traffic will go to the router and then be dropped.

If you run tracert 8.8.8.8

Do you get a error immediately or does it show the router IP as the first hop.

Maybe try something a bit more complex. Can you open the ip of the router in the web browser as if you were going to configure it.

 

[nimbosa]

That is very strange. Normally if you can ping the router the traffic will go to the router and then be dropped.

If you run tracert 8.8.8.8

Do you get a error immediately or does it show the router IP as the first hop.

Maybe try something a bit more complex. Can you open the ip of the router in the web browser as if you were going to configure it.

It shows an error immediately, no router IP. I can open the router IP in a browser.

 

[bill001g]

Look in the ipconfig /all for your ethernet port. Check the subnet mask is 255.255.255.0. It for some reason does not know to send 8.8.8.8 to the gateway IP.

When you run tracert it should send the packet to the gateway first and since you can actually get into the router/gateway it means communication is good.

You could also try to temporarily disable the firewall but generally firewall will not block ping or tracert.

 

[nimbosa]

Look in the ipconfig /all for your ethernet port. Check the subnet mask is 255.255.255.0. It for some reason does not know to send 8.8.8.8 to the gateway IP.

When you run tracert it should send the packet to the gateway first and since you can actually get into the router/gateway it means communication is good.

You could also try to temporarily disable the firewall but generally firewall will not block ping or tracert.

Ok, I actually found the problem. It was a VPN I used to use for work. It wasn't on, and I don't think it was even set to launch on startup, so I didn't think it was an issue. But I uninstalled it and everything started working again. Thanks for the help, especially since thinking about firewalls prompted me to dig around for any program that could be blocking traffic.