Ethernet not working after fresh install of 16.04 64 bit

As per title. Just re-installed 16.04 after putting a partition of Win7 (yes…I feel dirty even mentioning MS) on main drive for a particular program I need (to do with photogrammetry). Reinstalled UM 16.04 on empty space. All went well apart form ethernet. It just wont connect.

The ethernet card in question is listed as:

realtek rtl8111/8168/8411pci exress gigabit ethernet controller

No idea what is going wrong. This card has worked in all previous editions of UM and also worked in my immediately previous installation of 16.04

Anybody any ideas?

It’s quite a big deal for me for slightly convoluted reasons: I use Virgin optic fibre for my broadband service. However, Virgin have a nasty practice (either by intentional policy or by technical complacency) of providing a really crappy broadband speeds for any domestic Linux machine directly connected to the service. By this I mean, instead of the advertised speeds of around 70 to 100 mbps, I get around 12 mbps. I have got around this by connecting my Linux machine to an old laptop running Win7. The laptop is connected to the router via wireless and gets the advertised speeds. I then use my laptop as a shared internet connection to my Linux machine via ethernet cable. That way, my Linux machine gets the advertised speeds because, presumably, the router only sees the windows laptop.

At the moment, i am having to rely on my wireless connection on my Linux machine and am on around 12mbps.

Help!

I also have another ethernet card on my Linux machine, which I sometimes employ (but not presently) as an internal adapter for an LTSP network. This one is not working either. It is also a realtek card. Again, this worked on my last installation of UM 16.04 plus all other previous UM editions. It is listed as:

realtek rtl8111/8168/8411pci exress gigabit ethernet controller (tg-3468 gigabit pci express network adapter)

This is a copy of my log:

May 4 21:07:16 server NetworkManager[829]: [1462392436.8206] dhcp4 (enp5s0): state changed unknown -> timeout
May 4 21:07:16 server NetworkManager[829]: [1462392436.8368] dhcp4 (enp5s0): canceled DHCP transaction, DHCP client pid 2233
May 4 21:07:16 server NetworkManager[829]: [1462392436.8369] dhcp4 (enp5s0): state changed timeout -> done
May 4 21:07:16 server NetworkManager[829]: [1462392436.8374] device (enp5s0): state change: ip-config -> failed (reason ‘ip-config-unavailable’) [70 120 5]
May 4 21:07:16 server NetworkManager[829]: [1462392436.8383] device (enp5s0): Activation: failed for connection ‘Wired connection 2’
May 4 21:07:16 server NetworkManager[829]: [1462392436.8397] device (enp5s0): state change: failed -> disconnected (reason ‘none’) [120 30 0]
May 4 21:07:16 server NetworkManager[829]: [1462392436.8464] policy: auto-activating connection ‘Wired connection 2’
May 4 21:07:16 server NetworkManager[829]: [1462392436.8482] device (enp5s0): Activation: starting connection ‘Wired connection 2’ (fdc49439-0a9a-4e7a-8f6e-ee857246ca8f)
May 4 21:07:16 server NetworkManager[829]: [1462392436.8486] device (enp5s0): state change: disconnected -> prepare (reason ‘none’) [30 40 0]
May 4 21:07:16 server NetworkManager[829]: [1462392436.8508] device (enp5s0): state change: prepare -> config (reason ‘none’) [40 50 0]
May 4 21:07:16 server NetworkManager[829]: [1462392436.8524] device (enp5s0): state change: config -> ip-config (reason ‘none’) [50 70 0]
May 4 21:07:16 server NetworkManager[829]: [1462392436.8534] dhcp4 (enp5s0): activation: beginning transaction (timeout in 45 seconds)
May 4 21:07:16 server NetworkManager[829]: [1462392436.8576] dhcp4 (enp5s0): dhclient started with pid 2307
May 4 21:07:37 server NetworkManager[829]: [1462392457.9606] device (enp5s0): state change: ip-config -> deactivating (reason ‘user-requested’) [70 110 39]
May 4 21:07:37 server NetworkManager[829]: [1462392457.9613] audit: op=“device-disconnect” interface=“enp5s0” ifindex=3 pid=1559 uid=1000 result=“success”

It looks like the device is working, but just can’t “connect” to your network for some reason. Looks like a DHCP problem (which negotiates the IP address) - you could try restarting the router if you haven’t already.

Are you able to connect by manually specifying an IP address, gateway and netmask?

2 Likes

I’ll go and restart the router and report back

FIXED!

Reset router and the bad thing went away…:grin:

Speed back up into the late 70s mbps

What a bloody numpty I am for not doing that in the first place!

Cheers lah7

2 Likes