Unexplainable lack of internet access, No error messages.

Up until 2 days ago, everything was peachy. Then, for whatever reason, my computer decided to not connect to the internet. The weird thing is, it says its connected in the system tray, and the windows internet diagnostics tell me that it "Can't identify the problem". My laptop is hooked up both wirelessly and hard wired to a router, but I doubt its the router that's the issue, because I'm currently typing this from my school laptop, which is working fine. As is every other computer.

So its just that laptop. I don't really know how to make it clear exactly whats wrong, but I'll try my best.

When I run windows live messenger troubleshooting, it tells me "key ports" isn't working.

Peerblock, upon starting the computer, would give the error message:

base filtering engine
ipsec poligy agent
ike authIP IPsec keyring modules

So I looked for ways to fix that, and found out that this was caused by a virus. 2 scans and 26 problem fixes later, I download a BFE fix from my school laptop and transfer it over to the fail one, and peerblock seems to work, but can't load because I still don't have internet access.

edit: peerblock seems to be working fully, blocking incoming connections. Still can't connect to anything else.

But I don't know how. There is no little error icon on the internet thing in the system tray. (look at me and my fancy lingo!)

I went to yahoo answers and got a lot of derp replies, like "If ur on the internats now than why issar a problem, stupid".

I appreciate any help you can give, even if my ineptitude puts you off =(

Possibly a basic really but does the problem computer have its correct addresses - IP, Subnet Mask, Default Gateway and DNS Servers?

You ask me like I can understand what exactly it is you're asking me to check.

Windows live messenger had that stuff in its list when it was troubleshooting, but they all had checkmarks. Only "Key Ports" was broken.

Run ipconfig /all in a Command Prompt window. Go to “Start > Run”, type…

cmd.exe /k ipconfig /all

...and click OK. This will show details of all network adapters installed in the PC. Right click in the Command Prompt window, "Select All" and press Enter to copy the details to the clipboard. Paste the details into a forum reply here.

If you are unable to paste the details directly from the computer, because it cannot get online, paste them instead into a blank "Notepad" file, transfer the file to a working PC and copy/paste the details from there.

Windows IP Configuration

Host Name . . . . . . . . . . . . : (something lalalala)
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : 14-DA-E9-0D-80-16
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wireless Network Connection 2:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Virtual WiFi Miniport Adapter
Physical Address. . . . . . . . . : 82-B9-A5-AF-14-A1
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Atheros AR9285 Wireless Network Adapter
Physical Address. . . . . . . . . : E0-B9-A5-AF-14-A1
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.1.67(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : November-30-12 5:08:20 AM
Lease Expires . . . . . . . . . . : December-01-12 5:08:24 AM
Default Gateway . . . . . . . . . : 192.168.1.254
DHCP Server . . . . . . . . . . . : 192.168.1.254
DNS Servers . . . . . . . . . . . : 192.168.1.254
75.153.176.1
NetBIOS over Tcpip. . . . . . . . : Enabled

The addresses appear to be OK but I see you're using a "wireless" connection and the ethernet adapter is disconnected. Are you also unable to get online with a wired ethernet connection?

mgmcc said:

The addresses appear to be OK but I see you're using a "wireless" connection and the ethernet adapter is disconnected. Are you also unable to get online with a wired ethernet connection?

Nope, they both give the same issue. Appear to be connected (both wireless and ethernet, I've tried both together and seperately) but don't connect. Troubleshooting says it can't identify the problem.

It may be that the TCP/IP stack or Winsock has been damaged in which case open a Command Prompt window ("Start > Run", type cmd and click OK).

To repair the TCP/IP stack, at the prompt, type...

netsh int ip reset resetlog.txt

...and press Enter

(note the spaces in the command line). The original prompt will reappear, exit the Command Prompt window and reboot the PC.

To reset Winsock entries, at the prompt, type...

netsh winsock reset catalog

...and press Enter

Exit the Command Prompt window and reboot the PC. (If running both repairs, reboot after running the second command.)

The second repair doesn't seem to work. It just keeps telling me "the following helper/command was not found/cant be loaded: WSHELPER.DLL/winsock reset catalog

Edit: I did something, I don't know what, but here's more info. I looked to google to see how else I could reset winsock, and found I can release/renew ipconfig. I did that, then ran the windows internet troubleshooter again, it came up with 2 errors. For a whole minute, I had internet access, but then it went back to the original issue. Seems to be connected, troubleshooter can't identify, can't connect to anything.

You would want to make sure that was an elevated "Admin" command prompt.

If this system can't run the winsock reset command then there are more than just network problems here.


You might want to run the sfc/scannow command and see what it comes up with.