On Fri, Dec 21, 2007 at 05:16:40PM +1000, Julian De Marchi wrote: > <snip> > >> The network administrator should have tools to detect the problem but you >> can try this method (i never use it when i have an ip conflict) >> >> First : launch "ifconfig" and see your ip address/netmask. I assume that >> is 192.168.1.2 with a netmask 255.255.255.0 >> >> Second : launch "nmap 192.168.1.0-255" (adapt according your ip and >> netmask). I take some minutes (less than 5 in most of cases). This method >> works if the machine on the network don't block each reply from nmap, but >> i think it's so if your network adminstrator did his job ;) >> Now you will see each ip used on your network. >> >> Third : Switch to a static address that has not been listed by nmap and >> see if you have problem. If you have one, try another till you find >> temporary a ip address which is not used >> >> Fourth : in root, do "arp 192.168.1.2"(your first ip address which gives >> the conflict). Normally, it will show you its mac address. With this one, >> you can see your network administrator. >> >> I repeat that i never used this method with an ip conflict. I may not work >> but if it works, i'm glad to know it. > > Great suggestion Chris! I never though of using nmap for this type of > troubleshooting. some company would consider this hacking if not done by the it department and the user could get ping'ed!
> > Well done Chris! > > -- > Cheers, > Julian De Marchi > -- > OpenNIC user - http://www.opennicproject.org/ > -- > Please avoid sending me Word or PowerPoint attachments. > See http://www.gnu.org/philosophy/no-word-attachments.html > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a > subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > >
signature.asc
Description: Digital signature
