Networking unreachable with Ubuntu 16.10 Server and J3455B-ITX

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP








up vote
0
down vote

favorite












I have a fresh install of Ubuntu 16.10 (with kernel 4.8) and the network isn't connecting (via Ethernet). The machine is a new J3455B-ITX mobo/CPU combo.



Here's what ifconfig shows:



enp1s0: ///
lo: ///


My /etc/network/interfaces file looks like this:



auto lo
iface lo inet loopback
#
auto enp1s0
iface enp1s0 inet dhcp
netmask 255.255.255.0


Here's the output of services networking status:



Active: failed (Result: timeout)
Starting Raise networking interfaces...
waiting for lock on /run/network/ifstate.enp1s0
networking.service start operation timed out. terminating.
Failed to start Raise network interfaces


I'm stumped. Any ideas?










share|improve this question























  • Do you have a DHCP server available for the enp1s0 interface? What means "netmask ...." in interfaces file as you want to use DHCP configuration?
    – mariaczi
    Apr 18 at 8:09










  • Yes I already have a router on the network that is the DHCP server. The only reason I added the netmask was because I noticed in the logs it was searching for 255.255.255.255.
    – Adam Simpson
    Apr 18 at 11:18










  • To be sure, if you have all required drivers (included firmware files) try to setup static IP (help.ubuntu.com/lts/serverguide/network-configuration.html) and check if you will have access to the internet.
    – mariaczi
    Apr 18 at 11:22










  • The issue there is I’ve never had network access (I installed this last night) so I don’t have a way to know or get what drivers I may need.
    – Adam Simpson
    Apr 18 at 12:05










  • Did you try setup static IP for network interface?
    – mariaczi
    Apr 18 at 12:43














up vote
0
down vote

favorite












I have a fresh install of Ubuntu 16.10 (with kernel 4.8) and the network isn't connecting (via Ethernet). The machine is a new J3455B-ITX mobo/CPU combo.



Here's what ifconfig shows:



enp1s0: ///
lo: ///


My /etc/network/interfaces file looks like this:



auto lo
iface lo inet loopback
#
auto enp1s0
iface enp1s0 inet dhcp
netmask 255.255.255.0


Here's the output of services networking status:



Active: failed (Result: timeout)
Starting Raise networking interfaces...
waiting for lock on /run/network/ifstate.enp1s0
networking.service start operation timed out. terminating.
Failed to start Raise network interfaces


I'm stumped. Any ideas?










share|improve this question























  • Do you have a DHCP server available for the enp1s0 interface? What means "netmask ...." in interfaces file as you want to use DHCP configuration?
    – mariaczi
    Apr 18 at 8:09










  • Yes I already have a router on the network that is the DHCP server. The only reason I added the netmask was because I noticed in the logs it was searching for 255.255.255.255.
    – Adam Simpson
    Apr 18 at 11:18










  • To be sure, if you have all required drivers (included firmware files) try to setup static IP (help.ubuntu.com/lts/serverguide/network-configuration.html) and check if you will have access to the internet.
    – mariaczi
    Apr 18 at 11:22










  • The issue there is I’ve never had network access (I installed this last night) so I don’t have a way to know or get what drivers I may need.
    – Adam Simpson
    Apr 18 at 12:05










  • Did you try setup static IP for network interface?
    – mariaczi
    Apr 18 at 12:43












up vote
0
down vote

favorite









up vote
0
down vote

favorite











I have a fresh install of Ubuntu 16.10 (with kernel 4.8) and the network isn't connecting (via Ethernet). The machine is a new J3455B-ITX mobo/CPU combo.



Here's what ifconfig shows:



enp1s0: ///
lo: ///


My /etc/network/interfaces file looks like this:



auto lo
iface lo inet loopback
#
auto enp1s0
iface enp1s0 inet dhcp
netmask 255.255.255.0


Here's the output of services networking status:



Active: failed (Result: timeout)
Starting Raise networking interfaces...
waiting for lock on /run/network/ifstate.enp1s0
networking.service start operation timed out. terminating.
Failed to start Raise network interfaces


I'm stumped. Any ideas?










share|improve this question















I have a fresh install of Ubuntu 16.10 (with kernel 4.8) and the network isn't connecting (via Ethernet). The machine is a new J3455B-ITX mobo/CPU combo.



Here's what ifconfig shows:



enp1s0: ///
lo: ///


My /etc/network/interfaces file looks like this:



auto lo
iface lo inet loopback
#
auto enp1s0
iface enp1s0 inet dhcp
netmask 255.255.255.0


Here's the output of services networking status:



Active: failed (Result: timeout)
Starting Raise networking interfaces...
waiting for lock on /run/network/ifstate.enp1s0
networking.service start operation timed out. terminating.
Failed to start Raise network interfaces


I'm stumped. Any ideas?







networking server ethernet dhcp






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Apr 20 at 19:31









Fabby

24.4k1352153




24.4k1352153










asked Apr 18 at 4:15









Adam Simpson

535




535











  • Do you have a DHCP server available for the enp1s0 interface? What means "netmask ...." in interfaces file as you want to use DHCP configuration?
    – mariaczi
    Apr 18 at 8:09










  • Yes I already have a router on the network that is the DHCP server. The only reason I added the netmask was because I noticed in the logs it was searching for 255.255.255.255.
    – Adam Simpson
    Apr 18 at 11:18










  • To be sure, if you have all required drivers (included firmware files) try to setup static IP (help.ubuntu.com/lts/serverguide/network-configuration.html) and check if you will have access to the internet.
    – mariaczi
    Apr 18 at 11:22










  • The issue there is I’ve never had network access (I installed this last night) so I don’t have a way to know or get what drivers I may need.
    – Adam Simpson
    Apr 18 at 12:05










  • Did you try setup static IP for network interface?
    – mariaczi
    Apr 18 at 12:43
















  • Do you have a DHCP server available for the enp1s0 interface? What means "netmask ...." in interfaces file as you want to use DHCP configuration?
    – mariaczi
    Apr 18 at 8:09










  • Yes I already have a router on the network that is the DHCP server. The only reason I added the netmask was because I noticed in the logs it was searching for 255.255.255.255.
    – Adam Simpson
    Apr 18 at 11:18










  • To be sure, if you have all required drivers (included firmware files) try to setup static IP (help.ubuntu.com/lts/serverguide/network-configuration.html) and check if you will have access to the internet.
    – mariaczi
    Apr 18 at 11:22










  • The issue there is I’ve never had network access (I installed this last night) so I don’t have a way to know or get what drivers I may need.
    – Adam Simpson
    Apr 18 at 12:05










  • Did you try setup static IP for network interface?
    – mariaczi
    Apr 18 at 12:43















Do you have a DHCP server available for the enp1s0 interface? What means "netmask ...." in interfaces file as you want to use DHCP configuration?
– mariaczi
Apr 18 at 8:09




Do you have a DHCP server available for the enp1s0 interface? What means "netmask ...." in interfaces file as you want to use DHCP configuration?
– mariaczi
Apr 18 at 8:09












Yes I already have a router on the network that is the DHCP server. The only reason I added the netmask was because I noticed in the logs it was searching for 255.255.255.255.
– Adam Simpson
Apr 18 at 11:18




Yes I already have a router on the network that is the DHCP server. The only reason I added the netmask was because I noticed in the logs it was searching for 255.255.255.255.
– Adam Simpson
Apr 18 at 11:18












To be sure, if you have all required drivers (included firmware files) try to setup static IP (help.ubuntu.com/lts/serverguide/network-configuration.html) and check if you will have access to the internet.
– mariaczi
Apr 18 at 11:22




To be sure, if you have all required drivers (included firmware files) try to setup static IP (help.ubuntu.com/lts/serverguide/network-configuration.html) and check if you will have access to the internet.
– mariaczi
Apr 18 at 11:22












The issue there is I’ve never had network access (I installed this last night) so I don’t have a way to know or get what drivers I may need.
– Adam Simpson
Apr 18 at 12:05




The issue there is I’ve never had network access (I installed this last night) so I don’t have a way to know or get what drivers I may need.
– Adam Simpson
Apr 18 at 12:05












Did you try setup static IP for network interface?
– mariaczi
Apr 18 at 12:43




Did you try setup static IP for network interface?
– mariaczi
Apr 18 at 12:43










1 Answer
1






active

oldest

votes

















up vote
1
down vote



accepted
+50










Seems that your computer is having two network cards, enp2s0 = RTL8168g/8111g, enp1s0 = Intel(R) PRO/1000



Are you completely sure that your ethernet cable is on Intel, not the realtek?



Seems that your cable is connected to enp2s0 not enp1s0. I made that conclusion of this line you show (see the no-carrier flag):



2: enp2s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 70:85:c2:4b:68:0a brd ff:ff:ff:ff:ff:ff
3: enp1s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
link/ether 00:1b:21:39:ed:64 brd ff:ff:ff:ff:ff:ff


I Suggest you try to replace your networking config to raise interface as enp2s0 with configuration like this:



auto lo
iface lo inet loopback
#
auto enp2s0
iface enp2s0 inet dhcp


Actually you don't need netmask, dhcp broadcast to 255.255.255.255 should go to every device on your layer2 network.






share|improve this answer




















  • Ah you nailed it! Thank you so much! For my own edification what does 'no-carrier' mean? I'll award the bounty when it allows me to...
    – Adam Simpson
    Apr 21 at 16:51










  • No carrier means there is no active line connected to your network card.
    – Pasi Suominen
    Apr 26 at 14:49










Your Answer







StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "89"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1025994%2fnetworking-unreachable-with-ubuntu-16-10-server-and-j3455b-itx%23new-answer', 'question_page');

);

Post as a guest






























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
1
down vote



accepted
+50










Seems that your computer is having two network cards, enp2s0 = RTL8168g/8111g, enp1s0 = Intel(R) PRO/1000



Are you completely sure that your ethernet cable is on Intel, not the realtek?



Seems that your cable is connected to enp2s0 not enp1s0. I made that conclusion of this line you show (see the no-carrier flag):



2: enp2s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 70:85:c2:4b:68:0a brd ff:ff:ff:ff:ff:ff
3: enp1s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
link/ether 00:1b:21:39:ed:64 brd ff:ff:ff:ff:ff:ff


I Suggest you try to replace your networking config to raise interface as enp2s0 with configuration like this:



auto lo
iface lo inet loopback
#
auto enp2s0
iface enp2s0 inet dhcp


Actually you don't need netmask, dhcp broadcast to 255.255.255.255 should go to every device on your layer2 network.






share|improve this answer




















  • Ah you nailed it! Thank you so much! For my own edification what does 'no-carrier' mean? I'll award the bounty when it allows me to...
    – Adam Simpson
    Apr 21 at 16:51










  • No carrier means there is no active line connected to your network card.
    – Pasi Suominen
    Apr 26 at 14:49














up vote
1
down vote



accepted
+50










Seems that your computer is having two network cards, enp2s0 = RTL8168g/8111g, enp1s0 = Intel(R) PRO/1000



Are you completely sure that your ethernet cable is on Intel, not the realtek?



Seems that your cable is connected to enp2s0 not enp1s0. I made that conclusion of this line you show (see the no-carrier flag):



2: enp2s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 70:85:c2:4b:68:0a brd ff:ff:ff:ff:ff:ff
3: enp1s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
link/ether 00:1b:21:39:ed:64 brd ff:ff:ff:ff:ff:ff


I Suggest you try to replace your networking config to raise interface as enp2s0 with configuration like this:



auto lo
iface lo inet loopback
#
auto enp2s0
iface enp2s0 inet dhcp


Actually you don't need netmask, dhcp broadcast to 255.255.255.255 should go to every device on your layer2 network.






share|improve this answer




















  • Ah you nailed it! Thank you so much! For my own edification what does 'no-carrier' mean? I'll award the bounty when it allows me to...
    – Adam Simpson
    Apr 21 at 16:51










  • No carrier means there is no active line connected to your network card.
    – Pasi Suominen
    Apr 26 at 14:49












up vote
1
down vote



accepted
+50







up vote
1
down vote



accepted
+50




+50




Seems that your computer is having two network cards, enp2s0 = RTL8168g/8111g, enp1s0 = Intel(R) PRO/1000



Are you completely sure that your ethernet cable is on Intel, not the realtek?



Seems that your cable is connected to enp2s0 not enp1s0. I made that conclusion of this line you show (see the no-carrier flag):



2: enp2s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 70:85:c2:4b:68:0a brd ff:ff:ff:ff:ff:ff
3: enp1s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
link/ether 00:1b:21:39:ed:64 brd ff:ff:ff:ff:ff:ff


I Suggest you try to replace your networking config to raise interface as enp2s0 with configuration like this:



auto lo
iface lo inet loopback
#
auto enp2s0
iface enp2s0 inet dhcp


Actually you don't need netmask, dhcp broadcast to 255.255.255.255 should go to every device on your layer2 network.






share|improve this answer












Seems that your computer is having two network cards, enp2s0 = RTL8168g/8111g, enp1s0 = Intel(R) PRO/1000



Are you completely sure that your ethernet cable is on Intel, not the realtek?



Seems that your cable is connected to enp2s0 not enp1s0. I made that conclusion of this line you show (see the no-carrier flag):



2: enp2s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 70:85:c2:4b:68:0a brd ff:ff:ff:ff:ff:ff
3: enp1s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
link/ether 00:1b:21:39:ed:64 brd ff:ff:ff:ff:ff:ff


I Suggest you try to replace your networking config to raise interface as enp2s0 with configuration like this:



auto lo
iface lo inet loopback
#
auto enp2s0
iface enp2s0 inet dhcp


Actually you don't need netmask, dhcp broadcast to 255.255.255.255 should go to every device on your layer2 network.







share|improve this answer












share|improve this answer



share|improve this answer










answered Apr 21 at 16:13









Pasi Suominen

44526




44526











  • Ah you nailed it! Thank you so much! For my own edification what does 'no-carrier' mean? I'll award the bounty when it allows me to...
    – Adam Simpson
    Apr 21 at 16:51










  • No carrier means there is no active line connected to your network card.
    – Pasi Suominen
    Apr 26 at 14:49
















  • Ah you nailed it! Thank you so much! For my own edification what does 'no-carrier' mean? I'll award the bounty when it allows me to...
    – Adam Simpson
    Apr 21 at 16:51










  • No carrier means there is no active line connected to your network card.
    – Pasi Suominen
    Apr 26 at 14:49















Ah you nailed it! Thank you so much! For my own edification what does 'no-carrier' mean? I'll award the bounty when it allows me to...
– Adam Simpson
Apr 21 at 16:51




Ah you nailed it! Thank you so much! For my own edification what does 'no-carrier' mean? I'll award the bounty when it allows me to...
– Adam Simpson
Apr 21 at 16:51












No carrier means there is no active line connected to your network card.
– Pasi Suominen
Apr 26 at 14:49




No carrier means there is no active line connected to your network card.
– Pasi Suominen
Apr 26 at 14:49

















 

draft saved


draft discarded















































 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1025994%2fnetworking-unreachable-with-ubuntu-16-10-server-and-j3455b-itx%23new-answer', 'question_page');

);

Post as a guest













































































Popular posts from this blog

pylint3 and pip3 broken

Missing snmpget and snmpwalk

How to enroll fingerprints to Ubuntu 17.10 with VFS491