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.
In my job's infinite wisdom, they fired the old UNIX/Linux sys admin that was my senior. My team currently has an outdated system where the master and backup NIS+ servers are run on Solaris 9 machines. The rest of are machines, the clients, that we are trying to access are Red Hat Enterprise Linux 4.8 AS machines. When attempting to access these client machines with SSH we can get as far as reaching them on the network and be prompted a warning banner and password. However, it will keep asking us for our password over and over again as if it was incorrect. These same issues arise when we attempt to login in locally with the machine and not just SSH.
When a hard reset was attempted on the problem, I noticed that the NIS service successfully binds but receives a failure when it attempts to listen. The ntpd service also fails as well. Our team's LAN/WAN network administrator states that there are no firewall rules blocking the ports necessary to run these. If anyone can give me some guidance or assistance I would be most grateful. I'm trying to read up on NIS+, but I just stare at it blankly feeling completely lost as I am still a newbie UNIX/Linux administrator.
Please post your thread in only one forum. Posting a single thread in the most relevant forum will make it easier for members to help you and will keep the discussion in one place. This thread is being closed because it is a duplicate.