16.04 - Ubuntu (dual boot Windows) Ethernet Not Connecting/Detecting - Ask Ubuntu

i'm new linux , installed ubuntu 16.04 lts windows 10. (i've installed ubuntu on different partition windows, if of help). set ubuntu ethernet not being detected , connected. same works fine when on windows. i've searched other questions on site none of them solved problem. glad if helped me out here! thanks!

okay, user put bounty on question. unable comment due lack of reputation. think should take reins of question hands. so, describe system's properties.

i had installed ubuntu 16.04 on separate partition in parallel windows 10. laptop lenovo z51-70. problem ethernet not connecting on ubuntu.

this result of "ipconfig" on windows.

windows ip configuration   wireless lan adapter local area connection* 2:     media state . . . . . . . . . . . : media disconnected    connection-specific dns suffix  . :  ethernet adapter ethernet:     connection-specific dns suffix  . :    link-local ipv6 address . . . . . : fe80::d01f:a297:5f9c:80f%4    ipv4 address. . . . . . . . . . . : 10.9.73.16    subnet mask . . . . . . . . . . . : 255.255.224.0    default gateway . . . . . . . . . : 10.9.70.250  ethernet adapter ethernet 2:     media state . . . . . . . . . . . : media disconnected    connection-specific dns suffix  . :  wireless lan adapter wi-fi:     media state . . . . . . . . . . . : media disconnected    connection-specific dns suffix  . :  ethernet adapter bluetooth network connection:     media state . . . . . . . . . . . : media disconnected    connection-specific dns suffix  . :  tunnel adapter isatap.{5f5a44d4-1648-49e4-8c87-54cb2ab99206}:     media state . . . . . . . . . . . : media disconnected    connection-specific dns suffix  . :  tunnel adapter local area connection* 12:     media state . . . . . . . . . . . : media disconnected    connection-specific dns suffix  . : 

also, add rebooting didn't help. restarting network-manager didn't help. giving ip on windows before booting ubuntu didn't help.

the output of script @davidfoerster mentioned @ wireless-info.txt.

the bible of network connection problems

the best place start favorite bible of network connections (wiki.archlinux.org - enable wol in windows driver) archlinux.

although there dozens of things can try:

1 check connection 2 set hostname 2.1 local network hostname resolution 3 device driver 3.1 check status 3.2 load module 4 network interfaces 4.1 device names 4.1.1 current device names 4.1.2 change device name 4.1.3 reverting traditional device names 4.2 set device mtu , queue length 4.3 enabling , disabling network interfaces 5 configure ip address 5.1 dynamic ip address 5.1.1 systemd-networkd 5.1.2 dhcpcd 5.1.3 dhclient 5.1.4 netctl 5.2 static ip address 5.2.1 netctl 5.2.2 systemd-networkd 5.2.3 dhcpcd 5.2.4 manual assignment 5.2.5 calculating addresses 6 tips , tricks 6.1 ifplugd laptops 6.2 bonding or lag 6.3 ip address aliasing 6.3.1 example 6.4 change mac/hardware address 6.5 internet sharing 6.6 router configuration 6.7 promiscuous mode 7 troubleshooting 7.1 swapping computers on cable modem 7.2 tcp window scaling problem 7.2.1 how diagnose problem 7.2.2 ways of fixing 7.2.2.1 bad 7.2.2.2 7.2.2.3 best 7.2.3 more 7.3 realtek no link / wol problem 7.3.1 enable nic directly in linux 7.3.2 rollback/change windows driver 7.3.3 enable wol in windows driver 7.3.4 newer realtek linux driver 7.3.5 enable lan boot rom in bios/cmos 7.4 no interface atheros chipsets 7.5 broadcom bcm57780 7.6 realtek rtl8111/8168b 7.7 gigabyte motherboard realtek 8111/8168/8411 8 see 

we'll start based on limited information given network card works in windows not ubuntu. outlined in next section.

windows disables nic (network interface card) on shutdown

when bios feature known wake on lan (wol) disabled nic have no blinking led's indicating connection , no connection router. windows can disable nic on shutdown. prevent happening on realtek cards under windows xp (example) use:

right click computer , choose "properties" --> "hardware" tab   --> device manager  --> network adapters   --> "double click" realtek ...    --> advanced tab     --> wake-on-lan after shutdown      --> enable 

this may not solve op problem because exact details not given. there high degree of confidence 1 of other solutions on web page solve problem.