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've been setting up an experimental Linux Server (RH 9.0) with OpenSSHd, Apache, ProFTPd, MySQL and PHP activated for my employer.
The server has a static IP-address and a valid DNS entry, and from time to time it works just fine, it responds to DNS and IP calls with no problem at all - including all servers.
Then, after a couple of hours, I lose the possibility to connect to the server from the outside world. It just doesn't respond, and I get time out-messages on SSH and not responding-messages on HTTP.
The "solution" for breaking the server's isolation is to call it from a machine on the same local network (ie another corporate server).
For instance, I've found solutions to include
a) make an SSH-call from a machine with IP xxx.xxx.xxx.2 (my server being xxx.xxx.xxx.8), and my server starts communicating with other networks after a couple of seconds
b) send a dummy e-mail from our mailserver (xxx.xxx.xxx.5) to my server (to a non existant recipient, causing the mail to bounce - my firewall is for that matter configured to drop mail, and no mail servers are activated).
But nevertheless I get the same result as in a) - a functioning server...
I've checked my log files and I can't find anything quite matching the time the server stopped responding.
Is there anyone who experienced a similar problem?