I’m having trouble getting an IP address via DHCP on my HP ProLiant DL380 Gen9 server running Debian. I’ve tried various troubleshooting steps, but nothing seems to work.

Error messages:

  • “No DHCPOFFERS received”
  • “No working leases in persistent database - sleeping”
  • “Activation of network connection failed” (GNOME)
  • “IP configuration unavailable” (Plasma)

Hardware:

  • HP ProLiant DL380 Gen9 server

Software:

  • Debian operating system
  • GNOME and Plasma desktop environments

Troubleshooting steps:

  • Checked network cable and ensured it’s properly connected
  • Restarted network service
  • Set /etc/NetworkManager/NetworkManager.conf managed=true

Additional information:

  • Internet worked during the Debian installation process, but not after booting into the installed system.
  • The problem occurs on both GNOME and Plasma desktop environments, but Plasma provides a slightly more helpful error message.

I’d appreciate any help or guidance on resolving this issue. Has anyone else experienced similar problems with DHCP on a HP ProLiant DL380 Gen9 server with Debian?

  • JackGreenEarth@lemm.eeOPEnglish
    1·
    2 months ago

    It’s not doing what it was before now, now it’s just showing the ‘activation of network connection failed’ error. But before when I ran the up command it had the connected sign, and said it was connected in the GUI, but when I tried accessing any website it wasn’t able to, and I don’t have any firewall installed, so I assumed that the connection wasn’t working.

    The result for ip address show ens6f1 is now the same as before

    12: ens6f1: <BROADCAST, MULTICAST, UP, LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 14:02:ec:7d:52:f1 brd ff:ff:ff:ff:ff:ff
    altname enp129s0f1
    inet6 fe80::1602::ecff::fe7d::52f1/64 scope link noprefixroute
    valid_lft forever preferred_lft forever

    • bloodfart
      2·
      2 months ago

      I think you’ve got someone helping you with this who’s working with you inside the gui. Rather than cause problems by asking you to try different command line troubleshooting steps that may work at cross purposes with that other thread of assistance, I’m gonna bow out.

      If you run into a wall, reboot your server and reply to this post and lll jump back in.