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?

  • Possibly linuxEnglish
    2·
    2 months ago

    How did you set it up? Did you just plug it in and forget about it?

      • Possibly linuxEnglish
        2·
        2 months ago

        Oh

        Is your phone connected to WiFi? What do the network settings show on your phone?

            • JackGreenEarth@lemm.eeOPEnglish
              1·
              2 months ago

              I tried changing the IP in manual settings, I’m not sure how I ping an IP, I assume it’s a command that I don’t know, but as the screenshots show, accessing a website didn’t work. I saw an IP in the startup menu and tried that but it didn’t seem to work

                • JackGreenEarth@lemm.eeOPEnglish
                  1·
                  2 months ago

                  Why is that? I applied the change, and restarted the Ethernet connection, but I still don’t have internet

                  • Possibly linuxEnglish
                    2·
                    2 months ago

                    You have a upstream issue then. I would start by checking the physical port and then work your way up until you find the fault.

                    It is also possible you have a bad network card as this is older hardware