Discussion Locked

Conflict w/ IP address and Hardware add

0 helpful
15 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
The error message is "The system has detected a conflict for IP address 176.16.22.22 with the system having hardware address 08:00:4e:10:8b:54. The interface has been disabled." This is right after a reboot on an ethernet network. We're unable tolog on to the network. Also clients are 95 with NT servers. We use DHCP and don't currently assinging static IP to sign them on. Looked at soem doc's from Microsoft and they didn't help! SO can you help please?

15 replies

by saihib

Try to ping that address. If you get a response then DHCP has given it out. Also the MAC address might have been given to two different NIC's in some sort of weird mixup.

by jaydev

Sorry, but MAC addresses are unique. I guess I should have included this before but that 176.16.22.22 belongs to a HUB. Don't want to restart or kill the hub.

by tchieng

Go to the DOS prompt on another PC on the network and type in "NBTSTAT -A 176.16.22.22" to figure out who's machine it is that's taking up the IP address. That command will give you the Netbios name of the PC using the Ip address. Hopefully you knowthat this is. Then go to that particular PC. Make sure it's not setup for static IP using that address. Run WINIPCFG and release and renew the IP address, or simply reboot the PC. Then come back to the trouble PC, reboot and see if it works. If not,you'll need your NT Administrators help to modify the DHCP server active list or scope or whatever you call it...

by jaydev

Good Answer buddy. Unfortunatley, we don't use static ip for any computer. It's a hub that much I know..the 172.16.22.22. We had already tried this and didn't work. But open to more suggestions. Thanks.

by gutridgesj

here is an obvious question, did you actually look at tcp/ip settings on the PC in question to see that there is not a static ip address assigned to it?

by shanghai sam

YES. One of the things we checked. Made sure no static IP was there already. We don't assign any static ip address. Only for test purposes. Thanks for the try. Open to everything.

by leizure. . .

Has the DHCP server been configured NOT to assign 176.16.22.22 to any PC logging on to the network?

by shanghai sam

Yes, DHCP is confiugred properly and we have scoped IP's out that are being used by HUBS and....
Thanks.

by rickh9

It sounds like your hub is not configured for DHCP, or possibly DHCP is not turned on. First verify the hub status and if it is a static entry create a reservation for it in the DHCP administrator. Either by activating DHCP on the hub or creating a reservation or removing the address from the scope, you need to get the DHCP server to stop attempting to re-issue the address. Once that is done you can go to a dos prompt on the workstation and type ipconfig /release and then ipconfig /renew and the machine will pick up a new ip address.

by shanghai sam

Thanks Rick, I am going to check your answer posted prior to this one. I think we have aleady tried that but will make sure one more time. Keep them coming. Here is some new information, one of the machine is fine after removing DUN. Tried it on 2nd machine and didn't work. Anything to do with that?

by gutridgesj

ok, well, here's the deal. Every PC with the problem has an IP address setting of that number somewhere. So, i say delete all the entries in the network settings except the network card and reboot. First, i would mark down what is there so you can put it back.
once the pc comes back up, add tcp/ip using dhcp and reboot. see if the problem still exists. if not, add client for MS and reboot.
the goal is to see what entry was doing it.
DUN has tcp/ip settings so that is a good place tolook.
if the problem comes back and you cannot see where it is, then check the registry for that number and find out if it is lingering around. if so, delete that registry entry.

next, why does that hub need an IP address in the first place? isay trash the ip address on the hub.

you said you did not want to do this, but i would power off the hub for a few seconds and then ping that address to see if it is still out there somewhere. maybe there is more to it than it seems.

i would also check to see if there are other DHCP servers on the network besides what you think there is. maybe a rogue dhcp server is out there and it is assigning that address. also, check the registry on all the dhcp servers for the ip address to see ifit is lingering around somewhere.

all this should keep you busy for a while.

by jaydev

Thanks. Your last statement was correct. It was a test server that had DHCP manager enabled. Giving out IP addresses. Thanks for your help. Test server went down and so did the problem. Test server came up problem came back and now we knewsoon that it was the test server causing the problem.

This discussion is closed to new replies.