Page 1 of 3 123 LastLast
Results 1 to 10 of 24

Thread: Built PC Can Not Connect to Network, both 18.04 AND 16.04 (Hardline)

  1. #1
    Join Date
    Jan 2010
    Location
    Pleasant Hill, Missouri
    Beans
    170
    Distro
    Ubuntu 18.04 Bionic Beaver

    Built PC Can Not Connect to Network, both 18.04 AND 16.04 (Hardline)

    Hello!

    I just built my first computer and am putting Ubuntu on it! We are having some major problems however...

    I can not connect to the internet via ethernet. It first started with the built in LAN supported chip provided by the motherboard. Ten hours of work later and no progress, so I went out and bought a PCIe Gigabit NIC. And guess what?! It doesn't work either.. I just so happen to have two drives with two different OS's (16.04, 18.04) in the machine and neither can connect, both show the same symptoms. I can confirm without a shadow of a doubt this is a problem with my computer and not the network it is tied to. Furthermore, I have tried this on multiple networks with he same result. Here is the motherboard I am using: https://www.asus.com/us/Motherboards/TUF-X299-MARK-2/

    This is what I have worked out so far;

    ifconfig -a
    Code:
     enp0s31f6 Link encap:Ethernet  HWaddr 18:31:bf:6d:3f:3c  
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:100 errors:0 dropped:9 overruns:0 frame:0
              TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000 
              RX bytes:12841 (12.8 KB)  TX bytes:0 (0.0 B)
              Interrupt:20 Memory:92f00000-92f20000 
    
    enp23s0   Link encap:Ethernet  HWaddr 00:e0:4c:89:20:45  
              inet6 addr: fe80::be61:d815:c5fc:11c2/64 Scope:Link
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:164 errors:0 dropped:9 overruns:0 frame:0
              TX packets:364 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000 
              RX bytes:63818 (63.8 KB)  TX bytes:69682 (69.6 KB)
    
    lo        Link encap:Local Loopback  
              inet addr:127.0.0.1  Mask:255.0.0.0
              inet6 addr: ::1/128 Scope:Host
              UP LOOPBACK RUNNING  MTU:65536  Metric:1
              RX packets:17150 errors:0 dropped:0 overruns:0 frame:0
              TX packets:17150 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1 
              RX bytes:10541135 (10.5 MB)  TX bytes:10541135 (10.5 MB)
    *Note* Sometimes the inet6 line will appear, sometimes not. It depends on which ethernet connection the computer is trying to connect to at that moment in time. This is in regards to "enp0s31f6" and "enp23s0". Again, the outcomes for both connections are the same. I simply am adding them both in the print out to save time.

    lspci -nnk | grep 0200 -A2
    Code:
     00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (2) I219-V [8086:15b8]
        Subsystem: ASUSTeK Computer Inc. Ethernet Connection (2) I219-V [1043:8672]
        Kernel driver in use: e1000e
    --
    17:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 07)
        Subsystem: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:0123]
        Kernel driver in use: r8169
    dmesg | grep e100
    Code:
     [    0.901950] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
    [    0.901951] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
    [    0.952298] e1000e 0000:00:1f.6: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
    [    1.300354] e1000e 0000:00:1f.6 eth0: registered PHC clock
    [    1.300356] e1000e 0000:00:1f.6 eth0: (PCI Express:2.5GT/s:Width x1) 18:31:bf:6d:3f:3c
    [    1.300357] e1000e 0000:00:1f.6 eth0: Intel(R) PRO/1000 Network Connection
    [    1.300441] e1000e 0000:00:1f.6 eth0: MAC: 12, PHY: 12, PBA No: FFFFFF-0FF
    [    1.301790] e1000e 0000:00:1f.6 enp0s31f6: renamed from eth0
    [   53.429975] e1000e: enp0s31f6 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
    [   53.429977] e1000e 0000:00:1f.6 enp0s31f6: 10/100 speed: disabling TSO
    *Note* As far as I can tell, in these last two lines, I establish a connection and then it fails shortly after.

    In summary, both devices on both OS's and two different networks perform exactly the same with the same symptoms. From what I can tell both devices make an attempt at connection and then fall short. As for why, I have no idea. I am not sure where to go from where I am at other than to boot the system on Windows and see if there is a change. But this is Ubuntu Forums, I'm sure we can figure it out before I succumb to the dark side. 😛

    Any and all help is appreciated. I am banging my head against a wall over here and until this problem is solved all I have is a $2,000 paper weight.

    Thanks,
    Matt
    Last edited by muddpup64; June 25th, 2018 at 04:48 PM. Reason: more info added

  2. #2
    Join Date
    Jan 2010
    Location
    Pleasant Hill, Missouri
    Beans
    170
    Distro
    Ubuntu 18.04 Bionic Beaver

    Re: Built PC Can Not Connect to Network, both 18.04 AND 16.04 (Hardline)

    Bump

    This expensive paper weight is kicking my ass. I posted this here in hopes it would have more eyes on it. If it needs to be moved to a more appropriate section, can a mod please do so?

  3. #3
    Join Date
    Feb 2008
    Location
    Texas
    Beans
    27,721
    Distro
    Ubuntu 18.04 Bionic Beaver

    Re: Built PC Can Not Connect to Network, both 18.04 AND 16.04 (Hardline)

    Thread moved to Networking & Wireless for a more appropriate fit.

  4. #4
    Join Date
    Jun 2009
    Location
    SW Forida
    Beans
    Hidden!
    Distro
    Ubuntu

    Re: Built PC Can Not Connect to Network, both 18.04 AND 16.04 (Hardline)

    My Asus motherboard is older. But same kernel driver, but using e1000e, but no mention of the r8169. Do you have dual ports with different drivers? Perhaps conflicts?

    [ 1.008442] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
    [ 1.008442] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
    [ 1.008618] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
    [ 1.080961] e1000e 0000:00:19.0 0000:00:19.0 (uninitialized): registered PHC clock
    [ 1.149682] e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) 10:c3:7b:6e:0c:af
    [ 1.149683] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
    [ 1.149711] e1000e 0000:00:19.0 eth0: MAC: 11, PHY: 12, PBA No: FFFFFF-0FF
    [ 1.150227] e1000e 0000:00:19.0 eno1: renamed from eth0
    [ 7.606202] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
    For more info on UEFI boot install & repair - Regularly Updated :
    http://ubuntuforums.org/showthread.php?t=2147295
    Please use Thread Tools above first post to change to [Solved] when/if answered completely.

  5. #5
    Join Date
    Jan 2010
    Location
    Pleasant Hill, Missouri
    Beans
    170
    Distro
    Ubuntu 18.04 Bionic Beaver

    Re: Built PC Can Not Connect to Network, both 18.04 AND 16.04 (Hardline)

    Quote Originally Posted by oldfred View Post
    My Asus motherboard is older. But same kernel driver, but using e1000e, but no mention of the r8169. Do you have dual ports with different drivers? Perhaps conflicts?
    The r8169 is the driver for a second PCIe NIC I installed. After no success with the native LAN I bought it in hopes I could get it to work. Here it the print out after I remove the second NIC:

    Code:
     muddpup@********:~$ ifconfig -a
    enp0s31f6 Link encap:Ethernet  HWaddr xx:xx
              inet6 addr: fe80::653e:c5c5:c0b:eba0/64 Scope:Link
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:16 errors:0 dropped:0 overruns:0 frame:0
              TX packets:38 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000 
              RX bytes:8965 (8.9 KB)  TX bytes:7063 (7.0 KB)
              Interrupt:20 Memory:92f00000-92f20000 
    
    lo        Link encap:Local Loopback  
              inet addr:127.0.0.1  Mask:255.0.0.0
              inet6 addr: ::1/128 Scope:Host
              UP LOOPBACK RUNNING  MTU:65536  Metric:1
              RX packets:10297 errors:0 dropped:0 overruns:0 frame:0
              TX packets:10297 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1 
              RX bytes:2758010 (2.7 MB)  TX bytes:2758010 (2.7 MB)

    Woah, one of my print outs changed. Check this out:

    Code:
     muddpup@********:~$ dmesg | grep e1000
    [    0.913898] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
    [    0.913899] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
    [    0.947540] e1000e 0000:00:1f.6: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
    [    1.260728] e1000e 0000:00:1f.6 eth0: registered PHC clock
    [    1.260729] e1000e 0000:00:1f.6 eth0: (PCI Express:2.5GT/s:Width x1) 18:31:bf:6d:3f:3c
    [    1.260730] e1000e 0000:00:1f.6 eth0: Intel(R) PRO/1000 Network Connection
    [    1.260800] e1000e 0000:00:1f.6 eth0: MAC: 12, PHY: 12, PBA No: FFFFFF-0FF
    [    1.262135] e1000e 0000:00:1f.6 enp0s31f6: renamed from eth0
    [  192.682984] e1000e: enp0s31f6 NIC Link is Down
    [  236.770497] e1000e: enp0s31f6 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
    [  236.770504] e1000e 0000:00:1f.6 enp0s31f6: 10/100 speed: disabling TSO
    [  245.277787] e1000e: enp0s31f6 NIC Link is Down
    [  250.146240] e1000e: enp0s31f6 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
    [  250.146247] e1000e 0000:00:1f.6 enp0s31f6: 10/100 speed: disabling TSO
    [  272.573177] e1000e: enp0s31f6 NIC Link is Down
    [  275.474131] e1000e: enp0s31f6 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
    [  275.474138] e1000e 0000:00:1f.6 enp0s31f6: 10/100 speed: disabling TSO
    Correct me if I'm wrong, but isn't it making multiple attempts at a connection and then failing? The ending is the same as before however: " e1000e 0000:00:1f.6 enp0s31f6: 10/100 speed: disabling TSO "
    But ya oldfred, my on board NIC using the same driver as yours, "e1000e".
    Last edited by oldfred; June 26th, 2018 at 04:27 AM. Reason: more info found, removed Mac
    He who asks is a fool for five seconds, but he who does not ask is a fool forever.

  6. #6
    Join Date
    Jan 2010
    Location
    Pleasant Hill, Missouri
    Beans
    170
    Distro
    Ubuntu 18.04 Bionic Beaver

    Re: Built PC Can Not Connect to Network, both 18.04 AND 16.04 (Hardline)

    I had a suspicion it is attempting to only connect via IPv6. I did an experiment with a know good machine and it turns out both networks I tested on have no IPv6 support.

    So, is there any thing I can do to give my machine IPv4 support?

    Or is this on a hardware level? I would not think so. I bought another NIC (which I have mentioned) and it did not work either.
    He who asks is a fool for five seconds, but he who does not ask is a fool forever.

  7. #7
    Join Date
    Jun 2009
    Location
    SW Forida
    Beans
    Hidden!
    Distro
    Ubuntu

    Re: Built PC Can Not Connect to Network, both 18.04 AND 16.04 (Hardline)

    Best not to post MAC.

    Do you have Internet icon in upper right corner.
    Does it show IP4?
    Or edit connections.

    They changed, and I do not know details of new way of configuring Internet.
    Mine just worked.
    For more info on UEFI boot install & repair - Regularly Updated :
    http://ubuntuforums.org/showthread.php?t=2147295
    Please use Thread Tools above first post to change to [Solved] when/if answered completely.

  8. #8
    Join Date
    Jan 2010
    Location
    Pleasant Hill, Missouri
    Beans
    170
    Distro
    Ubuntu 18.04 Bionic Beaver

    Re: Built PC Can Not Connect to Network, both 18.04 AND 16.04 (Hardline)

    The top right corner of the desktop gui? No, it just has the normal ethernet symbol.

    I know for sure one of the networks only supports IPv4 because it's owner set it up that way. As for the other network, I attempted to connect while forcing IPv6 and was unable to connect. As soon as you turn on IPv4, it works again.

    I do have the option to edit connection however. If that is what you are asking.

    I can send screenshot later tonight but I am at work right now.

  9. #9
    Join Date
    Jun 2009
    Location
    SW Forida
    Beans
    Hidden!
    Distro
    Ubuntu

    Re: Built PC Can Not Connect to Network, both 18.04 AND 16.04 (Hardline)

    Then is router set to restrict who can connect and your system is not in list that works?
    For more info on UEFI boot install & repair - Regularly Updated :
    http://ubuntuforums.org/showthread.php?t=2147295
    Please use Thread Tools above first post to change to [Solved] when/if answered completely.

  10. #10
    Join Date
    Jan 2010
    Location
    Pleasant Hill, Missouri
    Beans
    170
    Distro
    Ubuntu 18.04 Bionic Beaver

    Re: Built PC Can Not Connect to Network, both 18.04 AND 16.04 (Hardline)

    I forgot to mention a crucial piece of information. The machine I was able to connect with IPv4 is NOT the same machine I am having problems with. It is a separate device whose only purpose is to act as a known good. The machine I am having problems with won't connect AT ALL.

    As for a system blacklist, ya, there is no such thing on both networks.
    Last edited by muddpup64; June 26th, 2018 at 03:24 PM.

Page 1 of 3 123 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •