Solved

Windows System Error – There is an IP address conflict with another system on the network.

Posted on 2006-07-13
9
27,948 Views
Last Modified: 2011-08-18
Windows System Error – There is an IP address conflict with another system on the network.

I recently diagnosed a fault in my server NIC which was a 3Com PCI card. I replaced it with an Intel Pro/1000 T. The problem is that the original card had a static IP address of 192.168.1.3. This address is required for the new Intel card and an error message is displayed that there is a conflicting IP address in the system.

The conflict is not that another node has the same address but it is as a result of the 3com card not being uninstalled correctly. The operating System is Windows 2003 SBS Enterprise Edition

My question is, how do I remove the original configuration settings which will remove the error message. The network is working fine other that the error message. The system settings shows the 3Com card hidden but will not allow it to be removed. When I attempt to uninstall the device, an error message “Failed to uninstall the device. The device may be required to boot the computer” is displayed.

Any help would be much appreciated.
0
Comment
Question by:bushsubaru
9 Comments
 
LVL 57

Expert Comment

by:Pete Long
ID: 17097755
working from memory bear with me

start > run > devmgmt.msc

View > show

then its either hidden devices or all devices, you can then see the old network card and right click >uninstall it
0
 
LVL 57

Expert Comment

by:Pete Long
ID: 17097759
view > show hidden devices
0
 
LVL 57

Expert Comment

by:Pete Long
ID: 17097780
bushsubaru,
or
Right CLick My computer > Properties > Advanced > Environment Variables
System Variables Section > New

Create a new Variable Called

DEVMGR_SHOW_NONPRESENT_DEVICES
Set it's value to: 1
Reboot your machine
Goto your device manager
Show all hidden devices
Now you can see all devices you ever installed
Remove the NIC as usuall
0
 
LVL 57

Assisted Solution

by:Pete Long
Pete Long earned 200 total points
ID: 17097803
bushsubaru,
or
-------------Method 2-------------------
To get rid of that unwanted driver, device, or service:
1) Open the "Start" menu and choose "Run..."
2) Type in "cmd" (without the quotes) and click "ok".
3) At the cmd prompt, type in "set devmgr_show_nonpresent_devices=1"
(without the quotes) and press enter. (Note that nothing seems to
happen--this is ok. We are actually setting an environment variable
 which is going to help us to see hidden devices)
4) On the next cmd prompt line, type in "devmgmt.msc" (without the quotes)
 and press enter. This will launch the Windows Device Manager Console.
5) In the Device Manager Console, from the "View" menu, select
"Show Hidden Devices".

Now, as you expand the different drivers and devices in device manager
you will see not only the items that Windows currently detects as
 installed on your pc (these are the usual items displayed), but you
will also see drivers, devices, and services which have been loaded in
the past but were not uninstalled or are not currently started. You can
find your offending device, right-click, and choose "uninstall" to remove
it from the system completely.

Be careful though; you should note that non-loaded devices, drivers,
and services are "grayed" out, but that doesn't necessarily mean that
you should delete all of them. Only remove items you know you don't need.
And, be careful that you don't change too many devices or you might need
to re-activate your Windows installation.

Last thing, if you accidentally exit the Device Manager Console you will
need to start over again at the cmd prompt. To close the cmd prompt window,
type "exit" (without the quotes).
0
Maximize Your Threat Intelligence Reporting

Reporting is one of the most important and least talked about aspects of a world-class threat intelligence program. Here’s how to do it right.

 
LVL 26

Accepted Solution

by:
Leon Fester earned 200 total points
ID: 17097845
The error that you are getting is quite common in that scenario. i.e. when replacing a network card.

Your system will continue to work correctly with the old NIC card/settings as is.

The only way to uninstall the card is to put the old card back in and then remove it.

This behaviour is by design, and dates back to WinNT 3.1, when you HAD!!! to absolutely remove the OLD NIC first, reboot and then install the new NIC.
0
 

Assisted Solution

by:munu2000
munu2000 earned 100 total points
ID: 17101689
Yes. Whan dnt_localboy said is correct. put back old card. Once os detects, uninstall the nic from devicemanager. Shutdown windows. remove old card. restart os. See any error message & check the device manager. If cleared, shutdown. Insert new Intel card. On back.
0
 

Author Comment

by:bushsubaru
ID: 17103909
Thanks everyone for the advice. I suspected that the only solution was to put the old card back in the system and uninstall in correctly. I will let you know once I give it a try. It is odd that Microsoft haven't devised a routine which will remove spurious drivers and settings of this sort. Then again, logic isn't one of Microsofts' stong attributes.
0
 

Author Comment

by:bushsubaru
ID: 17347387
Hi Evereyone, Your comments were valuable and allowed me to test all conditions which might have lead to the problem.

However, I finally resolved the problem by firstly NOT considering that the server or any connected node was the problem but simply that I had forgotten about the managed switch which had been assigned the same IP address as the server NIC.

My fault, as I should have considered this before asking the experts.
0

Featured Post

Why You Should Analyze Threat Actor TTPs

After years of analyzing threat actor behavior, it’s become clear that at any given time there are specific tactics, techniques, and procedures (TTPs) that are particularly prevalent. By analyzing and understanding these TTPs, you can dramatically enhance your security program.

Join & Write a Comment

Even if you have implemented a Mobile Device Management solution company wide, it is a good idea to make sure you are taking into account all of the major risks to your electronic protected health information (ePHI).
If you're not part of the solution, you're part of the problem.   Tips on how to secure IoT devices, even the dumbest ones, so they can't be used as part of a DDoS botnet.  Use PRTG Network Monitor as one of the building blocks, to detect unusual…
Viewers will learn how to connect to a wireless network using the network security key. They will also learn how to access the IP address and DNS server for connections that must be done manually. After setting up a router, find the network security…
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…

706 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

20 Experts available now in Live!

Get 1:1 Help Now