Unable to get IP address via DHCP on HP ProLiant DL380 Gen9 with Debian
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?
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
Hmm. One way to check multiple options at once is to try the install again and see it internet is still present when installing the OS, as it was before. If it is, that would rule out a hardware issue.
I tried what I said, reinstalling to see if it still had internet. It did not. Therefore I went into a rabbithole of trying to rule out specific things of why it was working then but not now, and I still have no idea why it was working then, but I have plugged the Ethernet powerline into a new, more inconvenient, plug socket, and the wired internet is mostly working! I can still access most sites, but Firefox won't connect to addons.mozilla.com or accounts.firefox.com. Idk if that's a Firefox issues or a network issue, but it's mostly working now, which is great!