I have a Lenovo S10e netbook running a pretty clean version of 32bit opensuse 11.4, with very few standard patches since i installed it all those moons ago.
The problem is that firefox cannot connect to the internet, the odd bit is that skype has no such problems.
Are there any network related functions that that typically go screwy that might cause such a problem?
The netbook really hasn’t been used much for tinkering to have ‘accumulated’ a problem, but I’m about to give it to the extremely non-technical parents in law and cannot have it misbehaving, especially not as they are in a different country.
The reason can be DNS. I don’t know but may be Skupe is using IP addresses to connect.
You can check ping to your router and if it is working, you can try to change DNS. In example google DNS:
Tell us a bit more how you connect to the internet. This sounds like a possible DNS issue. When you think you should be connected, what is reported from this command?
On 07/26/2011 09:26 PM, Jedibeeftrix wrote:
>
> The problem is that firefox cannot connect to the internet, the odd bit
> is that skype has no such problems.
strange!
what operating system/version, bit and what firefox version/bit are you
using
if you are using openSUSE 11.4 and firefox 5.0 without having ever
installed from Factory, or Tumbleweed continue, if not post:
go Menu > File > Work Offline and UNcheck that box if it is checked…
if that fixes it great…but, if it is already unchecked then here are
some things to try (one at a time, checking for connectivity after each):
NOTE: read my caveat prior to proceeding.
confirm a different browser can get out…
disable all addons, if that fixes the problem then install them again
one at a time until you find the bad actor
remember and undo all of the tweaks you made to about:config
delete all cookies and history
using YaST > Software Management, search for firefox, and right click
on the black check mark and select “Update”…this will remove and
replace FF (the idea is maybe something got scrambled–have you had any
freezes or forced shutdowns…any disk problems?)
using YaST > Security and Users > User and Group Management, add a new
test user…log out and back in as that test user and see if FF works
as expected…
let us know how you get on…and what worked, if any do…
–
DD Caveat-Hardware-Software
openSUSE®, the “German Engineered Automobiles” of operating systems!
The first command would have overwritten any prior nameserver entry that may have existed, but it may be that before you executed that, there was no nameserver entry. That is why
grep name -i /etc/resolv.conf
resulted in - "nameserver 8.8.8.8"
Without adding the 8.8.8.8 (Google public DNS), you probably don’t have a name server configured.
When you next connect, to test whether DNS is working, you can do
ping google.com
It should return something like this
PING google.com (74.125.31.103) 56(84) bytes of data.
64 bytes from tb-in-f103.1e100.net (74.125.31.103): icmp_seq=1 ttl=40 time=181 ms
64 bytes from tb-in-f103.1e100.net (74.125.31.103): icmp_seq=2 ttl=40 time=183 ms
Edit: Another thing you can try is entering this google.com IP address into your browser
http://74.125.31.103/
Does that work ok? (It almost certainly will I’m guessing).
If a site cannot be resolved by name, then you have a DNS issue (and not a browser issue). After you add the nameserver entry, restart firefox, and try browsing again.
apologies people, turns out those first two commands (or one of) did the job magnificently, as the internet now works, i didn’t check as i thought they were only diagnostic.
apologies people, turns out those first two commands (or one of) did the job magnificently, as the internet now works, i didn’t check as i thought they were only diagnostic.
many thanks.
The command I gave was diagnostic, and should have been used to find out if any name servers were configured. From your first post, it was likely that it was a DNS issue. The command posted by rysic was to manually add a public name server to /etc/resolv.conf, however this will not survive a reboot, so you may need to configure your connection via YaST (if using ifup method), or Network Manager. Add any required DNS server IP address(es) permanently there.