IP configuration failed

This problem has been happening for a few days every time I try to connect to the internet using my ethernet cable. It tries to connect for some time but ultimately ends up failing. I tried fixing it by following some procedures (such as this one), but all ended up being unsuccessful. I’ve been using a Wi-Fi adapter for the meantime, which means my machine can connect to the internet, just not through my ethernet cable.

[azarth@blackice ~]$ nmcli device
DEVICE  TYPE      STATE                   CONNECTION 
wlan0   wifi      connected               Mellany    
lo      loopback  connected (externally)  lo         
enp9s0  ethernet  disconnected            --         
[azarth@blackice ~]$ nmcli connection
NAME     UUID                                  TYPE      DEVICE 
Mellany  8277e3c3-6061-4726-bb84-7d2259fe4d82  wifi      wlan0  
lo       170526ec-d457-4395-851b-fcdc0a3e268d  loopback  lo     
wire1    e2030d6b-59b6-36f9-807d-03d61cbb7a63  ethernet  --     
nov 08 01:58:56 blackice NetworkManager[833]: <info>  [1699419536.0930] manager: (enp9s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
nov 08 01:58:56 blackice NetworkManager[833]: <info>  [1699419536.0932] device (enp9s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
nov 08 01:58:58 blackice NetworkManager[833]: <info>  [1699419538.5783] device (enp9s0): carrier: link connected
nov 08 01:58:58 blackice NetworkManager[833]: <info>  [1699419538.5786] device (enp9s0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
nov 08 01:58:58 blackice NetworkManager[833]: <info>  [1699419538.5793] device (enp9s0): Activation: starting connection 'wire1' (e2030d6b-59b6-36f9-807d-03d61cbb7a63)
nov 08 01:58:58 blackice NetworkManager[833]: <info>  [1699419538.5794] device (enp9s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
nov 08 01:58:58 blackice NetworkManager[833]: <info>  [1699419538.5796] device (enp9s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
nov 08 01:58:58 blackice NetworkManager[833]: <info>  [1699419538.5929] device (enp9s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
nov 08 01:58:58 blackice NetworkManager[833]: <info>  [1699419538.5933] dhcp4 (enp9s0): activation: beginning transaction (timeout in 45 seconds)
nov 08 01:59:43 blackice NetworkManager[833]: <info>  [1699419583.3704] device (enp9s0): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
nov 08 01:59:43 blackice NetworkManager[833]: <warn>  [1699419583.3707] device (enp9s0): Activation: failed for connection 'wire1'
nov 08 01:59:43 blackice NetworkManager[833]: <info>  [1699419583.3709] device (enp9s0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
nov 08 01:59:43 blackice NetworkManager[833]: <info>  [1699419583.3988] dhcp4 (enp9s0): canceled DHCP transaction
nov 08 01:59:43 blackice NetworkManager[833]: <info>  [1699419583.3989] dhcp4 (enp9s0): activation: beginning transaction (timeout in 45 seconds)
nov 08 01:59:43 blackice NetworkManager[833]: <info>  [1699419583.3989] dhcp4 (enp9s0): state changed no lease
nov 08 01:59:43 blackice NetworkManager[833]: <info>  [1699419583.4003] device (enp9s0): Activation: starting connection 'wire1' (e2030d6b-59b6-36f9-807d-03d61cbb7a63)
nov 08 01:59:43 blackice NetworkManager[833]: <info>  [1699419583.4004] device (enp9s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
nov 08 01:59:43 blackice NetworkManager[833]: <info>  [1699419583.4005] device (enp9s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
nov 08 01:59:43 blackice NetworkManager[833]: <info>  [1699419583.4145] device (enp9s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
nov 08 01:59:43 blackice NetworkManager[833]: <info>  [1699419583.4150] dhcp4 (enp9s0): activation: beginning transaction (timeout in 45 seconds)
nov 08 02:00:28 blackice NetworkManager[833]: <info>  [1699419628.3733] device (enp9s0): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
nov 08 02:00:28 blackice NetworkManager[833]: <warn>  [1699419628.3736] device (enp9s0): Activation: failed for connection 'wire1'
nov 08 02:00:28 blackice NetworkManager[833]: <info>  [1699419628.3737] device (enp9s0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
nov 08 02:00:28 blackice NetworkManager[833]: <info>  [1699419628.3955] dhcp4 (enp9s0): canceled DHCP transaction
nov 08 02:00:28 blackice NetworkManager[833]: <info>  [1699419628.3955] dhcp4 (enp9s0): activation: beginning transaction (timeout in 45 seconds)
nov 08 02:00:28 blackice NetworkManager[833]: <info>  [1699419628.3956] dhcp4 (enp9s0): state changed no lease
nov 08 02:00:28 blackice NetworkManager[833]: <info>  [1699419628.3968] device (enp9s0): Activation: starting connection 'wire1' (e2030d6b-59b6-36f9-807d-03d61cbb7a63)
nov 08 02:00:28 blackice NetworkManager[833]: <info>  [1699419628.3969] device (enp9s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
nov 08 02:00:28 blackice NetworkManager[833]: <info>  [1699419628.3970] device (enp9s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
nov 08 02:00:28 blackice NetworkManager[833]: <info>  [1699419628.4105] device (enp9s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
nov 08 02:00:28 blackice NetworkManager[833]: <info>  [1699419628.4109] dhcp4 (enp9s0): activation: beginning transaction (timeout in 45 seconds)
nov 08 02:01:13 blackice NetworkManager[833]: <info>  [1699419673.3709] device (enp9s0): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
nov 08 02:01:13 blackice NetworkManager[833]: <warn>  [1699419673.3711] device (enp9s0): Activation: failed for connection 'wire1'
nov 08 02:01:13 blackice NetworkManager[833]: <info>  [1699419673.3713] device (enp9s0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
nov 08 02:01:13 blackice NetworkManager[833]: <info>  [1699419673.4088] dhcp4 (enp9s0): canceled DHCP transaction
nov 08 02:01:13 blackice NetworkManager[833]: <info>  [1699419673.4089] dhcp4 (enp9s0): activation: beginning transaction (timeout in 45 seconds)
nov 08 02:01:13 blackice NetworkManager[833]: <info>  [1699419673.4089] dhcp4 (enp9s0): state changed no lease
nov 08 02:01:13 blackice NetworkManager[833]: <info>  [1699419673.4101] device (enp9s0): Activation: starting connection 'wire1' (e2030d6b-59b6-36f9-807d-03d61cbb7a63)
nov 08 02:01:13 blackice NetworkManager[833]: <info>  [1699419673.4102] device (enp9s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
nov 08 02:01:13 blackice NetworkManager[833]: <info>  [1699419673.4103] device (enp9s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
nov 08 02:01:13 blackice NetworkManager[833]: <info>  [1699419673.4241] device (enp9s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
nov 08 02:01:13 blackice NetworkManager[833]: <info>  [1699419673.4244] dhcp4 (enp9s0): activation: beginning transaction (timeout in 45 seconds)
nov 08 02:01:58 blackice NetworkManager[833]: <info>  [1699419718.3731] device (enp9s0): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
nov 08 02:01:58 blackice NetworkManager[833]: <warn>  [1699419718.3734] device (enp9s0): Activation: failed for connection 'wire1'
nov 08 02:01:58 blackice NetworkManager[833]: <info>  [1699419718.3736] device (enp9s0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
nov 08 02:01:58 blackice NetworkManager[833]: <info>  [1699419718.3922] dhcp4 (enp9s0): canceled DHCP transaction
nov 08 02:01:58 blackice NetworkManager[833]: <info>  [1699419718.3922] dhcp4 (enp9s0): activation: beginning transaction (timeout in 45 seconds)
nov 08 02:01:58 blackice NetworkManager[833]: <info>  [1699419718.3922] dhcp4 (enp9s0): state changed no lease

I’ve also tried to connect to the internet on the LiveISO to see if it was some issue with packages or perhaps something else, but I have had the same results.

did you change the cable and restart your DHCP server?
Wired networks should work plug and play, as long as a working DHCP server is in the network (usually the router does that).
If it fails even on Live ISO and restarts also don’t fix it, my suggestion would be hardware fault.

1 Like

did you change the cable and restart your DHCP server?

I didn’t try to change the cable, mostly because I don’t have another cable right now - however, will do as soon as possible as I get a new one. As for restarting the DHCP server, I’m not really sure how I should go about doing this on NetworkManager. I could only find people doing this on dhcpcd.

If it fails even on Live ISO and restarts also don’t fix it, my suggestion would be hardware fault.

That’s also what I originally thought. I just want to make sure I exhaust all other possibilities before buying or changing any hardware.

whats special about your Network?
Like I said, usually the DHCP server is in the router that connects your home network to the internet.

whats special about your Network?
Like I said, usually the DHCP server is in the router that connects your home network to the internet.

There should be nothing special? Also, that information about the DHCP server doesn’t really tell me much.

Let’s say, the DHCP server is indeed located in the router. Are you saying I just have to restart the router or do I have to do something else entirely?

I understand barely anything about the technicalities of internet connections. I’m really gonna need you to hold my hand here.

a DHCP server is a piece of code (usually integrated in the router software) that tells each device on the network which IP adress and netmask it has to use, what the default nameserver is (so that for example www.google.com get’s resolved into an ip adress that the browser then can connect to) and which device IP provides the internet connection (usually the routers own IP adress).
Usually, there is also a configuration option where you can tell which mac adress should receive which IP adress if you need to use specific fixed IP adresses (usually for NAS or network printers or in large networks where each machine needs to use a specific IP for management reasons).

So yes, looking into your router logs might tell you if there is something wrong with your machine receiving an IP adress via cable and restarting your router also restarts your DHCP server.

1 Like

I am pretty sure I checked it thoroughly, but it seems there are no useful logs. Also, I have tried restarting the router twice, but no success, which is unfortunate.

Thank you for the explanation!

I am beginning to worry that something hardware-related is the cause of this - I will get another cable over the next few days, and if that doesn’t work, then I will switch my network card as a last resort. If you know anything else I can do to try and solve this problem, please tell me.

think i would borrow a friends router and check my card before just replacing it and finding out the issue was the router

I would love to, but that’s not really possible. I’d have to buy an entire new router in this case.

Also, wouldn’t that be strange though? Everyone in the house can connect to it via Wi-Fi just fine, including my very machine that is having problems connecting. Which would mean Wi-Fi connection works, but cabled doesn’t. It gets even stranger when considering the fact that this started happening only four days ago. It’s very strange if that were to be case, since that would entail the router just spontaneously stopped working as intended for no clear reason, out of nowhere. Still, that’s a possibility, but I do wonder if that really is what happened.

Okay, this has been officially the weirdest experience I have ever had with an error, ever. Just as the error caused itself in the first place for no apparent reason, it just fixed itself for no apparent reason. I swear I didn’t even do anything, I just woke up today and the cabled connection works.

Still, thank you, everyone who helped.

Nevermind, apparently it just started happening again?? Once again, I did nothing to make it stop working. It just did by itself.

I am so confused as to what is actually happening and why. I genuinely have no idea what is causing this.

The problem is finally resolved! It was a problem with the ISP and I had to switch my internet service entirely. Nothing to do with the cable, network card, or router.

Thank you everyone!

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.