Can't access websites through browser - but can ping them

  • Thread starter Thread starter Pho
  • Start date Start date

Pho

Pho

Pho

Soldato
Joined
18 Oct 2002
Posts
9,336
Location
Derbyshire
I've got a slight problem with my internet at home and am pretty stumped as to how to fix it.

My PC seems to have lost connectivity when using any browser or things such as Filezilla or Remote Desktop client, apart from when trying to access local IPs on my network or my router.

I can ping domains and the correct IP is returned; so I assume it's not a DNS problem. Other PCs in the house can access the internet fine, which suggests it's not a problem with my internet. I have disabled Windows Firewall and have tried setting it to 'allow all' mode with no luck.

I had this problem a few days ago which I think was caused by Wippien and it's metric setting; but I've even uninstalled that and it doesn't work still.

The proxy options in Internet Explorer are not set either.

Any ideas? It's quite frustrating!

Thanks.
 
I know when I removed the Bonjour app/service it knacked up the PC and I had to repair the WinSock. So I had to download (from another PC) and run LSPFix.

See if that helps. :)

Have you tried a different browser also? (Firefox, Opera).

For good meausre maybes replace the DNS settings in your Router to OpenDNS and then do an ipconfig /flushdns (or is it /dnsflush..... can never remember).

Thanks!
 
I tried LSPFix but it said there was no errors (everything was ok).

I've tried Firefox, IE and Chrome and none work. I've also tried OpenDNS but that's not working either; my DNS was setup as Google primary, OpenDNS secondary anyway.

I'm now down to inspecting it with Wireshark, this will be fun :/.
 
Well.. fixed it. :o.

I think it was actually a combination of two things; Wippien and my router. Wippien did cause my Internet to break like it did a few days ago, but my usual fix to that didn't work which was what made me think it had done something else to break it - but in fact I think my fix must have worked as it unblocked pinging.

I found out that when setting up some port-forwarding rules for my webserver on port 80 I'd added the rule to the 'IP Filters' section by mistake, which then blacklisted port 80 from my PC causing websites to be blocked. This would explain why I lost the ability to telnet to websites on port 80 too (it was working after I sorted out Wippien) but I completely forgot about that change I made.

If only I thought of the obvious solution of changing my IP first :o.
 
You must log in or register to reply here.
Back
Top Bottom