Can ping but cant browse [SOLVED]
Still struggling with this I'm afraid. It doesn't make any sense to me that I can ping an address but not browse to it. It proves I've got an internet connection with DNS. I can connect to the router no problem. My wifi signal is strong. I have a second laptop that also experiences the same problem.
I restored factory settings on my router but that didn't solve the problem. What was also strange was that I can connect to an FTP server but when I do something like a directory listing or a download the connection times out. Maybe there is a problem when transferring larget amounts of data.
The only thing that seems strange to me is the naming of my networks. When the LAN cable is plugged in I have an SSID = Fred, a LAN "home network" called Fred, and a wireless "home network" called Fred 2. (This is Win 7.) I don't know whether this is causing any conflicts. (Obviously when I try out the wireless network I unplug the LAN cable and only have the wireless network listed.)
I restored factory settings on my router but that didn't solve the problem. What was also strange was that I can connect to an FTP server but when I do something like a directory listing or a download the connection times out. Maybe there is a problem when transferring larget amounts of data.
The only thing that seems strange to me is the naming of my networks. When the LAN cable is plugged in I have an SSID = Fred, a LAN "home network" called Fred, and a wireless "home network" called Fred 2. (This is Win 7.) I don't know whether this is causing any conflicts. (Obviously when I try out the wireless network I unplug the LAN cable and only have the wireless network listed.)
Purleigh,
>So does browsing to 192.168.0.1 work with a WIRED connection ?
Yes.
I use FF already, and get the same responses from both FF & IE. I've got my firewall back on now.
Just to confuse things www.bbc.co.uk seems to be offline at present, but I tried with other sites instead.
So, while still wired and the router firewall is ENABLED I checked that Internet Explorer and Firefox BOTH can access www.bbc.co.uk/news and to 192.168.0.1 OK. No problems there.
I then tried with wireless. Now here's the strange thing - they are currently connecting, only sometimes, and then usually very slowly, although sometimes near normal speed. I had this a couple of days ago, but since then the connection had failed altogether. This afternoon it seems it is back. BTW: Windows says my signal strength is excellent, and I'm on channel 6 - with inSSIDer telling me that the signal is way stronger than all others in the area.
So I'm starting to think that this is an RFI problem, or maybe a hw failure in the router wireless circuits. I'd guess that the browsers are timing out when fetching web pages, and that is why pinging worked but browsing didn't. Appreciate your thoughts, particularly on how to tell if it is an RFI/interference problem.
>So does browsing to 192.168.0.1 work with a WIRED connection ?
Yes.
I use FF already, and get the same responses from both FF & IE. I've got my firewall back on now.
Just to confuse things www.bbc.co.uk seems to be offline at present, but I tried with other sites instead.
So, while still wired and the router firewall is ENABLED I checked that Internet Explorer and Firefox BOTH can access www.bbc.co.uk/news and to 192.168.0.1 OK. No problems there.
I then tried with wireless. Now here's the strange thing - they are currently connecting, only sometimes, and then usually very slowly, although sometimes near normal speed. I had this a couple of days ago, but since then the connection had failed altogether. This afternoon it seems it is back. BTW: Windows says my signal strength is excellent, and I'm on channel 6 - with inSSIDer telling me that the signal is way stronger than all others in the area.
So I'm starting to think that this is an RFI problem, or maybe a hw failure in the router wireless circuits. I'd guess that the browsers are timing out when fetching web pages, and that is why pinging worked but browsing didn't. Appreciate your thoughts, particularly on how to tell if it is an RFI/interference problem.
