[kwlug-disc] Ubuntu 12.04 LTS localhost* and internet fail - where to start?
jvj at golden.net
Wed Apr 9 17:30:22 EDT 2014
Resisted. continuing. Ubuntu issues w/router persist.
Lost count of troubleshooting exercises.
Recap: At 7:30 am all was OK and that during a session on a website via
the Linux box, the internet access to that site went down.
This leads be to believe that the configuration of the Linux box was
Dlink router: downloaded and installed latest firmware. Reset
configuration to factory defaults.
Windows box: internet access continues to be OK.
Linux box: Previously configured to dial through DSL modem to ISP.
Linux box: Now does the same through router.
ifconfig now shows IP 209.183.xxx.yyy not 192.168.0.100 as before (at
7:30 to 11:30 am)
Linux box Changed Settings > Network > Options > wired not DSL
Rebooted. NADDA ifconfig now shows IP 209.183.xxx.yyy not 192.168.0.100
Linux box: ping 127.0.0.1 OK
Linux box: ping localhost OK *
* sometimes fails (not sure what I was doing when I saw the failure)
Router: moving wires between physical ports. NO WIRELESS.
I am shutting everything down for a cold boot boot later this evening
and will pick up on this at that time.
On 2014-04-09 10:51, John Johnson wrote:
> Thanks for the tip: was looking for something like this.
> Troubleshooting round four:
> Pings with named ping destinations fail on both the Linux and Windows
> e.g. c:\>ping https://www.google.ca c:\>ping http://www.google.ca
> One of the destinations recommended in the link above, ping 22.214.171.124
> works on the Windows box.
> The Linux box however is still failing.
> On the Linux box, the error message returned for ping 126.96.36.199 is
> different from ping http://www.google.ca.
> For the google.ca, I see "unknown host".
> For 188.8.131.52 I see: from 192.168.0.1 icmp_ .... Destination Net
> Looks like the router is blocking the Linux box.
> Rebooted router. NADDA.
> Troubleshooting round five:
> Bypassed the Dlink router. Connected Linux box direct to DSL modem.
> Setup Ubuntu > Settings > Network as req'd to dial on the DSL modem as
> opposed to wired connection.
> FF on Linux box works.
> The issue with the Dlink router not the Linux box per se.
> Disconnected the Linux box, reconnected router and Windows box.
> OT (slightly):
> How do I set up Ubuntu with more than Network connection configuration?
> 1) (default) wired connection through router (w/o 'dialer' settings)
> 2) DSL modem with 'dialer' settings
> On 2014-04-09 09:53, L.D. Paniak wrote:
>> Can you ping a site on the internet from clients? eg 184.108.40.206
>> 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
>> Checked by AVG -www.avg.com
>> Version: 2014.0.4355 / Virus Database: 3882/7318 - Release Date: 04/08/14
> kwlug-disc mailing list
> kwlug-disc at kwlug.org
> Checked by AVG - www.avg.com <http://www.avg.com>
> Version: 2014.0.4355 / Virus Database: 3882/7318 - Release Date: 04/08/14
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the kwlug-disc