January 2, 20251 yr Morning all. I'm currently unable to connect to the GUI using the IP, local host etc and my server is unable to connect to the router. I had an ATX motherboard, switched to an ITX, proceeded to change the IP in Unraid to be static to my old ATX IP. Then I wanted to do some testing on the old ATX board, swapped it back in and the GUI is simply unavailable. My router doesn't show it as connected in Unraid, but shows it connected when booting into windows on the same hardware. When I first booted into windows, the computer did not have access to the internet. I disabled the LAN in BIOS, started it, shutdown, enabled and then windows connected fine. Maybe pure luck and just needed a second time? I've performed the following: Confirmed the cable is good. The same system will boot into windows and connect to the internet just fine. Router detects system in Windows. Changed the IP address in network.cfg to another and still no go. Deleted network.cfg. System just states no IP address set when booted. Factory reset router. I'm at a complete loss here that the same hardware connects to the internet just fine via windows but not in Unraid. Anyone have any suggestions? Thanks for your help. Diagnostics attached tower-diagnostics-20250101-1645.zip Edited January 2, 20251 yr by Jlomb436 Forgot to attach Diag. Thanks.
January 2, 20251 yr Author 7 minutes ago, Squid said: No they're not My mistake. Just attached to original post. Thank you.
January 2, 20251 yr Community Expert I am going to make an assumption here: From this in the network,cfg, I assume that you are using a static IP address. USE_DHCP[0]="no" The problem with a static IP address is that it should be permanently assigned in the router. How the router knows that which NIC to assign to that address is determined by the MAC address of the NIC. When you changed the MB, the NIC has a different MAC address. You should properly check the router and straighten out things there. The other way to do it is edited that network.cfg file and change that line to USE_DHCP[0]="yes" And restart the server so that the route assigns an IP address using DHCP. (Note that doing it this way, you will probably end up with a new IP address!!) Read your router manual to see how to permanently assign that IP address to that MAC address. Edited January 2, 20251 yr by Frank1940
January 2, 20251 yr Author 2 minutes ago, Frank1940 said: I am going to make an assumption here: From this in the network,cfg, I assume that you are using a static IP address. USE_DHCP[0]="no" The problem with a static IP address is that it should be permanently assigned in the router. How the router knows that which NIC to assign to that address is determined by the MAC address of the NIC. When you changed the MB, the NIC has a different MAC address. You should properly check the router and straighten out things there. The other way to do it is edited that network.cfg file and change that line to USE_DHCP[0]="yes" And restart the server so that the route assigns an IP address using DHCP. (Note that doing it this way, you will probably end up with a new IP address!!) Read your router manual to see how to permanently assign that IP address to that MAC address. Thanks! I did try this by deleting the config, rebooted and it simply just states that "IP not set". Router shows it offline. I'm guessing the router shows it offline and doesn't assign an IP because of something within Unraid, as Windows works perfect. # Generated settings: IFNAME[0]="br0" DHCP_KEEPRESOLV="no" DHCP6_KEEPRESOLV="yes" BONDNAME[0]="bond0" BONDNICS[0]="eth0 eth1 eth2 eth3" BONDING_MODE[0]="1" BONDING_MIIMON[0]="100" BRNAME[0]="br0" BRNICS[0]="bond0" BRSTP[0]="no" BRFD[0]="0" PROTOCOL[0]="ipv4" USE_DHCP[0]="yes" USE_DHCP6[0]="" SYSNICS="1"
January 2, 20251 yr Community Expert Post new diagnostics from after you made the change in a NEW post!!!! . Edited January 2, 20251 yr by Frank1940
January 2, 20251 yr Author 12 minutes ago, Frank1940 said: Post new diagnostics from after you made the change in a NEW post!!!! . Deleted network.config again, booted and ran diagnostics. See attached. I know every little about networking, but looking at my system log, I do see lots of : Jan 1 16:44:12 Tower kernel: eth0: pci link is down Jan 1 16:44:12 Tower kernel: . Jan 1 16:44:12 Tower kernel: eth0: cmd = 0xff, should be 0x07 I did install realtek drivers from the store to try and force my 2.5 NIC into functioning ASPM so I'm not sure if that's what that is. But I did this a week ago and didn't have any issues until the 2nd change back into the original mobo. tower-diagnostics-20250102-0533.zip Edited January 2, 20251 yr by Jlomb436
January 2, 20251 yr Community Expert From the diagnostics file, this item indicates that there is a problem with the NIC, the Ethernet cable and/or the router/switch port. Settings for eth0: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full 2500baseT/Full Supported pause frame use: Symmetric Receive-only Supports auto-negotiation: Yes Supported FEC modes: Not reported Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full 2500baseT/Full Advertised pause frame use: Symmetric Receive-only Advertised auto-negotiation: Yes Advertised FEC modes: Not reported Speed: 2500Mb/s Duplex: Full Auto-negotiation: on Port: Twisted Pair PHYAD: 0 Transceiver: internal MDI-X: Unknown Supports Wake-on: pumbg Wake-on: d Current message level: 0x00000033 (51) drv probe ifdown ifup -------->>>>>> Link detected: no <<<<<____
January 2, 20251 yr Author 10 minutes ago, Frank1940 said: From the diagnostics file, this item indicates that there is a problem with the NIC, the Ethernet cable and/or the router/switch port. Settings for eth0: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full 2500baseT/Full Supported pause frame use: Symmetric Receive-only Supports auto-negotiation: Yes Supported FEC modes: Not reported Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full 2500baseT/Full Advertised pause frame use: Symmetric Receive-only Advertised auto-negotiation: Yes Advertised FEC modes: Not reported Speed: 2500Mb/s Duplex: Full Auto-negotiation: on Port: Twisted Pair PHYAD: 0 Transceiver: internal MDI-X: Unknown Supports Wake-on: pumbg Wake-on: d Current message level: 0x00000033 (51) drv probe ifdown ifup -------->>>>>> Link detected: no <<<<<____ Thank you. I would say I've ruled out all 3 of those as the NIC is being used to connect to the internet in Windows. Same cable, same router. I'm typing to you from the exact hardware used. Switch lights up green and amber when connected in Windows and in Unraid. I'm really at a loss here. I will try removing the Realtek driver plugin from the boot drive as I'm not sure what else to do.
January 2, 20251 yr Author Solution Solved! Drivers! That was it. My lord. For anyone experiencing this in the future, I had installed the Realtek Drivers for 2.5gb NIC 8125 via apps in addition to making an exception in the modprobe folder where I forced ASPM. That was: Create r8125.conf in /boot/config/modprobe.d with the following content: options r8125 aspm=1 options r8125 eee=0 I deleted that file along with the plugin and boom, I was in. Thanks for your suggestions Frank. Made me start to dig a little deeper on what I had done previously. Edited January 2, 20251 yr by Jlomb436
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.