Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Hi, in my LAN there have around 20pcs linux and window XP system. There have 3 PC having a same IP Address,so IP Address conflict. How to check is it inside the LAN have any system(PC) having IP Address conflict,what command should be use arp or what? than can find the all IP Address conflict PC's MAC address.
If there are only 20 PC's involved, then I would suggest to assign proper and unique IP's to all of them and file the IP numbers in a proper system admin documentation (very handy sometimes).
If you don't want to deal with IP numbers and there is no reason to have fixed numbers, then you should really switch to DHCP, as already suggested. Even internal web, samba and other servers will work fine with DHCP, because they usually run forever, so their IP is not changed by the Router.
For 20 IP addresses, it would be easy to keep track of them all in a spreadsheet. If you use Open Office Calc, a format for a column like "192.168.1."# and then filling down a range of numbers (the last octat) can be convenient. Then if someone needed another IP address, it would be a simple matter of opening the spreadsheet to find an available IP address. If you have some hosts that use DHCP and some servers on fixed IP addresses, make sure that you assign the fixed addresses outside the range of IP's that the DHCP server serves up. If you run a DHCP server on a computer, you can configure it to give fixed addresses to certain hosts based on their MAC addresses.