+ Post New Thread
Results 1 to 9 of 9
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 ...
  1. #1
    dsk
    dsk is offline

    Join Date
    Mar 2008
    Location
    London
    Posts
    93
    Thank Post
    7
    Thanked 1 Time in 1 Post
    Rep Power
    0

    Apparently 10.64.92.10 is in use on the network (but it really isnt!)

    Hello!

    So we have this issue where a secondary domain controller W2K3 reported an IP conflict on the network. Seems like something else has its IP address, but we have checked and double checked everything and cant seem to find what (if) anything that has it.

    We've recently just moved over to a virtualised environment and it was initially working fine.

    For some reason we can ping the IP, but tracert shows up nothing. Tried RDP to the IP and also web access, nothing again. DNS and DHCP also show negative for it.

    Bit stuck on what to do.

    I have come across this MS KB: Error message when you try to set an IP address on a network adapter but we've done that to no avail

    help

  2. #2
    pritchardavid's Avatar
    Join Date
    Sep 2009
    Location
    South Ockendon, Thurrock, United Kingdom
    Posts
    932
    Thank Post
    18
    Thanked 64 Times in 58 Posts
    Rep Power
    26
    Try wiping the whole list of leased addresses, that way whatever this is, it should find a new ip address

  3. #3

    maniac's Avatar
    Join Date
    Feb 2007
    Location
    Kent
    Posts
    3,069
    Thank Post
    210
    Thanked 430 Times in 310 Posts
    Rep Power
    144
    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.

  4. Thanks to maniac from:

    dsk (24th August 2010)

  5. #4

    GrumbleDook's Avatar
    Join Date
    Jul 2005
    Location
    Gosport, Hampshire
    Posts
    9,951
    Thank Post
    1,345
    Thanked 1,800 Times in 1,118 Posts
    Blog Entries
    19
    Rep Power
    597
    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.

  6. #5


    Join Date
    Dec 2005
    Location
    In the server room, with the lead pipe.
    Posts
    4,650
    Thank Post
    275
    Thanked 780 Times in 607 Posts
    Rep Power
    224
    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.

  7. #6
    jamesfed's Avatar
    Join Date
    Sep 2009
    Location
    Reading
    Posts
    2,208
    Thank Post
    137
    Thanked 345 Times in 291 Posts
    Rep Power
    87
    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).

  8. #7

    FN-GM's Avatar
    Join Date
    Jun 2007
    Location
    UK
    Posts
    16,054
    Thank Post
    888
    Thanked 1,729 Times in 1,492 Posts
    Blog Entries
    12
    Rep Power
    454
    Can you see what it is in your DNS?

  9. #8

    Join Date
    Jan 2006
    Location
    Surburbia
    Posts
    2,178
    Thank Post
    74
    Thanked 307 Times in 243 Posts
    Rep Power
    115
    Can you do an ARP lookup to get the hardware address, then look up the routing tables on your switch(s)
    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.

  10. Thanks to PiqueABoo from:

    dsk (24th August 2010)

  11. #9
    dsk
    dsk is offline

    Join Date
    Mar 2008
    Location
    London
    Posts
    93
    Thank Post
    7
    Thanked 1 Time in 1 Post
    Rep Power
    0
    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!

SHARE:
+ Post New Thread

Similar Threads

  1. [Video] Best FAILS of 2009 (apparently)
    By theeldergeek in forum Jokes/Interweb Things
    Replies: 1
    Last Post: 9th January 2010, 04:15 PM
  2. Apparently my PCs on fire!
    By joe90bass in forum Hardware
    Replies: 9
    Last Post: 13th June 2008, 10:05 PM
  3. My laptop isnt working properly.
    By simonti in forum Windows
    Replies: 2
    Last Post: 30th November 2007, 08:29 AM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •