unable to connect to the internet through ethernet

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








up vote
1
down vote

favorite












My laptop (Lenovo G-50-80) was connecting fine to the internet through ethernet but I had to turn it off by long pressing the power button after it had frozen for over 10 minutes because the VMware Player had frozen up.



But after turning on my computer again, i am only able to use the internet through a wireless connection case in point asking this question.



Here is the output of some of the necessary configuration files and commands that I thought might help:



/etc/network/interfaces:



# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback


/etc/NetworkManager/NetworkManager.conf:



[main]
plugins=ifupdown,keyfile,ofono
#dns=dnsmasq

[ifupdown]
managed=false


/etc/resolv.conf:



# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 192.168.0.1
nameserver 192.168.1.1
search xxx.xx.xx


ip link:



1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1
 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
 link/ether 50:7b:9d:12:a4:30 brd ff:ff:ff:ff:ff:ff
3: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT group default qlen 1000
 link/ether e4:f8:9c:d7:9b:41 brd ff:ff:ff:ff:ff:ff
4: vmnet1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN mode DEFAULT group default qlen 1000
 link/ether 00:50:56:c0:00:01 brd ff:ff:ff:ff:ff:ff
5: vmnet8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN mode DEFAULT group default qlen 1000
 link/ether 00:50:56:c0:00:08 brd ff:ff:ff:ff:ff:ff


I watched syslog file by running the command tail -f /var/log/syslog and here is the output...



When connected to wireless:



Apr 12 16:43:47 Lenovo-G50-80 systemd-timesyncd[781]: Timed out waiting for reply from 91.189.89.198:123 (ntp.ubuntu.com).
Apr 12 16:45:01 Lenovo-G50-80 CRON[4015]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Apr 12 16:46:05 Lenovo-G50-80 systemd-timesyncd[781]: Timed out waiting for reply from 91.189.91.157:123 (ntp.ubuntu.com).
Apr 12 16:46:16 Lenovo-G50-80 systemd-timesyncd[781]: Timed out waiting for reply from 91.189.89.198:123 (ntp.ubuntu.com).
Apr 12 16:46:26 Lenovo-G50-80 systemd-timesyncd[781]: Timed out waiting for reply from 91.189.94.4:123 (ntp.ubuntu.com).
Apr 12 16:46:36 Lenovo-G50-80 systemd-timesyncd[781]: Timed out waiting for reply from 91.189.89.199:123 (ntp.ubuntu.com).
Apr 12 16:51:03 Lenovo-G50-80 systemd-timesyncd[781]: Timed out waiting for reply from 91.189.89.198:123 (ntp.ubuntu.com).
Apr 12 16:51:13 Lenovo-G50-80 systemd-timesyncd[781]: Timed out waiting for reply from 91.189.91.157:123 (ntp.ubuntu.com).
Apr 12 16:51:23 Lenovo-G50-80 systemd-timesyncd[781]: Timed out waiting for reply from 91.189.89.199:123 (ntp.ubuntu.com).
Apr 12 16:51:33 Lenovo-G50-80 systemd-timesyncd[781]: Timed out waiting for reply from 91.189.94.4:123 (ntp.ubuntu.com).


When I tried to switch to ethernet:



Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.2170] device (enp2s0): Activation: starting connection 'Auto Ethernet' (308a058b-d505-4b7d-911f-06e133a924ec)
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.2172] audit: op="connection-activate" uuid="308a058b-d505-4b7d-911f-06e133a924ec" name="Auto Ethernet" pid=1761 uid=1000 result="success"
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.2174] device (enp2s0): state change: disconnected -> prepare (reason 'none') [30 40 0]
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.2201] device (enp2s0): state change: prepare -> config (reason 'none') [40 50 0]
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.2210] device (enp2s0): state change: config -> ip-config (reason 'none') [50 70 0]
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.2216] dhcp4 (enp2s0): activation: beginning transaction (timeout in 45 seconds)
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.2238] dhcp4 (enp2s0): dhclient started with pid 4231
Apr 12 16:52:05 Lenovo-G50-80 vmnet-natd: RTM_NEWLINK: name:enp2s0 index:2 flags:0x00011043
Apr 12 16:52:05 Lenovo-G50-80 vmnetBridge: RTM_NEWLINK: name:enp2s0 index:2 flags:0x00011043
Apr 12 16:52:05 Lenovo-G50-80 dhclient[4231]: DHCPREQUEST of 192.168.0.18 on enp2s0 to 255.255.255.255 port 67 (xid=0x269ab741)
Apr 12 16:52:05 Lenovo-G50-80 dhclient[4231]: DHCPNAK from 10.103.0.56 (xid=0x41b79a26)
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.2634] dhcp4 (enp2s0): state changed unknown -> expire
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.2737] dhcp4 (enp2s0): state changed expire -> unknown
Apr 12 16:52:05 Lenovo-G50-80 dhclient[4231]: DHCPDISCOVER on enp2s0 to 255.255.255.255 port 67 interval 3 (xid=0x91220402)
Apr 12 16:52:05 Lenovo-G50-80 dhclient[4231]: DHCPREQUEST of 192.168.0.18 on enp2s0 to 255.255.255.255 port 67 (xid=0x2042291)
Apr 12 16:52:05 Lenovo-G50-80 dhclient[4231]: DHCPOFFER of 192.168.0.18 from 192.168.0.1
Apr 12 16:52:05 Lenovo-G50-80 dhclient[4231]: DHCPACK of 192.168.0.18 from 192.168.0.1
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.3716] address 192.168.0.18
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.3716] plen 24 (255.255.255.0)
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.3716] gateway 192.168.0.1
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.3716] server identifier 192.168.0.1
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.3716] lease time 86400
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.3716] nameserver '192.168.0.1'
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.3717] dhcp4 (enp2s0): state changed unknown -> bound
Apr 12 16:52:05 Lenovo-G50-80 vmnet-natd: RTM_NEWADDR: index:2, addr:192.168.0.18
Apr 12 16:52:05 Lenovo-G50-80 avahi-daemon[903]: Joining mDNS multicast group on interface enp2s0.IPv4 with address 192.168.0.18.
Apr 12 16:52:05 Lenovo-G50-80 avahi-daemon[903]: New relevant interface enp2s0.IPv4 for mDNS.
Apr 12 16:52:05 Lenovo-G50-80 avahi-daemon[903]: Registering new address record for 192.168.0.18 on enp2s0.IPv4.
Apr 12 16:52:05 Lenovo-G50-80 vmnet-natd: RTM_NEWROUTE: index:2
Apr 12 16:52:05 Lenovo-G50-80 vmnetBridge: RTM_NEWROUTE: index:2
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.3741] device (enp2s0): state change: ip-config -> ip-check (reason 'none') [70 80 0]
Apr 12 16:52:05 Lenovo-G50-80 vmnetBridge: Stopped bridge wlp3s0 to virtual network 0.
Apr 12 16:52:05 Lenovo-G50-80 vmnetBridge: Started bridge enp2s0 to virtual network 0.
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.3754] device (enp2s0): state change: ip-check -> secondaries (reason 'none') [80 90 0]
Apr 12 16:52:05 Lenovo-G50-80 kernel: [ 878.873139] bridge-wlp3s0: disabling the bridge on dev down
Apr 12 16:52:05 Lenovo-G50-80 kernel: [ 878.873175] bridge-wlp3s0: down
Apr 12 16:52:05 Lenovo-G50-80 kernel: [ 878.873189] bridge-wlp3s0: detached
Apr 12 16:52:05 Lenovo-G50-80 kernel: [ 878.873226] /dev/vmnet: open called by PID 2129 (vmnet-bridge)
Apr 12 16:52:05 Lenovo-G50-80 kernel: [ 878.873236] /dev/vmnet: hub 0 does not exist, allocating memory.
Apr 12 16:52:05 Lenovo-G50-80 kernel: [ 878.873273] /dev/vmnet: port on hub 0 successfully opened
Apr 12 16:52:05 Lenovo-G50-80 kernel: [ 878.873285] bridge-enp2s0: up
Apr 12 16:52:05 Lenovo-G50-80 kernel: [ 878.873289] bridge-enp2s0: attached
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.3779] device (enp2s0): state change: secondaries -> activated (reason 'none') [90 100 0]
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.4416] manager: NetworkManager state is now CONNECTED_LOCAL
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.4418] manager: NetworkManager state is now CONNECTED_GLOBAL
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.4420] policy: set 'Auto Ethernet' (enp2s0) as default for IPv4 routing and DNS
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.4421] dns-mgr: Writing DNS information to /sbin/resolvconf
Apr 12 16:52:05 Lenovo-G50-80 dhclient[4231]: bound to 192.168.0.18 -- renewal in 39410 seconds.
Apr 12 16:52:05 Lenovo-G50-80 kernel: [ 879.071512] userif-3: sent link down event.
Apr 12 16:52:05 Lenovo-G50-80 kernel: [ 879.071516] userif-3: sent link up event.
Apr 12 16:52:05 Lenovo-G50-80 org.gtk.vfs.Daemon[1457]: ** (process:2337): WARNING **: Couldn't create directory monitor on smb://x-gnome-default-workgroup/. Error: Operation not supported by backend
Apr 12 16:52:05 Lenovo-G50-80 whoopsie[1957]: [16:52:05] offline
Apr 12 16:52:06 Lenovo-G50-80 NetworkManager[993]: <info> [1523541126.8824] device (enp2s0): Activation: successful, device activated.
Apr 12 16:52:06 Lenovo-G50-80 dbus[933]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Apr 12 16:52:06 Lenovo-G50-80 whoopsie[1957]: [16:52:06] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/2
Apr 12 16:52:06 Lenovo-G50-80 whoopsie[1957]: [16:52:06] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/2
Apr 12 16:52:06 Lenovo-G50-80 whoopsie[1957]: [16:52:06] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/2
Apr 12 16:52:06 Lenovo-G50-80 whoopsie[1957]: [16:52:06] online
Apr 12 16:52:06 Lenovo-G50-80 systemd[1]: Starting Network Manager Script Dispatcher Service...
Apr 12 16:52:06 Lenovo-G50-80 dbus[933]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Apr 12 16:52:06 Lenovo-G50-80 systemd[1]: Started Network Manager Script Dispatcher Service.
Apr 12 16:52:06 Lenovo-G50-80 nm-dispatcher: req:1 'up' [enp2s0]: new request (1 scripts)
Apr 12 16:52:06 Lenovo-G50-80 nm-dispatcher: req:1 'up' [enp2s0]: start running ordered scripts...
Apr 12 16:52:07 Lenovo-G50-80 avahi-daemon[903]: Joining mDNS multicast group on interface enp2s0.IPv6 with address fe80::ebba:fab2:4727:42aa.
Apr 12 16:52:07 Lenovo-G50-80 avahi-daemon[903]: New relevant interface enp2s0.IPv6 for mDNS.
Apr 12 16:52:07 Lenovo-G50-80 avahi-daemon[903]: Registering new address record for fe80::ebba:fab2:4727:42aa on enp2s0.*.


What could be the issue here and how can I resolve it?






16.04 networking internet ethernet







share|improve this question























  • What happens if you disable the vmnet/vfs/vmware?
    – heynnema
    Apr 12 at 15:31











  • @heynnema how do i do that
    – kellymandem
    Apr 12 at 15:32










  • I'm not familiar with vmnet/vfs/vmware, but you'd probably start with something like sudo systemctl stop vmnet... or you might have to uninstall it. Also, do you have 2 routers in your network configuration?
    – heynnema
    Apr 12 at 15:34











  • @heynnema right now my vmware player is not running so when i run that command i get Failed to stop vmnet.service: Unit vmnet.service not loaded., so i guess it's not the issue
    – kellymandem
    Apr 12 at 15:39










  • That command may not be the exact command that you need to stop the vm* services. You'll have to research it a little yourself, as I'm not that familiar with vm*, but some of the error messages indicate that your problem might be related. Tell me more about your network config. Do you have two routers?
    – heynnema
    Apr 12 at 15:43














up vote
1
down vote

favorite












My laptop (Lenovo G-50-80) was connecting fine to the internet through ethernet but I had to turn it off by long pressing the power button after it had frozen for over 10 minutes because the VMware Player had frozen up.



But after turning on my computer again, i am only able to use the internet through a wireless connection case in point asking this question.



Here is the output of some of the necessary configuration files and commands that I thought might help:



/etc/network/interfaces:



# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback


/etc/NetworkManager/NetworkManager.conf:



[main]
plugins=ifupdown,keyfile,ofono
#dns=dnsmasq

[ifupdown]
managed=false


/etc/resolv.conf:



# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 192.168.0.1
nameserver 192.168.1.1
search xxx.xx.xx


ip link:



1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1
 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
 link/ether 50:7b:9d:12:a4:30 brd ff:ff:ff:ff:ff:ff
3: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT group default qlen 1000
 link/ether e4:f8:9c:d7:9b:41 brd ff:ff:ff:ff:ff:ff
4: vmnet1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN mode DEFAULT group default qlen 1000
 link/ether 00:50:56:c0:00:01 brd ff:ff:ff:ff:ff:ff
5: vmnet8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN mode DEFAULT group default qlen 1000
 link/ether 00:50:56:c0:00:08 brd ff:ff:ff:ff:ff:ff


I watched syslog file by running the command tail -f /var/log/syslog and here is the output...



When connected to wireless:



Apr 12 16:43:47 Lenovo-G50-80 systemd-timesyncd[781]: Timed out waiting for reply from 91.189.89.198:123 (ntp.ubuntu.com).
Apr 12 16:45:01 Lenovo-G50-80 CRON[4015]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Apr 12 16:46:05 Lenovo-G50-80 systemd-timesyncd[781]: Timed out waiting for reply from 91.189.91.157:123 (ntp.ubuntu.com).
Apr 12 16:46:16 Lenovo-G50-80 systemd-timesyncd[781]: Timed out waiting for reply from 91.189.89.198:123 (ntp.ubuntu.com).
Apr 12 16:46:26 Lenovo-G50-80 systemd-timesyncd[781]: Timed out waiting for reply from 91.189.94.4:123 (ntp.ubuntu.com).
Apr 12 16:46:36 Lenovo-G50-80 systemd-timesyncd[781]: Timed out waiting for reply from 91.189.89.199:123 (ntp.ubuntu.com).
Apr 12 16:51:03 Lenovo-G50-80 systemd-timesyncd[781]: Timed out waiting for reply from 91.189.89.198:123 (ntp.ubuntu.com).
Apr 12 16:51:13 Lenovo-G50-80 systemd-timesyncd[781]: Timed out waiting for reply from 91.189.91.157:123 (ntp.ubuntu.com).
Apr 12 16:51:23 Lenovo-G50-80 systemd-timesyncd[781]: Timed out waiting for reply from 91.189.89.199:123 (ntp.ubuntu.com).
Apr 12 16:51:33 Lenovo-G50-80 systemd-timesyncd[781]: Timed out waiting for reply from 91.189.94.4:123 (ntp.ubuntu.com).


When I tried to switch to ethernet:



Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.2170] device (enp2s0): Activation: starting connection 'Auto Ethernet' (308a058b-d505-4b7d-911f-06e133a924ec)
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.2172] audit: op="connection-activate" uuid="308a058b-d505-4b7d-911f-06e133a924ec" name="Auto Ethernet" pid=1761 uid=1000 result="success"
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.2174] device (enp2s0): state change: disconnected -> prepare (reason 'none') [30 40 0]
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.2201] device (enp2s0): state change: prepare -> config (reason 'none') [40 50 0]
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.2210] device (enp2s0): state change: config -> ip-config (reason 'none') [50 70 0]
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.2216] dhcp4 (enp2s0): activation: beginning transaction (timeout in 45 seconds)
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.2238] dhcp4 (enp2s0): dhclient started with pid 4231
Apr 12 16:52:05 Lenovo-G50-80 vmnet-natd: RTM_NEWLINK: name:enp2s0 index:2 flags:0x00011043
Apr 12 16:52:05 Lenovo-G50-80 vmnetBridge: RTM_NEWLINK: name:enp2s0 index:2 flags:0x00011043
Apr 12 16:52:05 Lenovo-G50-80 dhclient[4231]: DHCPREQUEST of 192.168.0.18 on enp2s0 to 255.255.255.255 port 67 (xid=0x269ab741)
Apr 12 16:52:05 Lenovo-G50-80 dhclient[4231]: DHCPNAK from 10.103.0.56 (xid=0x41b79a26)
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.2634] dhcp4 (enp2s0): state changed unknown -> expire
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.2737] dhcp4 (enp2s0): state changed expire -> unknown
Apr 12 16:52:05 Lenovo-G50-80 dhclient[4231]: DHCPDISCOVER on enp2s0 to 255.255.255.255 port 67 interval 3 (xid=0x91220402)
Apr 12 16:52:05 Lenovo-G50-80 dhclient[4231]: DHCPREQUEST of 192.168.0.18 on enp2s0 to 255.255.255.255 port 67 (xid=0x2042291)
Apr 12 16:52:05 Lenovo-G50-80 dhclient[4231]: DHCPOFFER of 192.168.0.18 from 192.168.0.1
Apr 12 16:52:05 Lenovo-G50-80 dhclient[4231]: DHCPACK of 192.168.0.18 from 192.168.0.1
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.3716] address 192.168.0.18
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.3716] plen 24 (255.255.255.0)
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.3716] gateway 192.168.0.1
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.3716] server identifier 192.168.0.1
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.3716] lease time 86400
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.3716] nameserver '192.168.0.1'
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.3717] dhcp4 (enp2s0): state changed unknown -> bound
Apr 12 16:52:05 Lenovo-G50-80 vmnet-natd: RTM_NEWADDR: index:2, addr:192.168.0.18
Apr 12 16:52:05 Lenovo-G50-80 avahi-daemon[903]: Joining mDNS multicast group on interface enp2s0.IPv4 with address 192.168.0.18.
Apr 12 16:52:05 Lenovo-G50-80 avahi-daemon[903]: New relevant interface enp2s0.IPv4 for mDNS.
Apr 12 16:52:05 Lenovo-G50-80 avahi-daemon[903]: Registering new address record for 192.168.0.18 on enp2s0.IPv4.
Apr 12 16:52:05 Lenovo-G50-80 vmnet-natd: RTM_NEWROUTE: index:2
Apr 12 16:52:05 Lenovo-G50-80 vmnetBridge: RTM_NEWROUTE: index:2
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.3741] device (enp2s0): state change: ip-config -> ip-check (reason 'none') [70 80 0]
Apr 12 16:52:05 Lenovo-G50-80 vmnetBridge: Stopped bridge wlp3s0 to virtual network 0.
Apr 12 16:52:05 Lenovo-G50-80 vmnetBridge: Started bridge enp2s0 to virtual network 0.
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.3754] device (enp2s0): state change: ip-check -> secondaries (reason 'none') [80 90 0]
Apr 12 16:52:05 Lenovo-G50-80 kernel: [ 878.873139] bridge-wlp3s0: disabling the bridge on dev down
Apr 12 16:52:05 Lenovo-G50-80 kernel: [ 878.873175] bridge-wlp3s0: down
Apr 12 16:52:05 Lenovo-G50-80 kernel: [ 878.873189] bridge-wlp3s0: detached
Apr 12 16:52:05 Lenovo-G50-80 kernel: [ 878.873226] /dev/vmnet: open called by PID 2129 (vmnet-bridge)
Apr 12 16:52:05 Lenovo-G50-80 kernel: [ 878.873236] /dev/vmnet: hub 0 does not exist, allocating memory.
Apr 12 16:52:05 Lenovo-G50-80 kernel: [ 878.873273] /dev/vmnet: port on hub 0 successfully opened
Apr 12 16:52:05 Lenovo-G50-80 kernel: [ 878.873285] bridge-enp2s0: up
Apr 12 16:52:05 Lenovo-G50-80 kernel: [ 878.873289] bridge-enp2s0: attached
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.3779] device (enp2s0): state change: secondaries -> activated (reason 'none') [90 100 0]
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.4416] manager: NetworkManager state is now CONNECTED_LOCAL
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.4418] manager: NetworkManager state is now CONNECTED_GLOBAL
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.4420] policy: set 'Auto Ethernet' (enp2s0) as default for IPv4 routing and DNS
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.4421] dns-mgr: Writing DNS information to /sbin/resolvconf
Apr 12 16:52:05 Lenovo-G50-80 dhclient[4231]: bound to 192.168.0.18 -- renewal in 39410 seconds.
Apr 12 16:52:05 Lenovo-G50-80 kernel: [ 879.071512] userif-3: sent link down event.
Apr 12 16:52:05 Lenovo-G50-80 kernel: [ 879.071516] userif-3: sent link up event.
Apr 12 16:52:05 Lenovo-G50-80 org.gtk.vfs.Daemon[1457]: ** (process:2337): WARNING **: Couldn't create directory monitor on smb://x-gnome-default-workgroup/. Error: Operation not supported by backend
Apr 12 16:52:05 Lenovo-G50-80 whoopsie[1957]: [16:52:05] offline
Apr 12 16:52:06 Lenovo-G50-80 NetworkManager[993]: <info> [1523541126.8824] device (enp2s0): Activation: successful, device activated.
Apr 12 16:52:06 Lenovo-G50-80 dbus[933]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Apr 12 16:52:06 Lenovo-G50-80 whoopsie[1957]: [16:52:06] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/2
Apr 12 16:52:06 Lenovo-G50-80 whoopsie[1957]: [16:52:06] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/2
Apr 12 16:52:06 Lenovo-G50-80 whoopsie[1957]: [16:52:06] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/2
Apr 12 16:52:06 Lenovo-G50-80 whoopsie[1957]: [16:52:06] online
Apr 12 16:52:06 Lenovo-G50-80 systemd[1]: Starting Network Manager Script Dispatcher Service...
Apr 12 16:52:06 Lenovo-G50-80 dbus[933]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Apr 12 16:52:06 Lenovo-G50-80 systemd[1]: Started Network Manager Script Dispatcher Service.
Apr 12 16:52:06 Lenovo-G50-80 nm-dispatcher: req:1 'up' [enp2s0]: new request (1 scripts)
Apr 12 16:52:06 Lenovo-G50-80 nm-dispatcher: req:1 'up' [enp2s0]: start running ordered scripts...
Apr 12 16:52:07 Lenovo-G50-80 avahi-daemon[903]: Joining mDNS multicast group on interface enp2s0.IPv6 with address fe80::ebba:fab2:4727:42aa.
Apr 12 16:52:07 Lenovo-G50-80 avahi-daemon[903]: New relevant interface enp2s0.IPv6 for mDNS.
Apr 12 16:52:07 Lenovo-G50-80 avahi-daemon[903]: Registering new address record for fe80::ebba:fab2:4727:42aa on enp2s0.*.


What could be the issue here and how can I resolve it?






16.04 networking internet ethernet







share|improve this question























  • What happens if you disable the vmnet/vfs/vmware?
    – heynnema
    Apr 12 at 15:31











  • @heynnema how do i do that
    – kellymandem
    Apr 12 at 15:32










  • I'm not familiar with vmnet/vfs/vmware, but you'd probably start with something like sudo systemctl stop vmnet... or you might have to uninstall it. Also, do you have 2 routers in your network configuration?
    – heynnema
    Apr 12 at 15:34











  • @heynnema right now my vmware player is not running so when i run that command i get Failed to stop vmnet.service: Unit vmnet.service not loaded., so i guess it's not the issue
    – kellymandem
    Apr 12 at 15:39










  • That command may not be the exact command that you need to stop the vm* services. You'll have to research it a little yourself, as I'm not that familiar with vm*, but some of the error messages indicate that your problem might be related. Tell me more about your network config. Do you have two routers?
    – heynnema
    Apr 12 at 15:43












up vote
1
down vote

favorite









up vote
1
down vote

favorite











My laptop (Lenovo G-50-80) was connecting fine to the internet through ethernet but I had to turn it off by long pressing the power button after it had frozen for over 10 minutes because the VMware Player had frozen up.



But after turning on my computer again, i am only able to use the internet through a wireless connection case in point asking this question.



Here is the output of some of the necessary configuration files and commands that I thought might help:



/etc/network/interfaces:



# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback


/etc/NetworkManager/NetworkManager.conf:



[main]
plugins=ifupdown,keyfile,ofono
#dns=dnsmasq

[ifupdown]
managed=false


/etc/resolv.conf:



# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 192.168.0.1
nameserver 192.168.1.1
search xxx.xx.xx


ip link:



1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1
 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
 link/ether 50:7b:9d:12:a4:30 brd ff:ff:ff:ff:ff:ff
3: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT group default qlen 1000
 link/ether e4:f8:9c:d7:9b:41 brd ff:ff:ff:ff:ff:ff
4: vmnet1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN mode DEFAULT group default qlen 1000
 link/ether 00:50:56:c0:00:01 brd ff:ff:ff:ff:ff:ff
5: vmnet8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN mode DEFAULT group default qlen 1000
 link/ether 00:50:56:c0:00:08 brd ff:ff:ff:ff:ff:ff


I watched syslog file by running the command tail -f /var/log/syslog and here is the output...



When connected to wireless:



Apr 12 16:43:47 Lenovo-G50-80 systemd-timesyncd[781]: Timed out waiting for reply from 91.189.89.198:123 (ntp.ubuntu.com).
Apr 12 16:45:01 Lenovo-G50-80 CRON[4015]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Apr 12 16:46:05 Lenovo-G50-80 systemd-timesyncd[781]: Timed out waiting for reply from 91.189.91.157:123 (ntp.ubuntu.com).
Apr 12 16:46:16 Lenovo-G50-80 systemd-timesyncd[781]: Timed out waiting for reply from 91.189.89.198:123 (ntp.ubuntu.com).
Apr 12 16:46:26 Lenovo-G50-80 systemd-timesyncd[781]: Timed out waiting for reply from 91.189.94.4:123 (ntp.ubuntu.com).
Apr 12 16:46:36 Lenovo-G50-80 systemd-timesyncd[781]: Timed out waiting for reply from 91.189.89.199:123 (ntp.ubuntu.com).
Apr 12 16:51:03 Lenovo-G50-80 systemd-timesyncd[781]: Timed out waiting for reply from 91.189.89.198:123 (ntp.ubuntu.com).
Apr 12 16:51:13 Lenovo-G50-80 systemd-timesyncd[781]: Timed out waiting for reply from 91.189.91.157:123 (ntp.ubuntu.com).
Apr 12 16:51:23 Lenovo-G50-80 systemd-timesyncd[781]: Timed out waiting for reply from 91.189.89.199:123 (ntp.ubuntu.com).
Apr 12 16:51:33 Lenovo-G50-80 systemd-timesyncd[781]: Timed out waiting for reply from 91.189.94.4:123 (ntp.ubuntu.com).


When I tried to switch to ethernet:



Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.2170] device (enp2s0): Activation: starting connection 'Auto Ethernet' (308a058b-d505-4b7d-911f-06e133a924ec)
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.2172] audit: op="connection-activate" uuid="308a058b-d505-4b7d-911f-06e133a924ec" name="Auto Ethernet" pid=1761 uid=1000 result="success"
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.2174] device (enp2s0): state change: disconnected -> prepare (reason 'none') [30 40 0]
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.2201] device (enp2s0): state change: prepare -> config (reason 'none') [40 50 0]
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.2210] device (enp2s0): state change: config -> ip-config (reason 'none') [50 70 0]
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.2216] dhcp4 (enp2s0): activation: beginning transaction (timeout in 45 seconds)
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.2238] dhcp4 (enp2s0): dhclient started with pid 4231
Apr 12 16:52:05 Lenovo-G50-80 vmnet-natd: RTM_NEWLINK: name:enp2s0 index:2 flags:0x00011043
Apr 12 16:52:05 Lenovo-G50-80 vmnetBridge: RTM_NEWLINK: name:enp2s0 index:2 flags:0x00011043
Apr 12 16:52:05 Lenovo-G50-80 dhclient[4231]: DHCPREQUEST of 192.168.0.18 on enp2s0 to 255.255.255.255 port 67 (xid=0x269ab741)
Apr 12 16:52:05 Lenovo-G50-80 dhclient[4231]: DHCPNAK from 10.103.0.56 (xid=0x41b79a26)
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.2634] dhcp4 (enp2s0): state changed unknown -> expire
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.2737] dhcp4 (enp2s0): state changed expire -> unknown
Apr 12 16:52:05 Lenovo-G50-80 dhclient[4231]: DHCPDISCOVER on enp2s0 to 255.255.255.255 port 67 interval 3 (xid=0x91220402)
Apr 12 16:52:05 Lenovo-G50-80 dhclient[4231]: DHCPREQUEST of 192.168.0.18 on enp2s0 to 255.255.255.255 port 67 (xid=0x2042291)
Apr 12 16:52:05 Lenovo-G50-80 dhclient[4231]: DHCPOFFER of 192.168.0.18 from 192.168.0.1
Apr 12 16:52:05 Lenovo-G50-80 dhclient[4231]: DHCPACK of 192.168.0.18 from 192.168.0.1
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.3716] address 192.168.0.18
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.3716] plen 24 (255.255.255.0)
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.3716] gateway 192.168.0.1
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.3716] server identifier 192.168.0.1
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.3716] lease time 86400
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.3716] nameserver '192.168.0.1'
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.3717] dhcp4 (enp2s0): state changed unknown -> bound
Apr 12 16:52:05 Lenovo-G50-80 vmnet-natd: RTM_NEWADDR: index:2, addr:192.168.0.18
Apr 12 16:52:05 Lenovo-G50-80 avahi-daemon[903]: Joining mDNS multicast group on interface enp2s0.IPv4 with address 192.168.0.18.
Apr 12 16:52:05 Lenovo-G50-80 avahi-daemon[903]: New relevant interface enp2s0.IPv4 for mDNS.
Apr 12 16:52:05 Lenovo-G50-80 avahi-daemon[903]: Registering new address record for 192.168.0.18 on enp2s0.IPv4.
Apr 12 16:52:05 Lenovo-G50-80 vmnet-natd: RTM_NEWROUTE: index:2
Apr 12 16:52:05 Lenovo-G50-80 vmnetBridge: RTM_NEWROUTE: index:2
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.3741] device (enp2s0): state change: ip-config -> ip-check (reason 'none') [70 80 0]
Apr 12 16:52:05 Lenovo-G50-80 vmnetBridge: Stopped bridge wlp3s0 to virtual network 0.
Apr 12 16:52:05 Lenovo-G50-80 vmnetBridge: Started bridge enp2s0 to virtual network 0.
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.3754] device (enp2s0): state change: ip-check -> secondaries (reason 'none') [80 90 0]
Apr 12 16:52:05 Lenovo-G50-80 kernel: [ 878.873139] bridge-wlp3s0: disabling the bridge on dev down
Apr 12 16:52:05 Lenovo-G50-80 kernel: [ 878.873175] bridge-wlp3s0: down
Apr 12 16:52:05 Lenovo-G50-80 kernel: [ 878.873189] bridge-wlp3s0: detached
Apr 12 16:52:05 Lenovo-G50-80 kernel: [ 878.873226] /dev/vmnet: open called by PID 2129 (vmnet-bridge)
Apr 12 16:52:05 Lenovo-G50-80 kernel: [ 878.873236] /dev/vmnet: hub 0 does not exist, allocating memory.
Apr 12 16:52:05 Lenovo-G50-80 kernel: [ 878.873273] /dev/vmnet: port on hub 0 successfully opened
Apr 12 16:52:05 Lenovo-G50-80 kernel: [ 878.873285] bridge-enp2s0: up
Apr 12 16:52:05 Lenovo-G50-80 kernel: [ 878.873289] bridge-enp2s0: attached
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.3779] device (enp2s0): state change: secondaries -> activated (reason 'none') [90 100 0]
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.4416] manager: NetworkManager state is now CONNECTED_LOCAL
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.4418] manager: NetworkManager state is now CONNECTED_GLOBAL
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.4420] policy: set 'Auto Ethernet' (enp2s0) as default for IPv4 routing and DNS
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.4421] dns-mgr: Writing DNS information to /sbin/resolvconf
Apr 12 16:52:05 Lenovo-G50-80 dhclient[4231]: bound to 192.168.0.18 -- renewal in 39410 seconds.
Apr 12 16:52:05 Lenovo-G50-80 kernel: [ 879.071512] userif-3: sent link down event.
Apr 12 16:52:05 Lenovo-G50-80 kernel: [ 879.071516] userif-3: sent link up event.
Apr 12 16:52:05 Lenovo-G50-80 org.gtk.vfs.Daemon[1457]: ** (process:2337): WARNING **: Couldn't create directory monitor on smb://x-gnome-default-workgroup/. Error: Operation not supported by backend
Apr 12 16:52:05 Lenovo-G50-80 whoopsie[1957]: [16:52:05] offline
Apr 12 16:52:06 Lenovo-G50-80 NetworkManager[993]: <info> [1523541126.8824] device (enp2s0): Activation: successful, device activated.
Apr 12 16:52:06 Lenovo-G50-80 dbus[933]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Apr 12 16:52:06 Lenovo-G50-80 whoopsie[1957]: [16:52:06] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/2
Apr 12 16:52:06 Lenovo-G50-80 whoopsie[1957]: [16:52:06] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/2
Apr 12 16:52:06 Lenovo-G50-80 whoopsie[1957]: [16:52:06] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/2
Apr 12 16:52:06 Lenovo-G50-80 whoopsie[1957]: [16:52:06] online
Apr 12 16:52:06 Lenovo-G50-80 systemd[1]: Starting Network Manager Script Dispatcher Service...
Apr 12 16:52:06 Lenovo-G50-80 dbus[933]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Apr 12 16:52:06 Lenovo-G50-80 systemd[1]: Started Network Manager Script Dispatcher Service.
Apr 12 16:52:06 Lenovo-G50-80 nm-dispatcher: req:1 'up' [enp2s0]: new request (1 scripts)
Apr 12 16:52:06 Lenovo-G50-80 nm-dispatcher: req:1 'up' [enp2s0]: start running ordered scripts...
Apr 12 16:52:07 Lenovo-G50-80 avahi-daemon[903]: Joining mDNS multicast group on interface enp2s0.IPv6 with address fe80::ebba:fab2:4727:42aa.
Apr 12 16:52:07 Lenovo-G50-80 avahi-daemon[903]: New relevant interface enp2s0.IPv6 for mDNS.
Apr 12 16:52:07 Lenovo-G50-80 avahi-daemon[903]: Registering new address record for fe80::ebba:fab2:4727:42aa on enp2s0.*.


What could be the issue here and how can I resolve it?






16.04 networking internet ethernet







share|improve this question















My laptop (Lenovo G-50-80) was connecting fine to the internet through ethernet but I had to turn it off by long pressing the power button after it had frozen for over 10 minutes because the VMware Player had frozen up.



But after turning on my computer again, i am only able to use the internet through a wireless connection case in point asking this question.



Here is the output of some of the necessary configuration files and commands that I thought might help:



/etc/network/interfaces:



# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback


/etc/NetworkManager/NetworkManager.conf:



[main]
plugins=ifupdown,keyfile,ofono
#dns=dnsmasq

[ifupdown]
managed=false


/etc/resolv.conf:



# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 192.168.0.1
nameserver 192.168.1.1
search xxx.xx.xx


ip link:



1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1
 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
 link/ether 50:7b:9d:12:a4:30 brd ff:ff:ff:ff:ff:ff
3: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT group default qlen 1000
 link/ether e4:f8:9c:d7:9b:41 brd ff:ff:ff:ff:ff:ff
4: vmnet1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN mode DEFAULT group default qlen 1000
 link/ether 00:50:56:c0:00:01 brd ff:ff:ff:ff:ff:ff
5: vmnet8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN mode DEFAULT group default qlen 1000
 link/ether 00:50:56:c0:00:08 brd ff:ff:ff:ff:ff:ff


I watched syslog file by running the command tail -f /var/log/syslog and here is the output...



When connected to wireless:



Apr 12 16:43:47 Lenovo-G50-80 systemd-timesyncd[781]: Timed out waiting for reply from 91.189.89.198:123 (ntp.ubuntu.com).
Apr 12 16:45:01 Lenovo-G50-80 CRON[4015]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Apr 12 16:46:05 Lenovo-G50-80 systemd-timesyncd[781]: Timed out waiting for reply from 91.189.91.157:123 (ntp.ubuntu.com).
Apr 12 16:46:16 Lenovo-G50-80 systemd-timesyncd[781]: Timed out waiting for reply from 91.189.89.198:123 (ntp.ubuntu.com).
Apr 12 16:46:26 Lenovo-G50-80 systemd-timesyncd[781]: Timed out waiting for reply from 91.189.94.4:123 (ntp.ubuntu.com).
Apr 12 16:46:36 Lenovo-G50-80 systemd-timesyncd[781]: Timed out waiting for reply from 91.189.89.199:123 (ntp.ubuntu.com).
Apr 12 16:51:03 Lenovo-G50-80 systemd-timesyncd[781]: Timed out waiting for reply from 91.189.89.198:123 (ntp.ubuntu.com).
Apr 12 16:51:13 Lenovo-G50-80 systemd-timesyncd[781]: Timed out waiting for reply from 91.189.91.157:123 (ntp.ubuntu.com).
Apr 12 16:51:23 Lenovo-G50-80 systemd-timesyncd[781]: Timed out waiting for reply from 91.189.89.199:123 (ntp.ubuntu.com).
Apr 12 16:51:33 Lenovo-G50-80 systemd-timesyncd[781]: Timed out waiting for reply from 91.189.94.4:123 (ntp.ubuntu.com).


When I tried to switch to ethernet:



Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.2170] device (enp2s0): Activation: starting connection 'Auto Ethernet' (308a058b-d505-4b7d-911f-06e133a924ec)
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.2172] audit: op="connection-activate" uuid="308a058b-d505-4b7d-911f-06e133a924ec" name="Auto Ethernet" pid=1761 uid=1000 result="success"
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.2174] device (enp2s0): state change: disconnected -> prepare (reason 'none') [30 40 0]
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.2201] device (enp2s0): state change: prepare -> config (reason 'none') [40 50 0]
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.2210] device (enp2s0): state change: config -> ip-config (reason 'none') [50 70 0]
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.2216] dhcp4 (enp2s0): activation: beginning transaction (timeout in 45 seconds)
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.2238] dhcp4 (enp2s0): dhclient started with pid 4231
Apr 12 16:52:05 Lenovo-G50-80 vmnet-natd: RTM_NEWLINK: name:enp2s0 index:2 flags:0x00011043
Apr 12 16:52:05 Lenovo-G50-80 vmnetBridge: RTM_NEWLINK: name:enp2s0 index:2 flags:0x00011043
Apr 12 16:52:05 Lenovo-G50-80 dhclient[4231]: DHCPREQUEST of 192.168.0.18 on enp2s0 to 255.255.255.255 port 67 (xid=0x269ab741)
Apr 12 16:52:05 Lenovo-G50-80 dhclient[4231]: DHCPNAK from 10.103.0.56 (xid=0x41b79a26)
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.2634] dhcp4 (enp2s0): state changed unknown -> expire
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.2737] dhcp4 (enp2s0): state changed expire -> unknown
Apr 12 16:52:05 Lenovo-G50-80 dhclient[4231]: DHCPDISCOVER on enp2s0 to 255.255.255.255 port 67 interval 3 (xid=0x91220402)
Apr 12 16:52:05 Lenovo-G50-80 dhclient[4231]: DHCPREQUEST of 192.168.0.18 on enp2s0 to 255.255.255.255 port 67 (xid=0x2042291)
Apr 12 16:52:05 Lenovo-G50-80 dhclient[4231]: DHCPOFFER of 192.168.0.18 from 192.168.0.1
Apr 12 16:52:05 Lenovo-G50-80 dhclient[4231]: DHCPACK of 192.168.0.18 from 192.168.0.1
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.3716] address 192.168.0.18
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.3716] plen 24 (255.255.255.0)
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.3716] gateway 192.168.0.1
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.3716] server identifier 192.168.0.1
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.3716] lease time 86400
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.3716] nameserver '192.168.0.1'
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.3717] dhcp4 (enp2s0): state changed unknown -> bound
Apr 12 16:52:05 Lenovo-G50-80 vmnet-natd: RTM_NEWADDR: index:2, addr:192.168.0.18
Apr 12 16:52:05 Lenovo-G50-80 avahi-daemon[903]: Joining mDNS multicast group on interface enp2s0.IPv4 with address 192.168.0.18.
Apr 12 16:52:05 Lenovo-G50-80 avahi-daemon[903]: New relevant interface enp2s0.IPv4 for mDNS.
Apr 12 16:52:05 Lenovo-G50-80 avahi-daemon[903]: Registering new address record for 192.168.0.18 on enp2s0.IPv4.
Apr 12 16:52:05 Lenovo-G50-80 vmnet-natd: RTM_NEWROUTE: index:2
Apr 12 16:52:05 Lenovo-G50-80 vmnetBridge: RTM_NEWROUTE: index:2
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.3741] device (enp2s0): state change: ip-config -> ip-check (reason 'none') [70 80 0]
Apr 12 16:52:05 Lenovo-G50-80 vmnetBridge: Stopped bridge wlp3s0 to virtual network 0.
Apr 12 16:52:05 Lenovo-G50-80 vmnetBridge: Started bridge enp2s0 to virtual network 0.
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.3754] device (enp2s0): state change: ip-check -> secondaries (reason 'none') [80 90 0]
Apr 12 16:52:05 Lenovo-G50-80 kernel: [ 878.873139] bridge-wlp3s0: disabling the bridge on dev down
Apr 12 16:52:05 Lenovo-G50-80 kernel: [ 878.873175] bridge-wlp3s0: down
Apr 12 16:52:05 Lenovo-G50-80 kernel: [ 878.873189] bridge-wlp3s0: detached
Apr 12 16:52:05 Lenovo-G50-80 kernel: [ 878.873226] /dev/vmnet: open called by PID 2129 (vmnet-bridge)
Apr 12 16:52:05 Lenovo-G50-80 kernel: [ 878.873236] /dev/vmnet: hub 0 does not exist, allocating memory.
Apr 12 16:52:05 Lenovo-G50-80 kernel: [ 878.873273] /dev/vmnet: port on hub 0 successfully opened
Apr 12 16:52:05 Lenovo-G50-80 kernel: [ 878.873285] bridge-enp2s0: up
Apr 12 16:52:05 Lenovo-G50-80 kernel: [ 878.873289] bridge-enp2s0: attached
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.3779] device (enp2s0): state change: secondaries -> activated (reason 'none') [90 100 0]
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.4416] manager: NetworkManager state is now CONNECTED_LOCAL
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.4418] manager: NetworkManager state is now CONNECTED_GLOBAL
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.4420] policy: set 'Auto Ethernet' (enp2s0) as default for IPv4 routing and DNS
Apr 12 16:52:05 Lenovo-G50-80 NetworkManager[993]: <info> [1523541125.4421] dns-mgr: Writing DNS information to /sbin/resolvconf
Apr 12 16:52:05 Lenovo-G50-80 dhclient[4231]: bound to 192.168.0.18 -- renewal in 39410 seconds.
Apr 12 16:52:05 Lenovo-G50-80 kernel: [ 879.071512] userif-3: sent link down event.
Apr 12 16:52:05 Lenovo-G50-80 kernel: [ 879.071516] userif-3: sent link up event.
Apr 12 16:52:05 Lenovo-G50-80 org.gtk.vfs.Daemon[1457]: ** (process:2337): WARNING **: Couldn't create directory monitor on smb://x-gnome-default-workgroup/. Error: Operation not supported by backend
Apr 12 16:52:05 Lenovo-G50-80 whoopsie[1957]: [16:52:05] offline
Apr 12 16:52:06 Lenovo-G50-80 NetworkManager[993]: <info> [1523541126.8824] device (enp2s0): Activation: successful, device activated.
Apr 12 16:52:06 Lenovo-G50-80 dbus[933]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Apr 12 16:52:06 Lenovo-G50-80 whoopsie[1957]: [16:52:06] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/2
Apr 12 16:52:06 Lenovo-G50-80 whoopsie[1957]: [16:52:06] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/2
Apr 12 16:52:06 Lenovo-G50-80 whoopsie[1957]: [16:52:06] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/2
Apr 12 16:52:06 Lenovo-G50-80 whoopsie[1957]: [16:52:06] online
Apr 12 16:52:06 Lenovo-G50-80 systemd[1]: Starting Network Manager Script Dispatcher Service...
Apr 12 16:52:06 Lenovo-G50-80 dbus[933]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Apr 12 16:52:06 Lenovo-G50-80 systemd[1]: Started Network Manager Script Dispatcher Service.
Apr 12 16:52:06 Lenovo-G50-80 nm-dispatcher: req:1 'up' [enp2s0]: new request (1 scripts)
Apr 12 16:52:06 Lenovo-G50-80 nm-dispatcher: req:1 'up' [enp2s0]: start running ordered scripts...
Apr 12 16:52:07 Lenovo-G50-80 avahi-daemon[903]: Joining mDNS multicast group on interface enp2s0.IPv6 with address fe80::ebba:fab2:4727:42aa.
Apr 12 16:52:07 Lenovo-G50-80 avahi-daemon[903]: New relevant interface enp2s0.IPv6 for mDNS.
Apr 12 16:52:07 Lenovo-G50-80 avahi-daemon[903]: Registering new address record for fe80::ebba:fab2:4727:42aa on enp2s0.*.


What could be the issue here and how can I resolve it?






16.04 networking internet ethernet




16.04 networking internet ethernet






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Apr 12 at 15:26









Eliah Kagan

79.5k20221359




79.5k20221359










asked Apr 12 at 14:29









kellymandem

1184




1184











  • What happens if you disable the vmnet/vfs/vmware?
    – heynnema
    Apr 12 at 15:31











  • @heynnema how do i do that
    – kellymandem
    Apr 12 at 15:32










  • I'm not familiar with vmnet/vfs/vmware, but you'd probably start with something like sudo systemctl stop vmnet... or you might have to uninstall it. Also, do you have 2 routers in your network configuration?
    – heynnema
    Apr 12 at 15:34











  • @heynnema right now my vmware player is not running so when i run that command i get Failed to stop vmnet.service: Unit vmnet.service not loaded., so i guess it's not the issue
    – kellymandem
    Apr 12 at 15:39










  • That command may not be the exact command that you need to stop the vm* services. You'll have to research it a little yourself, as I'm not that familiar with vm*, but some of the error messages indicate that your problem might be related. Tell me more about your network config. Do you have two routers?
    – heynnema
    Apr 12 at 15:43
















  • What happens if you disable the vmnet/vfs/vmware?
    – heynnema
    Apr 12 at 15:31











  • @heynnema how do i do that
    – kellymandem
    Apr 12 at 15:32










  • I'm not familiar with vmnet/vfs/vmware, but you'd probably start with something like sudo systemctl stop vmnet... or you might have to uninstall it. Also, do you have 2 routers in your network configuration?
    – heynnema
    Apr 12 at 15:34











  • @heynnema right now my vmware player is not running so when i run that command i get Failed to stop vmnet.service: Unit vmnet.service not loaded., so i guess it's not the issue
    – kellymandem
    Apr 12 at 15:39










  • That command may not be the exact command that you need to stop the vm* services. You'll have to research it a little yourself, as I'm not that familiar with vm*, but some of the error messages indicate that your problem might be related. Tell me more about your network config. Do you have two routers?
    – heynnema
    Apr 12 at 15:43















What happens if you disable the vmnet/vfs/vmware?
– heynnema
Apr 12 at 15:31





What happens if you disable the vmnet/vfs/vmware?
– heynnema
Apr 12 at 15:31













@heynnema how do i do that
– kellymandem
Apr 12 at 15:32




@heynnema how do i do that
– kellymandem
Apr 12 at 15:32












I'm not familiar with vmnet/vfs/vmware, but you'd probably start with something like sudo systemctl stop vmnet... or you might have to uninstall it. Also, do you have 2 routers in your network configuration?
– heynnema
Apr 12 at 15:34





I'm not familiar with vmnet/vfs/vmware, but you'd probably start with something like sudo systemctl stop vmnet... or you might have to uninstall it. Also, do you have 2 routers in your network configuration?
– heynnema
Apr 12 at 15:34













@heynnema right now my vmware player is not running so when i run that command i get Failed to stop vmnet.service: Unit vmnet.service not loaded., so i guess it's not the issue
– kellymandem
Apr 12 at 15:39




@heynnema right now my vmware player is not running so when i run that command i get Failed to stop vmnet.service: Unit vmnet.service not loaded., so i guess it's not the issue
– kellymandem
Apr 12 at 15:39












That command may not be the exact command that you need to stop the vm* services. You'll have to research it a little yourself, as I'm not that familiar with vm*, but some of the error messages indicate that your problem might be related. Tell me more about your network config. Do you have two routers?
– heynnema
Apr 12 at 15:43




That command may not be the exact command that you need to stop the vm* services. You'll have to research it a little yourself, as I'm not that familiar with vm*, but some of the error messages indicate that your problem might be related. Tell me more about your network config. Do you have two routers?
– heynnema
Apr 12 at 15:43















active

oldest

votes











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%2f1024385%2funable-to-connect-to-the-internet-through-ethernet%23new-answer', 'question_page');

);

Post as a guest






















active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes















 

draft saved


draft discarded















































 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1024385%2funable-to-connect-to-the-internet-through-ethernet%23new-answer', 'question_page');

);

Post as a guest
































































-

Popular posts from this blog

pylint3 and pip3 broken

Image
Clash Royale CLAN TAG #URR8PPP up vote 0 down vote favorite I have tried sudo apt remove --purge on various packages. I get the same when I reinstall. I have also tried reinstall using aptitude. This does not work. My current workaround is to run pylint3 as root, which works, but is bad practice. pip3 $ pip3 Traceback (most recent call last): File "/usr/lib/python3/dist-packages/pip/_vendor/__init__.py", line 33, in vendored __import__(vendored_name, globals(), locals(), level=0) ImportError: No module named 'pip._vendor.pkg_resources' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/bin/pip3", line 9, in <module> from pip import main File "/usr/lib/python3/dist-packages/pip/__init__.py", line 13, in <module> from pip.exceptions import InstallationError, CommandError, PipError File "/usr/lib/python3/dist-packages/pip/exceptions.py", line 6, ...
Read more

Missing snmpget and snmpwalk

Image
Clash Royale CLAN TAG #URR8PPP up vote 0 down vote favorite I have installed Zabbix appliance, directly preinstalled and found that there is missing snmpwalk and snmpget commands. I tried to install it with: apt-get install net-snmp-utils but I have error message: Unable to locate package. I have also check what from SNMP is preinstalled and there is: libsnmp-base libsnmp30:amd64 snmp-mibs-downloader snmpd snmptrapd snmptrapfmt How can I install snmpget and snmpwalk ? snmp zabbix share | improve this question edited Jan 29 at 10:10 Yaron 8,552 7 18 38 asked Jan 29 at 9:51 Alfista 1 apt install snmp perhaps ? If named differently - apt cache snmp – fugitive Jan 29 at 10:00 add a comment  |  up vote 0 down vote favorite I have installed Zabbix appliance, directly preinstalled and found that there is missing snmpwalk and snmpget commands. I tried...
Read more

How to enroll fingerprints to Ubuntu 17.10 with VFS491

Image
Clash Royale CLAN TAG #URR8PPP up vote 1 down vote favorite I decided to switch from Windows to Ubuntu 17.10, I meet it like 8 years ago and I didn't decided to switch until now (haha). Well, my actual device is an HP Probook 4540s with a Validity fingerprint sensor (VFS491). The fingerprint sensor worked fine on Windows but I can't get it to work in Ubuntu. The device is recognized as 138a:003d but is not detected as a fingerprint scanner by some apps like Fingerprint GUI. I want to use the fingerprint scanner to log in into my user account in Ubuntu but it doesn't supports fingerprints without special software and the drivers of the fingerprint scanner are available for Windows but not for any Linux distribution. I found something on GitHub (https://github.com/eekpie/libfprint) about the integration of the VFS491 in libfprint and I think it can help but I don't know what to do with it, so that's why I need the help of the community to do it since I am...
Read more