Firefox can only browse open source web sites

Asked by Jimr

This is an ongoing problem I have had with Firefox 2.0 included in the Ubuntu install. First time it happened was immediately on install of 6.06 about 6 months ago. I can browse (almost) any open source site just fine. Any other site, however, including Google, simply won't ever appear. The clock just sits and whirs, and .... nothing. I recently installed 6.10 (Edgy). Everything worked just great until I tried to use the web interface to reconfigure my ActionTec DSL router. The Networking control panel crashed when trying to refresh the DHCP config, and now I have the same problem with Firefox not being able to browse any sites except Ubuntu and some of the other open source sites. DNS works fine, as I can ping hosts by name on the internet. Email still works fine. It is like the sites are blocked somehow.

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu firefox Edit question
Assignee:
No assignee Edit question
Solved by:
Jimr
Solved:
Last query:
Last reply:
Revision history for this message
Alan Pope 🍺🐧🐱 🦄 (popey) said :
#1

To eliminate Firefox from the equation can you try a couple of things:-

Open a terminal with Applications --> Accessories --> Terminal. In the terminal type the following command:-

wget http://google.com/

You should see something like this:-

alan@wopr:~$ wget http://google.com/
--09:38:01-- http://google.com/
           => `index.html'
Resolving google.com... 72.14.207.99, 64.233.167.99, 64.233.187.99
Connecting to google.com|72.14.207.99|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://www.google.com/ [following]
--09:38:02-- http://www.google.com/
           => `index.html'
Resolving www.google.com... 64.233.183.103, 64.233.183.104, 64.233.183.147, ...
Connecting to www.google.com|64.233.183.103|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://www.google.co.uk/ [following]
--09:38:02-- http://www.google.co.uk/
           => `index.html'
Resolving www.google.co.uk... 64.233.183.147, 64.233.183.99, 64.233.183.103, ...
Reusing existing connection to www.google.com:80.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]

    [ <=> ] 3,215 --.--K/s

09:38:02 (134.30 KB/s) - `index.html' saved [3215]

If that works (you get a file saved) then you should be able to open that in firefox by typing this:-

mozilla-firefox ~/index.html

And you should see the usual google form - missing the images.

If that all works then it is likely that the problem could be with Firefox. Can you check that you do not have a proxy server set with the following procedure:-

System --> Preferences --> Network Proxy

It should have "Direct internet connection" in there.

Also double check the settings in Firefox:-

Edit --> Preferences --> Advanced --> Network --> Settings.

Revision history for this message
Jimr (texcellence) said :
#2

Thanks.

I checked both preferences settings. They are both set to "Direct Internet Connection". I tried installing Edgy on a different hard drive, to see if it would work like it did at first. The fresh install has the same issue. It acts like a DNS problem, but I can do a lookup and get resolution every time. I can ping host names of DNS servers that I know respond to ICMP, and they all resolve and I get replies. However, I tried your suggestion and entered the commands and this is what I get (copied and pasted from terminal):

jimr@jimr-desktop:~$ wget http://google.com/
--15:34:03-- http://google.com/
           => `index.html'
Resolving google.com... 72.14.207.99, 64.233.167.99, 64.233.187.99
Connecting to google.com|72.14.207.99|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://www.google.com/ [following]
--15:34:08-- http://www.google.com/
           => `index.html'
Resolving www.google.com... 1.0.0.0
Connecting to www.google.com|1.0.0.0|:80... failed: Connection timed out.
Retrying.

--15:37:19-- http://www.google.com/
  (try: 2) => `index.html'
Connecting to www.google.com|1.0.0.0|:80...

It hangs forever. Note what the address resolved to the second time around. Obviously, resolution didn't work the second time. I don't get it. Windows 2000 on a different hard drive on the same computer works perfectly, so it doesn't seem to be a problem with the DNS servers, and weirdly enough, Edgy worked flawlessly for about two weeks, although I never got 6.06 to work. I'm using Qwest's DNS servers 205.171.2.65, and 205.171.3.65. The addresses are being supplied by my ActionTec DSL modem through DHCP. By the way, I'm writing this from Edgy. I can get to THIS site just fine. I just can't get to any non-open-source web site, and can't even get to many of the open-source sites.

Revision history for this message
Best Jimr (texcellence) said :
#3

Alan

I think I got it. Ubuntu can't use the ActionTec DSL modem as a DNS server, even though it works with Windows. I eliminated the entry for the modem's address, and just added another Qwest DNS server address, and now it works fine. Thank you much for your command line information. That turned the light on for me.

Jimr

Revision history for this message
santosh (umy1luv) said :
#4

santosh
        i think this yhe perfect one when i intered iin this site.