Connection issue with Linux on the network, not visible on the router.
Connection issue with Linux on the network, not visible on the router.
I figured networking would be better to post this problem consideing it's a network problem, not an OS problem. So, recently I've upgraded a system I use as a general home server for hosting an occasional game server and a few discord bots. I upgraded the motherboard, CPU and memory. Before the upgrade, the system worked flawlessly (albeit not strong enough to handle the servers I wanted, but it worked), connected to a switch that's connected to my router, both via ethernet cable. I experienced no errors, staying online and stable for easily over a month. However, after the upgrade, I cannot connect it back to my network. While I was throwing the parts in, I had moved the cable for the server directly to the router (eliminates a bottleneck from an old cable between router and switch). Once I got the system back and working, I plugged in the cable and tried to remote into it, but it never showed up. I threw a monitor onto it and found it wouldn't connect to anything at all. Following this discovery, I've been combing through the Internet and Ubuntu documentation, trying different solutions that didn't work. Eventually, I gave up and backed up everything important and reinstalled the whole OS (hey, sometimes nuking works, right?). I knew when I had originally installed Linux, it was able to configure the network just fine. However, nothing changed after the clean install. I've tried with static and dynamic ip. Nothing I've done has worked. This morning, I moved the cable to the original position on the switch, but nothing happened at all. At that point, I decided to check the connected devices according to my router, and curiously enough, it did not show there. No wired connection on the list met the description of my server. This makes me believe that the router has never encountered any traffic or anything at all from the server, which is really odd considering it was directly attached to it. I am at my wit's end right now about this. I've done everything I can think to do. I need y'all's help with this, cause there are people waiting for it to come back online. I can't try out any solutions until tomorrow morning at the earliest, and that's only for a brief period of time. The exact OS is a server version of Ubuntu 16.04 (with no GUI, just a terminal). The parts upgrade were: Motherboard: gigabyte 970a-ds3p CPU: AMD FX-6300 RAM: HyperX FURY 1x8gb The rest of the parts were pulled from some old low power systems (such as a sketchy PSU and a couple old hard drives). I've tried too many things to detail exactly what I've done in one post, however if you were to ask specifically, I'd be able to detail it for you. I appreciate any help I can get. Even failed solutions are good, cause they just narrow it down and remove what doesn't work.
The command returns details about network configuration and system status. The `dmesg | grep eth0` output shows kernel messages related to the eth0 interface, such as driver status or errors.
Can't locate either device at the moment. I'm waiting until tomorrow morning for a short time to try again. From what I recall, ifconfig displayed the expected results and identified the port correctly. I haven't tested the second option yet. The system doesn't have a network card installed; it's built into the motherboard and works fine with the port.
You're sure you've got someone behind the wheel? Every clue suggests there isn't one...
Instead of running dmesg, try searching dhcp /var/log/syslog later. Also, a properly set static configuration should have resolved the issue.
All systems need drivers for their hardware components. It seems your new motherboard's network chipset might not be detected by Ubuntu without a proper driver, which explains why you're facing issues.
I initially used a static IP address, but it didn’t work either. That makes sense. The linked posts seem quite alike. I’ll try again tomorrow morning. The main issue now is figuring out how to install a driver via the terminal—probably needing a flash drive without an internet connection.
You'd need to install the correct driver, preferably in an easy-to-use .deb format, and use sudo for installation. If you're working on a Linux server, make sure you understand these steps.