Network manager sometimes don't connect to network

What is the output of:

sudo lshw -C network; lsb_release -a; uname -a; sudo rfkill list; dmesg | grep -i firm

Thanks

I need to show you the output when the problem comes out, or it is doesn't matter?

For normal situation it is:

simplehuman@simplehuman-System-Product-Name:~$ sudo lshw -C network; lsb_release -a; uname -a; sudo rfkill list; dmesg | grep -i firm
[sudo] password for simplehuman:
PCI (sysfs)

  *-network
       описание: Ethernet interface
       продукт: RTL8111/8168B PCI Express Gigabit Ethernet controller
       производитель: Realtek Semiconductor Co., Ltd.
       физический ID: 0
       сведения о шине: pci@0000:03:00.0
       логическое имя: eth0
       версия: 01
       серийный №: 00:1f:1f:72:29:d6
       размер: 100Mbit/s
       capacity: 1Gbit/s
       разрядность: 64 bits
       частота: 33MHz
       возможности: pm vpd msi pciexpress bus_master cap_list rom ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
       кофигурация: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=full ip=217.147.162.205 latency=0 link=yes multicast=yes port=MII speed=100Mbit/s
       ресурсы: IRQ:77 ioport:a800(размер=256) память:f9fff000-f9ffffff память:f9fc0000-f9fdffff
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 12.10
Release: 12.10
Codename: quantal
Linux simplehuman-System-Product-Name 3.5.0-17-generic #28-Ubuntu SMP Tue Oct 9 19:31:23 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

What is the output of:

sudo dmidecode -t 1

Thanks

simplehuman@simplehuman-System-Product-Name:~$ sudo dmidecode -t 1
[sudo] password for simplehuman:
# dmidecode 2.11
SMBIOS 2.5 present.

Handle 0x0001, DMI type 1, 27 bytes
System Information
 Manufacturer: System manufacturer
 Product Name: System Product Name
 Version: System Version
 Serial Number: System Serial Number
 UUID: 6020001F-C600-0008-B86B-BCAEC52CC2E5
 Wake-up Type: Power Switch
 SKU Number: To Be Filled By O.E.M.
 Family: To Be Filled By O.E.M.

In 12.04 sometimes disabling, wait for 5-10 seconds and enabling networking helps. But in 12.10 it doesn't help anymore.

Is this a home built PC?

Yes, it is. And I don't have this problem on 9.10 - 10.10 Ubuntu versions. And on Windows XP and Windows 7. So I don't think it is a hardware problem. Also I was faced with this problem on some laptops on Ubuntu 12.04.

I'd boot to the Karmic live CD and run:

sudo lshw -C network

And add the output to the bug report so the bug fixing guy(s) can see what wifi chip you have

The problem is not with wifi, it is with wired network. So maybe you don't understand the problem and I need to add another information?

So I still need an answer

The wired connection has an IP of 217.147.162.205.If you run:

ping -c 4 8.8.8.8

Does it ping ok?

simplehuman@simplehuman-System-Product-Name:~$ ping -c 4 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_req=1 ttl=50 time=31.2 ms
64 bytes from 8.8.8.8: icmp_req=2 ttl=50 time=31.1 ms
64 bytes from 8.8.8.8: icmp_req=3 ttl=50 time=31.3 ms
64 bytes from 8.8.8.8: icmp_req=4 ttl=50 time=30.9 ms

--- 8.8.8.8 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3000ms
rtt min/avg/max/mdev = 30.986/31.181/31.333/0.184 ms

Brilliant, your only issue is DNS then :)

run:

echo "nameserver 8.8.8.8" | sudo tee /etc/resolvconf/resolv.conf.d/tail > /dev/null

Reboot to test

I will after finishing my work. What result I need to observe? That my wired network won't connect, or it will connect?
The issue is pretty random so that's why I am asking (~10-20% of boot times).

Just try we access. It will work :)

This doesn't solved the problem... after "echo "nameserver 8.8.8.8" | sudo tee /etc/resolvconf/resolv.conf.d/tail > /dev/null" and booting today - Ubuntu doesn't want connect to wired network...

This question was expired because it remained in the 'Open' state without activity for the last 15 days.