Wireless Networks Thread, Apparently 10.64.92.10 is in use on the network (but it really isnt!) in Technical; Hello!
So we have this issue where a secondary domain controller W2K3 reported an IP conflict on the network. Seems ...
23rd August 2010, 04:06 PM #1
IDG Tech News
23rd August 2010, 04:12 PM #2
Try wiping the whole list of leased addresses, that way whatever this is, it should find a new ip address
23rd August 2010, 06:00 PM #3
Can you do an ARP lookup to get the hardware address, then look up the routing tables on your switch(s) to pin point the offending bit of hardware (assuming you have managed switches of course) that might help you find it. It's likely it will just return the ligitimate servers address, but there's always a chance.
P-dave's suggestion is also a good one, I do this as a matter of course every now and then, particularly when we get a lot of new hardware and chuck a lot of old stuff - it stops old bits of hardware hanging onto reservations and causes no harm.
23rd August 2010, 08:20 PM #4
I tend to favour making everything a reserved IP and keep a very limited scope where possible. This also allows for a better audit trail when tracking down the exact machine which is causing problems.
23rd August 2010, 10:32 PM #5
Is that secondary DC virtual?
Did you give it a static IP before you installed vmware tools / xen tools / whatever PV addons?
Did you then assign that same static IP to the "new" virtual nic created after the tools install?
Normally it bitches if you do this, but handles it fine. You may have found the exception. Try removing the other NIC from device manager.
23rd August 2010, 10:39 PM #6
Did you remove the network adapter settings before you virtulised?
You may find that the old hardware still has ahold of your IP adresses (even though its not in use).
23rd August 2010, 10:45 PM #7
Can you see what it is in your DNS?
24th August 2010, 12:04 AM #8
That would work if it pings, otherwise you normally get a Windows event log entry which has the MAC in it (in the log on the system that is complaining about the conflict). I usually look up the vendor the MAC belongs to in the IEEE OUI because that can sometimes help tell you what device wotdunnit.
Can you do an ARP lookup to get the hardware address, then look up the routing tables on your switch(s)
Thanks to PiqueABoo from:
24th August 2010, 09:46 AM #9
- Rep Power
Cheers guys. After some ARP lookup and looking for the culprit on the core switch, we got it. Still not too sure what the device is, but unplugged the port it was using and managed to get our controller back onto that IP.
I have a feeling it might some new WiFi access points that were installed over the holiday, but cant check.
Cheers again! You guys are awesome!
By theeldergeek in forum Jokes/Interweb Things
Last Post: 9th January 2010, 04:15 PM
By joe90bass in forum Hardware
Last Post: 13th June 2008, 10:05 PM
By simonti in forum Windows
Last Post: 30th November 2007, 08:29 AM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)