0

I am running a remote server a VPS, all was well,

Upgraded to Ubuntu 16.04 and immediately my ssh (putty) stopped allowing me access, it just can't find server, cannot ping... it says

network unreachable

Checked all firewalls and all exactly same as before,

All firewalls open on correct ports, all software runs correctly on reboot, its all working except I cannot connect to server by any means, I cannot SSH,

When running service networking status I get the following error report,

networking failure error report

It is failing to raise networking services and so I cannot access server, it also lists dhclient failure,

My Hosting provider provides a terminal interface so I can run commands luckily,

Please help as I have tried ALL articles on net for this including here and no luck, I now have a server which is working fine except neither I or anyone else can ever contact it,

The contents of my /etc/network/interfaces file are correct,

Loopback interface
auto lo eth0
iface lo inet loopback

Primary Network Interface
auto eth0
iface eth0 inet dhcp

please advise as I am not willing to start from scratch with server and don't know why Ubuntu has not fixed this ongoing bug which many people have reported,

Hope you can help?

  • Hi, I ran ifconfig results below, then changed /etc/network/interfaces file, firstly to docker0 then to veth1367b5d to try raising them, and ran ifup and ifdown exactly as you suggested for each one in turn to test them: !Test results and error message docker is a container running for my discourse forum, and two other Ethernet listed, I tried docker and then one of ethernets but neither produced anything but errors and would not raised network services, any help would be appreciated thank you – dredgerman Aug 20 '16 at 5:23
4

In 16.04, because of persistent naming, your interface is probably no longer eth0. Check:

ifconfig

For example, my ethernet interface is now enp0s25. Correct your /etc/network/interfaces file as needed and then:

sudo ifdown enp0s25 && sudo ifup enp0s25

Of course, substitue your interface name as needed.

Why is enp#s# in stead of eth# ? Whats the meaning of enp#s#?

  • 1
    chili, +1, but i think it's time to start telling people to use ip as a must :) – heemayl Aug 19 '16 at 19:38
  • 1
    @heemayl Old dogs and new tricks, etc.! – chili555 Aug 19 '16 at 19:40
  • Thank you will report back, appreciate you taking time to help! – dredgerman Aug 19 '16 at 22:13
  • I have added result of following the suggested steps above, still no luck getting it working, won't raise network service... – dredgerman Aug 19 '16 at 22:37
  • Hi, I ran ifconfig results below, then changed /etc/network/interfaces file, firstly to docker0 then to veth1367b5d to try raising them, and ran ifup and ifdown exactly as you suggested for each one in turn to test them: Results of your instructions docker is a container running for my discourse forum, and two other Ethernet listed, I tried docker0 and then one of ethernets but neither produced anything but errors (see image above) and would not raise network services, any help would be appreciated thank you – dredgerman Aug 20 '16 at 5:56

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.