Ubuntu 17.10 Server running Ubuntu Desktop. Network Manager will not detect Ethernet
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgO9GURib1T8z7lCwjOGLQaGtrueEthgQ8LO42ZX8cOfTqDK4jvDDpKkLFwf2J49kYCMNW7d4ABih_XCb_2UXdq5fPJDkoyg7-8g_YfRUot-XnaXkNYycsNp7lA5_TW9td0FFpLQ2APzKcZ/s1600/1.jpg)
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhYQ0N5W1qAOxLP7t7iOM6O6AzbZnkXUy16s7P_CWfOb5UbTQY_aDsc727chyphenhyphen5W4IppVNernMMQeaUFTB_rFzAd95_CDt-tnwN-nBx6JyUp2duGjPaL5-VgNO41AVsA_vu30EJcipdDG409/s400/Clash+Royale+CLAN+TAG%2523URR8PPP.png)
up vote
2
down vote
favorite
I know this question has been asked several times from Ubuntu 17.04 Server and previous. The Ubuntu Desktop, once installed, will not detect and manage the Ethernet Adapter.
I have stepped thru the previously reported fix here which has not fixed this issue for a new 17.10 Server running Ubuntu Desktop (both Gnome and Budgie)
Ethernet device not managed
Points to note.
- This Ubuntu 17.10 Server is a VirtualBox VM running on a Windoze 7 Host.
- the VM has the NIC setting on NAT. (I don't want to expose this VM on the main router DHCP scope as it's on a work machine/network)
the Ubuntu 17.10 server does have functioning network but just CANNOT be managed with the Ubuntu desktop Network Manager
I'd basically like to tweak what's needed on the Ubuntu 17.10 Server so the Network Manager will detect the network connection.
config files in the Ubuntu 17.10 Server
/etc/network/interfaces
:
# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)
# Generated by debian-installer.
# The loopback interface
auto lo
iface lo inet loopback
/etc/NetworkManager/NetworkManager.conf
:
[main]
plugins=ifupdown,keyfile
[ifupdown]
managed=true
[device]
wifi.scan-rand-mac-address=no
/etc/netplan/01-netcfg.yaml
:
# This file describes the network interfaces available on your system
# For more information, see netplan(5).
network:
version: 2
renderer: networkd
ethernets:
enp0s3:
dhcp4: yes
Whats nice is I'm able to snapshot the VM, play, and quickly revert if something is totally munched.
I'm thinking enp0s3
needs to be listed in the /etc/NetworkManager/NetworkManager.conf
file?
server network-manager 17.10
add a comment |Â
up vote
2
down vote
favorite
I know this question has been asked several times from Ubuntu 17.04 Server and previous. The Ubuntu Desktop, once installed, will not detect and manage the Ethernet Adapter.
I have stepped thru the previously reported fix here which has not fixed this issue for a new 17.10 Server running Ubuntu Desktop (both Gnome and Budgie)
Ethernet device not managed
Points to note.
- This Ubuntu 17.10 Server is a VirtualBox VM running on a Windoze 7 Host.
- the VM has the NIC setting on NAT. (I don't want to expose this VM on the main router DHCP scope as it's on a work machine/network)
the Ubuntu 17.10 server does have functioning network but just CANNOT be managed with the Ubuntu desktop Network Manager
I'd basically like to tweak what's needed on the Ubuntu 17.10 Server so the Network Manager will detect the network connection.
config files in the Ubuntu 17.10 Server
/etc/network/interfaces
:
# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)
# Generated by debian-installer.
# The loopback interface
auto lo
iface lo inet loopback
/etc/NetworkManager/NetworkManager.conf
:
[main]
plugins=ifupdown,keyfile
[ifupdown]
managed=true
[device]
wifi.scan-rand-mac-address=no
/etc/netplan/01-netcfg.yaml
:
# This file describes the network interfaces available on your system
# For more information, see netplan(5).
network:
version: 2
renderer: networkd
ethernets:
enp0s3:
dhcp4: yes
Whats nice is I'm able to snapshot the VM, play, and quickly revert if something is totally munched.
I'm thinking enp0s3
needs to be listed in the /etc/NetworkManager/NetworkManager.conf
file?
server network-manager 17.10
add a comment |Â
up vote
2
down vote
favorite
up vote
2
down vote
favorite
I know this question has been asked several times from Ubuntu 17.04 Server and previous. The Ubuntu Desktop, once installed, will not detect and manage the Ethernet Adapter.
I have stepped thru the previously reported fix here which has not fixed this issue for a new 17.10 Server running Ubuntu Desktop (both Gnome and Budgie)
Ethernet device not managed
Points to note.
- This Ubuntu 17.10 Server is a VirtualBox VM running on a Windoze 7 Host.
- the VM has the NIC setting on NAT. (I don't want to expose this VM on the main router DHCP scope as it's on a work machine/network)
the Ubuntu 17.10 server does have functioning network but just CANNOT be managed with the Ubuntu desktop Network Manager
I'd basically like to tweak what's needed on the Ubuntu 17.10 Server so the Network Manager will detect the network connection.
config files in the Ubuntu 17.10 Server
/etc/network/interfaces
:
# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)
# Generated by debian-installer.
# The loopback interface
auto lo
iface lo inet loopback
/etc/NetworkManager/NetworkManager.conf
:
[main]
plugins=ifupdown,keyfile
[ifupdown]
managed=true
[device]
wifi.scan-rand-mac-address=no
/etc/netplan/01-netcfg.yaml
:
# This file describes the network interfaces available on your system
# For more information, see netplan(5).
network:
version: 2
renderer: networkd
ethernets:
enp0s3:
dhcp4: yes
Whats nice is I'm able to snapshot the VM, play, and quickly revert if something is totally munched.
I'm thinking enp0s3
needs to be listed in the /etc/NetworkManager/NetworkManager.conf
file?
server network-manager 17.10
I know this question has been asked several times from Ubuntu 17.04 Server and previous. The Ubuntu Desktop, once installed, will not detect and manage the Ethernet Adapter.
I have stepped thru the previously reported fix here which has not fixed this issue for a new 17.10 Server running Ubuntu Desktop (both Gnome and Budgie)
Ethernet device not managed
Points to note.
- This Ubuntu 17.10 Server is a VirtualBox VM running on a Windoze 7 Host.
- the VM has the NIC setting on NAT. (I don't want to expose this VM on the main router DHCP scope as it's on a work machine/network)
the Ubuntu 17.10 server does have functioning network but just CANNOT be managed with the Ubuntu desktop Network Manager
I'd basically like to tweak what's needed on the Ubuntu 17.10 Server so the Network Manager will detect the network connection.
config files in the Ubuntu 17.10 Server
/etc/network/interfaces
:
# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)
# Generated by debian-installer.
# The loopback interface
auto lo
iface lo inet loopback
/etc/NetworkManager/NetworkManager.conf
:
[main]
plugins=ifupdown,keyfile
[ifupdown]
managed=true
[device]
wifi.scan-rand-mac-address=no
/etc/netplan/01-netcfg.yaml
:
# This file describes the network interfaces available on your system
# For more information, see netplan(5).
network:
version: 2
renderer: networkd
ethernets:
enp0s3:
dhcp4: yes
Whats nice is I'm able to snapshot the VM, play, and quickly revert if something is totally munched.
I'm thinking enp0s3
needs to be listed in the /etc/NetworkManager/NetworkManager.conf
file?
server network-manager 17.10
server network-manager 17.10
edited Feb 26 at 14:41
muru
130k19274467
130k19274467
asked Feb 26 at 14:38
![](https://i.stack.imgur.com/81rb9.jpg?s=32&g=1)
![](https://i.stack.imgur.com/81rb9.jpg?s=32&g=1)
Josho
153
153
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
2
down vote
accepted
If you want Network Manager to handle networking, I suggest that you change the netplan file:
sudo mv /etc/netplan/01-netcfg.yaml /etc/netplan/01-network-manager-all.yaml
Then change the file:
sudo nano /etc/netplan/01-network-manager-all.yaml
Change the file to read:
# Let NetworkManager manage all devices on this system
network:
version: 2
renderer: NetworkManager
Save and close the text editor. Next:
sudo netplan apply
sudo service network-manager restart
Any improvement? It may take a reboot.
No reboot required. Worked perfectly
â Josho
Feb 26 at 15:15
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
accepted
If you want Network Manager to handle networking, I suggest that you change the netplan file:
sudo mv /etc/netplan/01-netcfg.yaml /etc/netplan/01-network-manager-all.yaml
Then change the file:
sudo nano /etc/netplan/01-network-manager-all.yaml
Change the file to read:
# Let NetworkManager manage all devices on this system
network:
version: 2
renderer: NetworkManager
Save and close the text editor. Next:
sudo netplan apply
sudo service network-manager restart
Any improvement? It may take a reboot.
No reboot required. Worked perfectly
â Josho
Feb 26 at 15:15
add a comment |Â
up vote
2
down vote
accepted
If you want Network Manager to handle networking, I suggest that you change the netplan file:
sudo mv /etc/netplan/01-netcfg.yaml /etc/netplan/01-network-manager-all.yaml
Then change the file:
sudo nano /etc/netplan/01-network-manager-all.yaml
Change the file to read:
# Let NetworkManager manage all devices on this system
network:
version: 2
renderer: NetworkManager
Save and close the text editor. Next:
sudo netplan apply
sudo service network-manager restart
Any improvement? It may take a reboot.
No reboot required. Worked perfectly
â Josho
Feb 26 at 15:15
add a comment |Â
up vote
2
down vote
accepted
up vote
2
down vote
accepted
If you want Network Manager to handle networking, I suggest that you change the netplan file:
sudo mv /etc/netplan/01-netcfg.yaml /etc/netplan/01-network-manager-all.yaml
Then change the file:
sudo nano /etc/netplan/01-network-manager-all.yaml
Change the file to read:
# Let NetworkManager manage all devices on this system
network:
version: 2
renderer: NetworkManager
Save and close the text editor. Next:
sudo netplan apply
sudo service network-manager restart
Any improvement? It may take a reboot.
If you want Network Manager to handle networking, I suggest that you change the netplan file:
sudo mv /etc/netplan/01-netcfg.yaml /etc/netplan/01-network-manager-all.yaml
Then change the file:
sudo nano /etc/netplan/01-network-manager-all.yaml
Change the file to read:
# Let NetworkManager manage all devices on this system
network:
version: 2
renderer: NetworkManager
Save and close the text editor. Next:
sudo netplan apply
sudo service network-manager restart
Any improvement? It may take a reboot.
answered Feb 26 at 15:05
![](https://i.stack.imgur.com/cKG9a.jpg?s=32&g=1)
![](https://i.stack.imgur.com/cKG9a.jpg?s=32&g=1)
chili555
36.7k54776
36.7k54776
No reboot required. Worked perfectly
â Josho
Feb 26 at 15:15
add a comment |Â
No reboot required. Worked perfectly
â Josho
Feb 26 at 15:15
No reboot required. Worked perfectly
â Josho
Feb 26 at 15:15
No reboot required. Worked perfectly
â Josho
Feb 26 at 15:15
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1009988%2fubuntu-17-10-server-running-ubuntu-desktop-network-manager-will-not-detect-ethe%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password