Windows Forum

Ask something
Discussion Locked

IP address conflicts

0 helpful
12 replies

by Member 36347166

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We are getting 5 to 10 IP address conflicts on our network every day. When I check the DHCP pool I have about 7 entries that say BAD ADDRESS with some wacky MIC addresses that I can't trace. After I delete these, the conflicts stop for awhile, but they invariable come back the next day. I'm running a pool of 120 addresses, on NT 4 sp6a. Please help!!!

12 replies

by turambar386

Do you have any Sybase hubs? They have weird MAC addresses and use DHCP by default.

Could be some other hub or router or printer that is set to use bootp/dhcp.

by Member 36347166

Thank you, but no, we don't have any Sybase hubs. I can't imagine what other device might be servicing DHCP requests but I will take a closer look. Thank you again.

by drew1124

Check and be sure that there is not another dhcp pool running on another part of your domain. This happened to me with multple domains. I inherited the problem, my local domain had dhcp set up and the corporate server had it setup as well. This may not be what you needed but it happened to me that way.

by gjconely

I have ran into this problem many times when using 10base hubs. By switching those hubs to a cheep LinkSys 10\100 switch, I was able to resolve the problem. Why it did it in the first place, I was never able to find out.

by kenalmoore

The first thing I would check and see if ALL CLIENTS ARE using DHCP!! If some clients or hardware device has a static IP address, that is the problem.

by shawnyong

Suggest you check you network health status, software like etherboy work great for me. If your collsion rate is low, you might want to change the node which the DHCP server is connected to.
Hope this helps.

by Member 36347166

Thank you to all, but it turns out that a flaky Cisco Catalyst switch was the culprit. We had to pwoer it off and reseat the blades. Everything has been fine since.

This discussion is closed to new replies.