Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I run a small server w/ CentOS 5.8. It's main function is as a samba fileserver.
It has a static IP, and was working until last night. I got a call that the network was down, and when I got to the office it was the only machine without a connection. It's on a wired connection that's plugged directly into the switch rack. I also moved it directly into the router, which didn't work. I've also tried the usual boring stuff (rebooting the network service in init.d, etc.). Nothing seems to be working :/
I'm no expert with logs in linux, is there a network log that I can find? What's the best troubleshooting step to see what's going wrong with the machine?
After investigating a bit further, I'm pretty sure this is a NIC hardware issue. I haven't had time to test much. The NIC still shows on lspci, and I am seeing just the green light on the back on the CPU where the ethernet is plugged in. eth0 is running as well, which really makes me think this is hardware related. How known are NICs for just dying, but still appearing to function?
I'm going to boot to a LiveCD tonight to test it. I'll post any results, and as usual, any advice is much appreciated
A really weird thing happened yesterday. I was sitting in my chair wondering why the NIC would crap out on me out of nowhere. I built this machine myself, so I was about to crack it open as I noticed that the power cable was a tad loose. I had already begun setting up a new server and was going to clone all of our data over to it. When I plugged the power cable back in all the way (it had ~1/4 inch to go), the computer booted up and was running at normal speed with an internet connection.
I'm a EECS major in college, and I'm REALLY curious as to why this happened - did lack of power or signal flow somehow temporarily sieze the mobo and [for some reason] the peripherals and components weren't getting the right voltage or current? Probably going to start another thread about this...
Lesson learned - before you troubleshoot a "dead" NIC, unplug everything, open it up, make sure it's all good, plug everything back in, and give it 1 more go before you throw the flag.
Wow. I'm not qualified enough as an electrician to have an idea. My guess would be that there wasn't enough contact between the surfaces to allow an adequate flow of current, but that is a guess based on complete and total ignorance. Or perhaps a bit of corrosion built up on the contacts and reseating the cable cleaned it off.
Your troubleshooting principle is excellent though. Even when it's likely not a hardware problem, five minutes of reseating cables and other simple hardware tests are quick and easy and can save hours of agonizing over software.