IP CONFLICT

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

Q)Is it possible to have two PC's on a AD sever with the same IP address?

When connecting to network a message pops up from the task bar stating IP conflict?? The only way around it is if I use the command IPconfig/release, then manually insert ip address.

However if the PC is switched off/cold rebooted the same message appears??

 

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

A) Yes it is possible, but you don't want it to happen as it causes all sorts of confusion!

Do you know what the other device with the same IP address is?

 

Cheeks

Sounds like a DHCP issue. You've probably got a static IP somewhere on your network without the requisite reservation/exclusion in DHCP. Seems as if the DHCP server is doling out IP addresses and is trying to allocate the statically assigned address to another client.

 

I have checked with networks and they say the 128 address, (I'm not sure if I should post the full address on an open forum??) is only binded to that one PC??

I have been instructed to re-install windows, I can't see how this will make a difference because the operating system is loaded from a RIS server and the ip address is given automatically by the AD server??

 

So how do you get around this?? Would you reset the server?

Would this result in crashing the rest of the network or is there another way

 

Shut the PC down that is giving you the conflict error. go to another PC and ping the IP address and see if you get a response.

 

I tried that AJ, 3 times and still it said there was a conflict.

 

Thanks I will try that!

 

if you do get a response with the machine shut down whilst pinging it, try typing

Code:

nbtstat -a 192.168.0.1

Obviously substituting the IP in the example for the specific IP you are looking at.

If you're lucky, you will get something like this:

Code:

Local Area Connection:
Node IpAddress: [192.168.0.1] Scope Id: []

           NetBIOS Remote Machine Name Table

       Name               Type         Status
    ---------------------------------------------
    FERGAL-DESKTOPN<00>  UNIQUE      Registered
    WORKGROUP      <00>  GROUP       Registered
    FERGAL-DESKTOPN<20>  UNIQUE      Registered
    WORKGROUP      <1E>  GROUP       Registered
    WORKGROUP      <1D>  UNIQUE      Registered
    ..__MSBROWSE__.<01>  GROUP       Registered

    MAC Address = nn-nn-8D-nn-DC-nn

This will tell you the machine name (fergal-desktopn), and the mac address of the machine holding that IP.

It doesnt always work. Some servers dont respond to it, but it might help you narrow things down.

 

If you're looking for the physical location of a machine holding an IP address, you could also ping it, then run arp -a from a command prompt, take a note of the MAC address, then, provided you have access to your switches, take a look at the MAC table and see which physical switch port the device is connected to. Y

ou might then have to do some tracing back across your patch panels, but this extremely low-tech method of finding a physical device has saved me in the past

 

We don't access to the DHCP servers nor the switches so we either pass it to another team (if they have time they'll do it) or we are told to do a rebuild using a RIS server - and that works.