IP Conflict Error in Enterprise Network

Home Forums Microsoft Networking and Management Services DHCP IP Conflict Error in Enterprise Network

This topic contains 6 replies, has 6 voices, and was last updated by Avatar christy18 5 years, 2 months ago.

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • Avatar
    gajanan
    Member
    #163521

    Hi,

    We are facing ip conflict errors on some client computers after migration of win 7 .
    we used Ghost to install OS on all systems.

    Please help me to resolved this issue.

    Avatar
    Ossian
    Moderator
    #189494

    Re: IP Conflict Error in Enterprise Network

    Do they have static or dynamic IPs?
    If static, no wonder you have conflicts!
    If dynamic, try a release & renew to pick up a unique IP

    Did you sysprep before imaging?

    Avatar
    Anonymous
    #368323

    Re: IP Conflict Error in Enterprise Network

    ip’s are dynamic no static ips

    Avatar
    uk_network
    Member
    #307910

    Re: IP Conflict Error in Enterprise Network

    Hi, I’ve seen this many times where an IP was statically assigned and not excluded from the DHCP range. The computer is turned off and the address is offered out by DHCP. The computer is powered up by someone and this duplicate message appears.
    When you get the error you should be able to remote onto the IP and it will most likely take you to the other machine which has the IP.
    You coudl ping the ip and then perform arp -a from cmd on a windows machine, when you have the mac you can see what port it’s connected to on the switch.
    show mac-address-table on a cisco.
    Hope this helps.

    Avatar
    biggles77
    Spectator
    #213115

    Re: IP Conflict Error in Enterprise Network

    A Knowledgeable Person wrote:
    Did you sysprep before imaging?

    Would be nice to know that answer.

    Avatar
    Ossian
    Moderator
    #189664

    Re: IP Conflict Error in Enterprise Network

    biggles77;284024 wrote:
    Would be nice to know that answer.

    Don’t hold your breath…
    It took 6 weeks to get a partial answer :twisted:

    Avatar
    christy18
    Member
    #390284

    Re: IP Conflict Error in Enterprise Network

    Ossian;284025 wrote:
    Don’t hold your breath…
    It took 6 weeks to get a partial answer :twisted:

    the delay is due to the ip conflict ;-)

    DHCP conflict detection set to 2 generally solves it as a bandaid.

Viewing 7 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic.