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.
The Culprit: Debian Etch File server (Samba & NFS exports)
Attached: Windows XP
Attached: Kunbuntu Feisty Fawn
Attached: Laptop, Dual Kunbuntu/ Windows XP
Other Windows machines on network, but are not linked to server.
The Network interface freezes up on occasion. Anywhere between immediately, and week or so. When frozen, even communication with itself via web interface is impossible.
I can solve this by stopping and starting the Eth interface. (Sometimes Smb needs to be restarted afterward.) However, the most prolonged up times involved a complete shutdown and restart.
I have changed the network cards, (disabled onboard via BIOS, and installed new working one from another machine) still with the same results.
I have also shut down all Windows machines and continue to have this problem.
When in this state, an attempt at communication with the machine does not return an error (as if the device was shut down) but continues attempting before eventually timing out.
I Have no idea what could be causing this. I have had the same setup before with the server being RedHat ES without an issue.
To answer the question in the subject line, yes. My Debian Etch file server serves up files by nfs to my Linux computers and by samba to my Windows computers. No problems.
Since you've already swapped network cards, my guess is a hardware issue with the router/switch. I recently put together a new web server and had frustrating problems with the ethernet connection constantly going down and up. Naturally, I suspected the NIC and consumed a lot of time troubleshooting it.
Turned out one port on my router was flakey. I switched to a different port and all of my problems evaporated.
Yesterday I would say your idea may be a one of many possibilites. Today however...
I took down one of the machines that was using the NFS export and it seemed to solve the problem.
I like the router Idea more and more... Except in my house it is not that simple. I have a Dlink wireless router (514?) plus a 24 port switch, and I threw in an old linsys router (used as a switch) because three network ports wasn't enough in my bedroom (how many couples do you know that fight over three network plugs). Additionally one of the plugs on the linksys is out of commision. any number of these could be a weak link in the chain. I had to reboot the router today to get my PDA to work wirelessly (not common)
:sigh: lots of long term troubleshooting ahead of me.