[kwlug-disc] Ubuntu 12.04 LTS localhost* and internet fail - where to start?
unsolicited at swiz.ca
Wed Apr 9 19:15:15 EDT 2014
What he said. Plus ...
Every so often I find resolv.conf gets trashed.
Thus ping 184.108.40.206 works but ping google.com does not.
Solution: add 'nameserver 220.127.116.11' into resolv.conf and get on with your
i.e. You'll have a better ability to troubleshoot the issue once you can
web browse again.
Thus, John, you have to distinguish between name resolution issues and
So, your next friend (having resolved any name resolution issues above),
is traceroute (tracert on windows). [You don't have to like / live with
Google DNS name resolution if you don't want to, permanently, but this
helps get you through that moment.]
So, if you 'traceroute 18.104.22.168' (or 22.214.171.124) you should see it hop along
out to the world, and if it doesn't / gets stopped, you've narrowed down
the size of your haystack. traceroute is more useful than ping here, but
ping is so much faster / easier to rip off / not have to wait for as you
do with traceroute.
Given multiple machines, you can do it from both to see if the problem
is unique to one or the other. (For example, a statically added route
lying around.) Routers frequently have a ping ability too. Taking ISP /
internet connectivity from house to world off the table sooner rather
than later can help retain sanity.
On 14-04-09 09:53 AM, L.D. Paniak wrote:
> Can you ping a site on the internet from clients? eg 126.96.36.199
> If not, you have no connectivity to the internet. Check
> cables/routing/gateway config.
> If so, can you ping a site by name: google.ca
> If not, check DNS.
> On 04/09/2014 09:46 AM, John Johnson wrote:
>> Ubuntu 12.04 LTS localhost* and internet fail (w/FF)- where to start?
>> My Linux box is, all of a sudden, failing to connect to the internet.
>> I was on a site earlier when the site (and others) started returning
>> the FF "server not found" (404) message.
>> Actually, I have made, I think, a good start (see below).
>> I am asking where do I go now?
>> Troubleshooting round one:
>> Boot. Reboot. Ubuntu restart. etc.
>> re-wired Linux box to Router connections.
>> Troubleshooting round two:
>> Linux box > terminal > ping 192.168.0.1 (Dlink router) are OK
>> Linux box > terminal > ping 192.168.0.115 (Windows box) OK
>> Linux box > terminal > ping 192.168.0.101 (loop back to Linux box) OK
>> Linux box > terminal > ping localhost (loop back to Linux box via
>> LAMP) OK *
>> Windows box > cmd window > ping 192.168.0.1 (Dlink router) are OK
>> Windows box > cmd window > ping 192.168.0.101 (Linux box) are OK
>> Windows box > cmd window > ping 192.168.0.115 (loop back Windows box)
>> are OK
>> Windows box > cmd window > ping localhost (loop back to Windows box
>> via XAMPP) are OK
>> *ping localhost was failing on the Linux box when I started
>> troubleshooting. Working now.
>> FF internet access still fails.
>> Troubleshooting round three:
>> Suspecting that the issue may be isolated to FF:
>> FF restarted in safe-mode. i.e. with add-ons disabled: still fails
>> Attempted bypass of FF through Ubuntu Software Centre and install of
>> Chromium browser: fail.
>> Analysis: The issue does not look to be isolated to FF.
>> kwlug-disc mailing list
>> kwlug-disc at kwlug.org
> kwlug-disc mailing list
> kwlug-disc at kwlug.org
More information about the kwlug-disc