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?

  • hungover_pilot@lemmy.world
    link
    fedilink
    arrow-up
    2
    ·
    2 months ago

    If you set a static ip can you get connectivity? Have you confirmed that your interface is still up via Ifconfig or ip link?

    • JackGreenEarth@lemm.eeOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      2 months ago

      I wouldn’t know how to do that. Would I have to find out what specific IP to set it to, or would any random one work?

      • Possibly linux@lemmy.zip
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 month ago

        You need an IP that is in the same subnet as the rest of the network. Take your gateway IP and then find the subnet mask. (It is probably a /24 which is 255.255.255.0)

        Next pick a random ending number (x.x.x.67 for example). Try to ping it from a different device to make sure that it isn’t in use. Once you do that you can set it on the server. Go to network and then set it to manual. Set the IP, subnet mask and gateway IP. Then try to ping the gateway. If that fails you have a layer 1 problem (hardware)

        • JackGreenEarth@lemm.eeOP
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 month ago

          I set the manual ipv4 to 192.168.0.72, and it says it’s connected - it doesn’t have any ‘activation of network connection failed’ error messages, but it doesn’t seem to actually have any internet either