Discussion Locked

Conflicting NIC Addresses

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I was called by an associates client,he was on vacation,about an issue concerning conflicting NIC addresses. Evidently after taking an image two addresses were changed and now conflict. I tried to uninstall the card off the network and reinstall it,but still came up with the same conflicting address. These had been on the network before and were working for sometime. How can i get these addresses back to there original settings? I didn't know alot about the Network because it was not originally my client. I have never seen this happen before.
It didn't seem like a hardware issue because the cards worked and did not conflict before they took the image. Can anyone tell me what occured and how to remedy the situation? Any help would be appreciated! Thanks in Advance!! Ron

9 replies

by poettone

I have had this happen in the past lasting only a couple times though. I had to go and reserve the conflicting IP in DHCP to remedy this one problem. Im not sure by your conflicting if you mean IP or Mac so I will leave it at that. But it could be amac address problem as well. You say you uninstalled the adapter, have you released/renewed the lease ffrom the server? I wish you luck as this can be very frustrating.

Good Luck!

by barry hensley

Not sure exactly what desktop OS or method of assigning ip addresses you use but, here are some things to check.

If you used an image to configure a hard drive, then the IP address on the new machine will be the same as the IP address on the machine from where the image was taken. You can correct this two ways.

1. If the IP address is hardcoded at the workstation, open the properties dialog box for the TCP/IP protocol and change the IP address to one that is available.

2. If the IP address is assigned through DHCP, you will have to delete the workstation's reservation from the DHCP database and force it to get a new one. Workstations will request the same IP address that was previously used and, if it is available, the DHCP manager will assign it. But, the workstation will only request a renewal of its lease is about to expire. If the lease is NOT about to expire, the workstation will continue to use the previously assigned IP address even if you remove it from the DHCP manager.

So, remove the IP addresses for BOTH machines that are conflicting (from the DHCP manager) and then force the workstations to get new addresses by releasing their IP addresses and requesting new ones.

You don't have a MAC address problem.Every NIC on planet earth has a unique MAC address. The only possible way to have a MAC address conflict is to manually override the factory assigned MAC address and put in one of your own.... which is NOT a smart thing to do.

Good luck.

by wcraigmiles

In response to answer two, it is possible to have to NIC with the same MAC. It usually doesn't happen with big name brand manufacturers, but... I have had off-brands cause me no end of problems, usually in an IPX environment not IP.

I do believethat the way to solve this was given in number 2. It is most likely that the IP addresses are what is conflicting.

by estebandelatorre

If between nwSERVERS:
Check the servers IPX internal network address in autoexec.ncf. They sould be different (you can put here a random hex number)

If between workstations:
If the conflit occurs at ip or ipx level,
go to card details and change ipx or ip address of one of the two cards.
Also check the windows 95/98/NT machine name. It's common that afer restoring an image (such as from Norton ghost) the machine name was not changed!

OR... you may have to nic cards with the same mac address! Not very usual...
You will have to find one of them, and replace with a NEW one. The old nic card should be used in another network.

by rlyon

Thanks I actually did replace the NIC, rebooted and fixed the problem. I actually forgot to mention in my opening question this was Novell. Thanks again!! Ron

This discussion is closed to new replies.