Member Avatar for bongmort

I'm running Vista SP2 on a laptop. I have strong wireless signal, I can connect to network drives through wireless, but I can't get connected to the internet using IE or Firefox.

I can ping the router () and google.com with 0% loss, but get General failure if I ping the computer IP 192.168.1.7.

Would greatly appreciate any help.

  • 2 Contributors
  • 3 Replies
  • 201 Views
  • 8 Hours Discussion Span
  • Latest Post Latest Post by rch1231

Dani AI

Generated

As reported, the adapter shows a local IP and external name servers, and ’s pointer to Network and Sharing Center was the right first step. The combination of working SMB/network-drive access and successful ICMP to the router and an external host, while HTTP(S) fails in browsers, usually means HTTP traffic is being blocked, redirected, or proxied at the application or filter layer — not a simple IP/DNS outage. The “General failure” when pinging the host’s own IP further suggests a local stack or firewall/LSP interaction rather than the wireless link itself.

Troubleshooting order (fast checks first):

  • Inspect Windows/IE proxy (Internet Options → Connections → LAN settings) and Firefox network proxy settings for any configured proxy.
  • Check the system WinHTTP proxy:
netsh winhttp show proxy
  • Temporarily disable third‑party firewall/AV (brief test) to see if HTTP resumes. Test TCP port connectivity to a web server (telnet can be used if present).

If the above does not resolve, reset the socket/stack and clear DNS, then reboot:

netsh winsock reset
netsh int ip reset resetlog.txt
ipconfig /flushdns

Collect state information to narrow causes:

ipconfig /all
route print
netstat -ano | findstr :80
tracert -d 8.8.8.8

Also check the hosts file at %systemroot%\system32\drivers\etc\hosts for unexpected entries, and try a known public DNS (for example 8.8.8.8) temporarily to rule out DNS‑level filtering. Common culprits for this symptom set are (1) an unwanted proxy, (2) an LSP/filter driver installed by security software, or (3) a router/ISP-level DNS/content filter. Resetting Winsock and removing a bad proxy/filter often restores normal browsing.

Recommended Answers

All 3 Replies

Member Avatar for rch1231

My first suggestion in these cases is to see what shows under Network and Sharing Center, View Status, Details. Make sure that you have an IP address in the routers subnet and Name Servers assigned that you can ping and query (from command prompt : nslookup google.com <name-server IP address> ).

If there are no discrepancies then the next thing to try is assign the wireless a static IP address, disable the device, wait 5 seconds then re-enable. See if you get a stable connection then.

Member Avatar for bongmort

The View Status, Details showed an IP address of and names servers and 156.154.71.22.

When I typed "nslookup google.com ", I got a Usage response with syntax codes. Am I missing something in the command?

Thanks.

Member Avatar for rch1231

Should be:

nslookup google.com
nslookup <domain name> <name server to query>

Sorry it is probably the way I listed the command options.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.