Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Can't connect to internet after power failure. 1

Status
Not open for further replies.
Mar 31, 2007
6
JP
I've got the power cut while PC was running (w7). After rebooting I'm not able to connect to the internet anymore.

In Device Manager, under Network Adapters there is a "Realtek PCIe GBE..." device properly installed.
But under Other Devices there are now more entries with exclamation mark:
- Network controller
- Multimedia controller
- PCI Communication controller
I tried updating the drivers, then deleting and reinstalling but no success so far. Still can't connect to the internet.
The browser can see the router, at 192.168.1.1
I don't know where the problem is.

I'm quite puzzled, I'd appreciate any ideas about what I could do.

Thanks
 
does the router have an WAN IP? What do you get with ipconfig/all from a command prompt? Are the ip addresses for the DNS servers in the router correct? From a command prompt what do you get with a ping microsoft.com or a ping to 8.8.8.8 (public dns server for Google)? It is possible the OS got damaged when power was lost, what happens if you reload to an earlier time?
 
System Restore back to a day (or two days) before the power outage.
Then check Device Manager for missing items/exclamation points.

If still there, you're going to have to install those items manually, but.....

There's always a chance that the motherboard was damaged as well. No UPS attached to the computer??? Power problems can kill you any time. I strongly recommend everyone have a UPS to protect their PC.

Something basic like this at a minimum:
 
rclarke250 - you beat me to the POST button.

Also, if the route can be pinged/logged into, look upstream to see if the modem is dead/damaged. Contact the ISP to see if they can see your modem.
 

Further to rclarke250's and goombawaho's suggestions try doing the following in the order indicated:

1. Shut down computer
2. Shut down router
3. Shut down modem
4. Wait 30 seconds and turn on modem.
5. Once modem is fully booted turn on router.
6. Once router is fully online turn on computer.
7. Log in and try connecting to the Internet again.

Hope this helps.

Please help us help you. Read Tek-Tips posting polices before posting.
Canadian members check out Tek-Tips in Canada for socializing, networking, and anything non-technical.
 
Did you try system restore as suggested??? That should have been the 3rd step after rebooting everything and reinstalling drivers.

If you can plug another PC into your router/modem and it works, I'd say network card is toasted, assuming you got rid of all the unknown devices in the Dev Mgr.

Try an add-in PCI-E network card or wireless USB card. And buy that UPS.

If you want to go nuts and just prove that it's the motherboard, reload your O.S. from scratch.
 
what does it matter if you don't have a static IP? What address is the pc at?should be 192.168.1.xxx, Since you can see the router at the gateway address, you should be able to log into the router, the status page of the router will tell you a lot, so will doing a ipconfig/all on your pc, do that and tell us what's there. Should be an ip address a gateway and dns on the pc, and the router should have both lan ip (192.168.1.1) and a wan ip, and dns server ip addresses. your link shows me nothing, says 404 error, and the rest is in Japanese.

Bypass the router, plug the output of the modem, into the lan port on the pc, reboot the pc, this should allow you access to the internet, if it does, the problem is in the router, if not, the problem is in the modem or pc. can you log into the status page of the modem?
 
What rclarke250 said is true. I'm not sure why I didn't think about this before: If you are getting an IP address and can ping or login to the router at 192.168.1.1 your network card is not fried and the driver must be installed. Sorry for being dense about that.

The other suggestions still apply though:
System restore, try a different network card.

After that, you have to start thinking about malware. Or even before.
 
OK, I think I've posted the wrong link. Here's the right one for the ipconfig /all. result.
Just in case, I write it as text too:


Windows IP Configuration

Host Name . . . . . . . . . . . . : 0age-PC
Primary Dns Suffix . . . . . . . .:
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled . . . . . . . .: No
WINS Proxy Enabled . . . . . . . .: No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix:
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address . . . . . . . . .: F8-0F-41-11-ED-B8
DHCP Enabled . . . . . . . . . . .: Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 address . . . . . . . . . . : 2001:c90:e99 :50c2 :2549 :7172 :6e82 :c983(Preferred)
Temporary IPu6 flddress . . . . . : 2001 :c90:e99 :50c2 :2418 :if ea:22ce :7620(Preferred)
Link-local IPv6 flddress . . . . .: fe80::2549:7172:6e82:c973%11(Preferred)
IPv4 flddress . . . . . . . . . . : 192 .168 .1.2(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained . . . . . . . . . .: Thursday, April 19, 2012 4:14:12 PM
Lease Expires . . . . . . . . . : Friday, April 20, 2012 4:14:11 AM
Default Gateway . . . . . . . . . : fe80::21a:30ff:fe55:301a%ll
0.0.0.0
192.168.1.1

DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
NetBIOS over Tcpip . . . . . . . .: Enabled

Tunnel adapter isatap.<78744C41-D18E-41D0-ABB8-64278A982E2C>:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . .:
Description : Microsoft ISATAP Adapter
Physical Address . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix :
Description . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

 
 http://www.japan-romania.com/_serban/ipconfigAll1.gif
So that IP info looks ok. Give us the ping results of "ping at the command prompt (no quotes).

Then:
Why don't you do a malware scan with TDSSKiller (first) and then MalwareByte's Anti-Malware (second) and report back.

Then it's down to a System restore or trying a different network card - whichever one is easier. Network card is easier if you have one.
 
What are you getting on the router status page? Can you log into the router? or if you plug the pc into the modem and reboot do you get internet? It looks like either a modem issue, or wan port side router issue.
 
^^^^That is good advice as well. As said, "if you plug the pc into the modem and reboot do you get internet?" and it does not work, contact your ISP.

If they say they can see your modem, go with my suggestions.
 
That's NOT the result of pinging google AND you didn't tell us if you tried the modem plugged directly into the PC.

In that picture, you are obviously plugged into the router still with a 192 IP address.

Please follow directions and report results clearly and accurately or you're wasting everyone's time.
 
3 IPv6 addresses (2 of which appear to be dodgy) and 3 Default Gateways (2 of which are invalid)?

Looks like a) the OP's IPv6 stack needs resetting and b) the OP is using either iTunes or Adobe CS3, both of which are known to add a Default Gateway of 0.0.0.0.

To fix a), do the following:
1. In the Start > Search text field enter 'CMD'.
2. When CMD is found, right-click on it and choose 'Run as Administrator'.
3. When the command prompt appears, type the following and press ENTER:
netsh int ipv6 reset reset.log
This should fix the spurious IPv6 settings, leaving just the Link-local IPv6 Address entry and removing the IPv6 entry for the Default Gateway. If the IPv6 entry remains in the Default Gateway list then, temporarily, disable IPv6 on the NIC.

To fix b) temporarily, do the following:
1. In the Start > Search text field enter 'CMD'.
2. When CMD is found, right-click on it and choose 'Run as Administrator'.
3. When the command prompt appears, type the following and press ENTER:
route delete 0.0.0.0
OR use the Microsoft Fixit, available here:
To fix b) permanently, disable or remove the Bonjour service.

Hope this helps...
 
I would hold off Rick998's suggestions until you try what I have said and what Rclarke250 has said. Please don't troubleshoot in three directions at once.

The next step should be to connect the PC to the modem and restart both. Please, do as indicated.
 
@Rick: Thanks, a lot, I could finally get connected to the net, hopefully not only temporarily!
So it seems the cmd instruction you said solved the problem:
netsh int ipv6 reset reset.log

And now the default gateway is no more 0.0.0.0

It's true I have Adobe CS3 installed, however there no Bonjour service active. I couldn't find it neither in TaskManager, nor in services.msc
I don't have iTunes installed.

I knew that internet still uses IPv4 so I don't quite understand why IPv6 when not properly set would be such a pain in the ass...

Many thanks!!!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top