No network on 12.04 install

[Dotan Cohen]

I just installed Kubuntu 12.04 on a new computer with an Asus
motherboard containing onboard NIC. The onboard NIC is enabled in
BIOS. I don't happen to have a spare network card to test with. The
internet connection is via a D-Link router, either wired or wireless
via T-Link USB wireless adapter. The internet connection works fine
for other computers on the network (2 wired and 1 wireless). I have
tried multiple known-good cables and router ports with this computer.
I also booting into Kubuntu 11.10 LiveCD to test there as well, same
results.

This machine will not connect to the internet. On the wired connection in 12.04:

shelly@neptune:~$ sudo service networking status
networking stop/waiting
shelly@neptune:~$ sudo service networking restart
stop: Unknown instance:
networking stop/waiting
shelly@neptune:~$ ping google.com
ping: unknown host google.com
shelly@neptune:~$ ping 127.0.0.1
PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.
64 bytes from 127.0.0.1: icmp_req=1 ttl=64 time=0.027 ms
64 bytes from 127.0.0.1: icmp_req=2 ttl=64 time=0.019 ms
64 bytes from 127.0.0.1: icmp_req=3 ttl=64 time=0.017 ms
64 bytes from 127.0.0.1: icmp_req=4 ttl=64 time=0.027 ms
64 bytes from 127.0.0.1: icmp_req=5 ttl=64 time=0.018 ms
64 bytes from 127.0.0.1: icmp_req=6 ttl=64 time=0.021 ms
64 bytes from 127.0.0.1: icmp_req=7 ttl=64 time=0.019 ms
^C
--- 127.0.0.1 ping statistics ---
7 packets transmitted, 7 received, 0% packet loss, time 5997ms
rtt min/avg/max/mdev = 0.017/0.021/0.027/0.004 ms
shelly@neptune:~$ ifconfig
eth0      Link encap:Ethernet  HWaddr 54:04:a6:82:6b:eb
          inet6 addr: fe80::5604:a6ff:fe82:6beb/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:6 errors:0 dropped:0 overruns:0 frame:0
          TX packets:230 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:360 (360.0 B)  TX bytes:50506 (50.5 KB)
          Interrupt:46 Base address:0xe000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:134 errors:0 dropped:0 overruns:0 frame:0
          TX packets:134 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:10616 (10.6 KB)  TX bytes:10616 (10.6 KB)

shelly@neptune:~$ lshw -C network
WARNING: you should run this program as super-user.
  *-network
       description: Ethernet interface
       product: RTL8111/8168B PCI Express Gigabit Ethernet controller
       vendor: Realtek Semiconductor Co., Ltd.
       physical id: 0
       bus info: pci@0000:04:00.0
       logical name: eth0
       version: 06
       serial: 54:04:a6:82:6b:eb
       size: 100Mbit/s
       capacity: 1Gbit/s
       width: 64 bits
       clock: 33MHz
       capabilities: bus_master cap_list ethernet physical tp mii 10bt
10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=r8169
driverversion=2.3LK-NAPI duplex=full firmware=rtl8168e-3_0.0.4
03/27/12 latency=0 multicast=yes port=MII speed=100Mbit/s
       resources: irq:46 ioport:e000(size=256)
memory:d0004000-d0004fff memory:d0000000-d0003fff
WARNING: output may be incomplete or inaccurate, you should run this
program as super-user.
shelly@neptune:~$ sudo lshw -C network
  *-network
       description: Ethernet interface
       product: RTL8111/8168B PCI Express Gigabit Ethernet controller
       vendor: Realtek Semiconductor Co., Ltd.
       physical id: 0
       bus info: pci@0000:04:00.0
       logical name: eth0
       version: 06
       serial: 54:04:a6:82:6b:eb
       size: 100Mbit/s
       capacity: 1Gbit/s
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress msix vpd bus_master cap_list
ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd
autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=r8169
driverversion=2.3LK-NAPI duplex=full firmware=rtl8168e-3_0.0.4
03/27/12 latency=0 link=yes multicast=yes port=MII speed=100Mbit/s
       resources: irq:46 ioport:e000(size=256)
memory:d0004000-d0004fff memory:d0000000-d0003fff
shelly@neptune:~$ sudo service network-manager status
network-manager start/running, process 823
shelly@neptune:~$ sudo service network-manager restart
network-manager stop/waiting
network-manager start/running, process 1684
shelly@neptune:~$ lsmod | grep -i r8169
r8169                  62099  0
shelly@neptune:~$



--
Dotan Cohen

http://gibberish.co.il
http://what-is-what.com

--
kubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users

[Basil Chupin-2]

On 30/06/12 02:36, Dotan Cohen wrote:

> I just installed Kubuntu 12.04 on a new computer with an Asus
> motherboard containing onboard NIC. The onboard NIC is enabled in
> BIOS. I don't happen to have a spare network card to test with. The
> internet connection is via a D-Link router, either wired or wireless
> via T-Link USB wireless adapter. The internet connection works fine
> for other computers on the network (2 wired and 1 wireless). I have
> tried multiple known-good cables and router ports with this computer.
> I also booting into Kubuntu 11.10 LiveCD to test there as well, same
> results.
>
> This machine will not connect to the internet. On the wired connection in 12.04:

2 days ago I installed an additional HDD on the computer. Took it off
the workbench, connected it to all the normal things - but I had no
connection to the internet (ie ADSL modem). The lights on the modem
showed that the cable WAS connected to the computer. Changed cables,
checked the BIOS, reset the BIOS - still nothing.

Yesterday I went out and bought a PCIe network card and now I have
internet access.

For some unknown reason the onboard LAN decided to die. And I always use
an antistatic strap when I am messing around with a computer.

BC



--
Using openSUSE 12.2 x86_64 KDE 4.8.4 and kernel 3.4.4 on a system with-
AMD FX 8-core 3.6/4.2GHz processor
16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM
Gigabyte AMD3+ m/board; Gigabyte nVidia GTX550Ti 1GB DDR5 GPU


--
kubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users

[Dotan Cohen]

On Sat, Jun 30, 2012 at 6:47 AM, Basil Chupin <[hidden email]> wrote:

> 2 days ago I installed an additional HDD on the computer. Took it off the
> workbench, connected it to all the normal things - but I had no connection
> to the internet (ie ADSL modem). The lights on the modem showed that the
> cable WAS connected to the computer. Changed cables, checked the BIOS, reset
> the BIOS - still nothing.
>
> Yesterday I went out and bought a PCIe network card and now I have internet
> access.
>
> For some unknown reason the onboard LAN decided to die. And I always use an
> antistatic strap when I am messing around with a computer.
>
> BC
>

My first inclination was a dead LAN port, but the computer shows the
same symptoms when trying to connect via USB wireless card.


--
Dotan Cohen

http://gibberish.co.il
http://what-is-what.com

--
kubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users

[Basil Chupin-2]

On 30/06/12 16:50, Dotan Cohen wrote:

> On Sat, Jun 30, 2012 at 6:47 AM, Basil Chupin <[hidden email]> wrote:
>> 2 days ago I installed an additional HDD on the computer. Took it off the
>> workbench, connected it to all the normal things - but I had no connection
>> to the internet (ie ADSL modem). The lights on the modem showed that the
>> cable WAS connected to the computer. Changed cables, checked the BIOS, reset
>> the BIOS - still nothing.
>>
>> Yesterday I went out and bought a PCIe network card and now I have internet
>> access.
>>
>> For some unknown reason the onboard LAN decided to die. And I always use an
>> antistatic strap when I am messing around with a computer.
>>
>> BC
>>
> My first inclination was a dead LAN port, but the computer shows the
> same symptoms when trying to connect via USB wireless card.

That particular USB port has 'gone' as well?

I even re-installed the whole OS system because I did not believe that
the onboard LAN could have gone belly up after only 2 months of use.
But....as they say in the movies, "S*** happens" :-( .

Does doing 'sudo lshw' or 'hwinfo' provide any clues? Or an entry in
/var/log message file?

BC

--
Using openSUSE 12.2 x86_64 KDE 4.8.4 and kernel 3.4.4 on a system with-
AMD FX 8-core 3.6/4.2GHz processor
16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM
Gigabyte AMD3+ m/board; Gigabyte nVidia GTX550Ti 1GB DDR5 GPU


--
kubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users

[Dotan Cohen]

On Sat, Jun 30, 2012 at 1:25 PM, Basil Chupin <[hidden email]> wrote:

> That particular USB port has 'gone' as well?
>
> I even re-installed the whole OS system because I did not believe that the
> onboard LAN could have gone belly up after only 2 months of use. But....as
> they say in the movies, "S*** happens" :-( .
>
> Does doing 'sudo lshw' or 'hwinfo' provide any clues? Or an entry in
> /var/log message file?
>
>

The system recognises and I can select wifi networks, but none of them connect.

The problem is that the system is not getting an IP address. It
appears that DHCP was not configured for either eth0 nor the WAN. I'm
fighting with it now to get DHCP working.

--
Dotan Cohen

http://gibberish.co.il
http://what-is-what.com

--
kubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users

[Nils Kassube-2]

Dotan Cohen wrote:
> The system recognises and I can select wifi networks, but none of
> them connect.
>
> The problem is that the system is not getting an IP address. It
> appears that DHCP was not configured for either eth0 nor the WAN. I'm
> fighting with it now to get DHCP working.

I would also check the router settings. If the router has DHCP disabled,
you wouldn't get an IP address either. I'm quite sure that DHCP is
enabled by default for Kubuntu.


Nils

--
kubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users

[Basil Chupin-2]

On 30/06/12 21:59, Dotan Cohen wrote:

> On Sat, Jun 30, 2012 at 1:25 PM, Basil Chupin <[hidden email]> wrote:
>> That particular USB port has 'gone' as well?
>>
>> I even re-installed the whole OS system because I did not believe that the
>> onboard LAN could have gone belly up after only 2 months of use. But....as
>> they say in the movies, "S*** happens" :-( .
>>
>> Does doing 'sudo lshw' or 'hwinfo' provide any clues? Or an entry in
>> /var/log message file?
>>
>>
> The system recognises and I can select wifi networks, but none of them connect.
>
> The problem is that the system is not getting an IP address. It
> appears that DHCP was not configured for either eth0 nor the WAN. I'm
> fighting with it now to get DHCP working.

Which is exactly what I went through and why I re-installed the system
thinking that the network configuration was somehow messed up :-( .

In my case, I even checked that the little contact "fingers" in the RJ45
connectors were correctly in place and didn't somehow get out of their
position (which actually happened many years ago on one of the RJ11
connectors).

The only suggestions I can now offer is to get a network card (borrow or
buy) and install that.

Frustrating I know when you think that there is no logical reason for
something like what you are experiencing should suddenly happen.

BC

--
Using openSUSE 12.2 x86_64 KDE 4.8.4 and kernel 3.4.4 on a system with-
AMD FX 8-core 3.6/4.2GHz processor
16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM
Gigabyte AMD3+ m/board; Gigabyte nVidia GTX550Ti 1GB DDR5 GPU


--
kubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users

[FarSight Data Systems]

On Saturday, June 30, 2012 08:46:29 AM Basil Chupin wrote:

> On 30/06/12 21:59, Dotan Cohen wrote:

> > On Sat, Jun 30, 2012 at 1:25 PM, Basil Chupin <[hidden email]> wrote:

> >> That particular USB port has 'gone' as well?

> >>

> >> I even re-installed the whole OS system because I did not believe that

> >> the onboard LAN could have gone belly up after only 2 months of use.

> >> But....as they say in the movies, "S*** happens" :-( .

> >>

> >> Does doing 'sudo lshw' or 'hwinfo' provide any clues? Or an entry in

> >> /var/log message file?

> >

> > The system recognises and I can select wifi networks, but none of them

> > connect.

> >

> > The problem is that the system is not getting an IP address. It

> > appears that DHCP was not configured for either eth0 nor the WAN. I'm

> > fighting with it now to get DHCP working.

>

> Which is exactly what I went through and why I re-installed the system

> thinking that the network configuration was somehow messed up :-( .

>

> In my case, I even checked that the little contact "fingers" in the RJ45

> connectors were correctly in place and didn't somehow get out of their

> position (which actually happened many years ago on one of the RJ11

> connectors).

>

> The only suggestions I can now offer is to get a network card (borrow or

> buy) and install that.

>

> Frustrating I know when you think that there is no logical reason for

> something like what you are experiencing should suddenly happen.

>

> BC

One of the things I like to do to test hardware is boot with knoppix. It will find all the working hardware, If the hardware works with that then you have an OS, configuration, or software problem. If the hardware doesn't work then, you need to fix the hardware.

Mark

--
kubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users

[Dotan Cohen]

On Sat, Jun 30, 2012 at 3:31 PM, Nils Kassube <[hidden email]> wrote:

> Dotan Cohen wrote:
>> The system recognises and I can select wifi networks, but none of
>> them connect.
>>
>> The problem is that the system is not getting an IP address. It
>> appears that DHCP was not configured for either eth0 nor the WAN. I'm
>> fighting with it now to get DHCP working.
>
> I would also check the router settings. If the router has DHCP disabled,
> you wouldn't get an IP address either. I'm quite sure that DHCP is
> enabled by default for Kubuntu.
>

Thank you Nils. The router does have DHCP enabled and working for
other computers on the LAN and WAN. Also, I tried connecting to
another known-good router on another network and also there would not
get an IP address.


--
Dotan Cohen

http://gibberish.co.il
http://what-is-what.com

--
kubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users

[Dotan Cohen]

On Sat, Jun 30, 2012 at 3:46 PM, Basil Chupin <[hidden email]> wrote:

> Which is exactly what I went through and why I re-installed the system
> thinking that the network configuration was somehow messed up :-( .
>
> In my case, I even checked that the little contact "fingers" in the RJ45
> connectors were correctly in place and didn't somehow get out of their
> position (which actually happened many years ago on one of the RJ11
> connectors).
>
> The only suggestions I can now offer is to get a network card (borrow or
> buy) and install that.
>
> Frustrating I know when you think that there is no logical reason for
> something like what you are experiencing should suddenly happen.
>

The network cable, router, router port, and USB wifi adapter are
known-good and work with other equipment. Frustratingly, even an
openSuse 12.1 LiveCD did not get an IP address via DHCP either!


--
Dotan Cohen

http://gibberish.co.il
http://what-is-what.com

--
kubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users

[Basil Chupin-2]

On 01/07/12 20:00, Dotan Cohen wrote:

> On Sat, Jun 30, 2012 at 3:46 PM, Basil Chupin <[hidden email]> wrote:
>> Which is exactly what I went through and why I re-installed the system
>> thinking that the network configuration was somehow messed up :-( .
>>
>> In my case, I even checked that the little contact "fingers" in the RJ45
>> connectors were correctly in place and didn't somehow get out of their
>> position (which actually happened many years ago on one of the RJ11
>> connectors).
>>
>> The only suggestions I can now offer is to get a network card (borrow or
>> buy) and install that.
>>
>> Frustrating I know when you think that there is no logical reason for
>> something like what you are experiencing should suddenly happen.
>>
> The network cable, router, router port, and USB wifi adapter are
> known-good and work with other equipment. Frustratingly, even an
> openSuse 12.1 LiveCD did not get an IP address via DHCP either!

Eh, sorry Dotan, but me thinks that it would appear that there is
something wrong with the mobo :-( .

But have you tried using a (borrowed) network card?

BC

--
Using openSUSE 12.2 x86_64 KDE 4.8.4 and kernel 3.4.4 on a system with-
AMD FX 8-core 3.6/4.2GHz processor
16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM
Gigabyte AMD3+ m/board; Gigabyte nVidia GTX550Ti 1GB DDR5 GPU


--
kubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users

[Dotan Cohen]

On Sun, Jul 1, 2012 at 3:18 PM, Basil Chupin <[hidden email]> wrote:
> Eh, sorry Dotan, but me thinks that it would appear that there is something
> wrong with the mobo :-( .
>
> But have you tried using a (borrowed) network card?
>

I tend to agree with you on this, but then why isn't it getting an IP
address when connecting via wifi over USB wifi adapter? I tried on two
separate known-good access points that I can connect to with other
equipment.


--
Dotan Cohen

http://gibberish.co.il
http://what-is-what.com

--
kubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users

[Basil Chupin-2]

On 01/07/12 22:34, Dotan Cohen wrote:

> On Sun, Jul 1, 2012 at 3:18 PM, Basil Chupin <[hidden email]> wrote:
>> Eh, sorry Dotan, but me thinks that it would appear that there is something
>> wrong with the mobo :-( .
>>
>> But have you tried using a (borrowed) network card?
>>
> I tend to agree with you on this, but then why isn't it getting an IP
> address when connecting via wifi over USB wifi adapter? I tried on two
> separate known-good access points that I can connect to with other
> equipment.

On the surface this appears to be a most reasonable question.

But what is now required - and which is always required when trying to
solve a problem - is to eliminate the variables which, in this case, is
trying out a (borrowed) network card. Once this has been tested then one
can concentrate on other possible causes of the problem :-) . Until this
is eliminated as a possible cause then your question comes to the
forefront :-) .

BC

--
Using openSUSE 12.2 x86_64 KDE 4.8.4 and kernel 3.4.4 on a system with-
AMD FX 8-core 3.6/4.2GHz processor
16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM
Gigabyte AMD3+ m/board; Gigabyte nVidia GTX550Ti 1GB DDR5 GPU


--
kubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users

[Hakan Koseoglu-2]

Dotan,
On 1 July 2012 13:34, Dotan Cohen <[hidden email]> wrote:
> I tend to agree with you on this, but then why isn't it getting an IP
> address when connecting via wifi over USB wifi adapter? I tried on two
> separate known-good access points that I can connect to with other
> equipment.

Not getting an IP via DHCP doesn't mean anything but there might be a
software fault. First, does it work at all? Assign it an IP address by
hand and then try pinging around.

Also you can do this:
hakan@jupiter:17:26:30:~$ cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
iface eth0 inet dhcp

More than once, esp. on my cloned VMs, Ubuntu decides to add a 2nd
card and then forgets all about it.

--
kubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users

[Leslie Anne Chatterton]

After you have assigned a fixed IP address to your network interface then ping 127.0.0.1 or "ping localhost" - same thing. This will be the lowest level test of your networking configuration.

If it returns a local ping then try the IP's of other computers on your local network. If that works try pinging some websites by name. Try "ping google.com". Many busy websites block ping return as a security measure but Google doesn't seem to at least on this Android Tablet.

Sent from my Motorola Xoom running Ice Cream Sandwich

On Jul 1, 2012 12:31 PM, "Hakan Koseoglu" <[hidden email]> wrote:
> I tend to agree with you on this, but then why isn't it getting an IP
> address when connecting via wifi over USB wifi adapter? I tried on two
> separate known-good access points that I can connect to with other
> equipment.

Not getting an IP via DHCP doesn't mean anything but there might be a
software fault. First, does it work at all? Assign it an IP address by
hand and then try pinging around.

Also you can do this:
hakan@jupiter:17:26:30:~$ cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
iface eth0 inet dhcp

More than once, esp. on my cloned VMs, Ubuntu decides to add a 2nd
card and then forgets all about it.

--
kubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users

--
kubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users

[Hakan Koseoglu-2]

Leslie,

On 1 July 2012 19:37, Leslie Anne Chatterton <[hidden email]> wrote:
> After you have assigned a fixed IP address to your network interface then
> ping 127.0.0.1 or "ping localhost" - same thing. This will be the lowest
> level test of your networking configuration.
>
> If it returns a local ping then try the IP's of other computers on your
> local network. If that works try pinging some websites by name. Try "ping
> google.com". Many busy websites block ping return as a security measure but
> Google doesn't seem to at least on this Android Tablet.

Pinging localhost doesn't mean anything. He should be at least pinging
the router or an other machine in the same network.

--
kubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users

[Leslie Anne Chatterton]

Hi Hakan,

I would respectfully disagree. In diagnosing a problem we start at the simplest point and work out from there.

If pinging localhost works then there is a valid IP address and the TCP/IP stack is functioning properly. If pinging localhost doesn't return any answer then that is where the troubleshooting has to start. There is no use pinging anything else until this is working.

After that has been established as working correctly we move on to the LAN and then the external sites. This checks on DNS etc.

If one jumps ahead and does the last step first and if it fails  then you have to go back to basics anyway. Successful troubleshooting requires a methodical and systematic method of approach. It took me years to learn this and discipline myself to follow it consistently but it always works.

Sent from my Motorola Xoom running Ice Cream Sandwich

On Jul 1, 2012 2:43 PM, "Hakan Koseoglu" <[hidden email]> wrote:

Leslie,

On 1 July 2012 19:37, Leslie Anne Chatterton <[hidden email]> wrote:
> After you have assigned a fixed IP address to your network interface then
> ping 127.0.0.1 or "ping localhost" - same thing. This will be the lowest
> level test of your networking configuration.
>
> If it returns a local ping then try the IP's of other computers on your
> local network. If that works try pinging some websites by name. Try "ping
> google.com". Many busy websites block ping return as a security measure but
> Google doesn't seem to at least on this Android Tablet.

Pinging localhost doesn't mean anything. He should be at least pinging
the router or an other machine in the same network.

--
kubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users

--
kubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users

[Hakan Koseoglu-2]

Leslie,

On 1 July 2012 20:30, Leslie Anne Chatterton <[hidden email]> wrote:
> I would respectfully disagree. In diagnosing a problem we start at the
> simplest point and work out from there.
He had already posted messages with himself pinging localhost. We're
past that point.

--
kubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users

[Leslie Anne Chatterton]

Hi Hakan,

Let's confine our remarks to being helpful to the man with the problem.

Best wishes,

Leslie Anne

> He had already posted messages with himself pinging localhost. We're
> past that point.

--
kubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users

[theuteck]

A few things you could check are if dhcp is added to the
/etc/apparmor.d/disable directory.  When I upgraded a 10.04 VM to
12.04 it would not get an address since Apparmor was blocking dhcp.
To disbale Apparmor from checking DHCP make this link;
ln -s /etc/apparmor.d/sbin.dhclient3 /etc/apparmor.d/disable/

Also look at /etc/udev/rules.d/70-persistent-net.rules and see if it
has a card defined.  Back up the file, then delete the SUBSYSTEM lines
and reboot and udev will redetect the card.

On Sun, Jul 1, 2012 at 4:04 PM, Leslie Anne Chatterton
<[hidden email]> wrote:

> Hi Hakan,
>
> Let's confine our remarks to being helpful to the man with the problem.
>
> Best wishes,
>
> Leslie Anne
>
>> He had already posted messages with himself pinging localhost. We're
>> past that point.
>
>
> --
> kubuntu-users mailing list
> [hidden email]
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/kubuntu-users
>

--
no .sig found
Please restart your browser.

--
kubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users