General discussion

Locked

Conflict w/ IP address and Hardware add

By Jaydev ·
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?

This conversation is currently closed to new comments.

15 total posts (Page 2 of 2)   Prev   01 | 02
Thread display: Collapse - | Expand +

All Comments

Collapse -

Conflict w/ IP address and Hardware add

by rickh9 In reply to Conflict w/ IP address an ...

Forgot ... Under W9x its winipcfg /release (/renew)

Collapse -

Conflict w/ IP address and Hardware add

by Shanghai Sam In reply to Conflict w/ IP address an ...

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?

Collapse -

Conflict w/ IP address and Hardware add

by gutridgesj In reply to Conflict w/ IP address an ...

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.

Collapse -

Conflict w/ IP address and Hardware add

by Jaydev In reply to Conflict w/ IP address an ...

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.

Collapse -

Conflict w/ IP address and Hardware add

by Jaydev In reply to Conflict w/ IP address an ...

This question was closed by the author

Back to Windows Forum
15 total posts (Page 2 of 2)   Prev   01 | 02

Related Discussions

Related Forums