不能设IP-您为这个网络适配器输入的IP地址（The IP address you entered for this network adapter cannot be set IP-）

不能设IP-您为这个网络适配器输入的IP地址（The IP address you entered for this network adapter cannot be set IP-） 不能设IP-您为这个网络适配器输入的IP地址(The IP address you entered for this network adapter cannot be set IP-) Question (20091113): The IP address you entered for this network adapter has been assigned to another adapter. 2009-04-02 16:47 You enter the IP address XXX for this network adapter. xxx. XXX xx has been assigned to another adapter ' xxx nic ', ' xxx Nic ' is hidden from the network and Dial-up Connections folder because it does not exist on the computer or an old adapter that does not work. If the same address is assigned to two of adapters, and they are all active, only one will use this address. This can cause incorrect system configuration. Would you like to enter a different IP address for this adapter from the IP Address List of the Advanced dialog box? Workaround: 1. Start ? executive ?cmd 2. Input: Set devmgr_show_nonpresent_devices=12 Input: Set Devmgr_show_nonpresent_devices=1 3. Input: Start DEVMGMT MSC 4. Click "View"?"Display hidden devices 5. Open "Network adapters". Remove the source of trouble! Method 2: Cause of failure: Windows $number believes that the NIC in different PCI slots is a different network card, regardless of whether they are actually the same, and even though the NIC Has been torn down, but its associated configuration file has been logged to the registry by the Windows system. So, in the "fault phenomenon" is the equivalent of the system think You now have two network cards installed in the computer, and the original one has been bound 192.168.0.1 This IP address, and then to another NIC binding this IP will naturally have error prompts! WORKAROUND: Open the registry, find the key value: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class], as prompted by the original network card Information can be removed from class to find the appropriate hardware configuration information item. Note: Each item has the corresponding hardware description information, before deleting please confirm do not delete the wrong. Note: If you do not know the network card Registry information, open the network card driver folder, in the Open Drive folder XP installation directory, there are Notepad, information in the inside, such as 8139/810X network card information is {4D36E972-E325-11CE-BFC1-08002BE10318}, and then found in the subdirectory of the 8139 network card information, delete can be. Method 3: Cause of failure: Windows $number will assume that the NIC in different PCI slots is a different network card, regardless of whether they are actually the same, and that even though the NIC has been removed, its associated profile has been logged to the registry by the Windows system. Therefore, in the "fault phenomenon" encountered, is the equivalent of the system that you now have two cards installed in the computer, and the original one has been bound 192.168.50.188 This IP address, and then give another card to bind this IP will naturally have error prompts! WORKAROUND: Open the registry, find the key value: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class], according to the original NIC information from class to find the corresponding hardware configuration information item Delete. Note: Each item has the corresponding hardware description information, before deleting please confirm do not delete the wrong. If you do not know the network card registry information, you can open the Properties dialog box of the network card, according to the network card descriptive text (if the NIC has been deleted, according to the name of the network card in the dialog box when you modify IP), you can search under the class item to locate the network adapter profile. If you use the network card manufacturers, models are the same, the only difference is the "Netcfginstanceid" value under their respective items. This can be done by modifying the current network adapter's rate or but in duplex mode and then refreshing under the registry key, and the corresponding registry key changes to the current network adapter. For example, the network card is Realtek 8139D network card, By searching Realtek, there are two entries. Modify the current working mode of using the NIC is 100M Full-duplex, two similar network card registry entries were observed, and the value of Duplexmode under a entries changed from 1 to 5, initially confirming that the current network adapter was used, and again confirming that the NIC working mode was restored to auto auto negotiation with a key value of 1. This is the current network card, the same another is the old network card information, the pilot backup, and then delete. Modify the IP settings again, without the previous warning window. Method 4:1. Click Start, point to All Programs, point to Accessories, and then click the command Prompt. 2. At the command prompt, type the following command, and then press ENTER: Set Devmgr_show_nonpresent_devices=1 3. At the command prompt, type the following command, and then press ENTER (where%systemroot% is the folder where Windows XP is installed): Cd\%systemroot%\system32 4. At the command prompt, type the following command, and then press Enter: Start DEVMGMT MSC 5. Troubleshoot devices and drivers in the Device Manager. Focus: In Device Manager, click Show hidden Devices on the View menu to see devices that are not connected to your computer. 6. After the problem is resolved, close the Device Manager. 7. Type exit at the command prompt. Note that when you close a command prompt window, Windows clears the Devmgr_show_nonpresent_devices=1 variable that you set in step 2nd and prevents the Phantom device from being displayed when you click Show hidden devices. Netizen reply: In Device Manager Hook select "Show hidden Device", see "Network adapter" in a gray-scale display of the old network card device, uninstall it after the reboot system, now local connection and so on back to normal ================================================================================================================= About Windows $number, XP, 2003 cannot set IP, remove hidden old NIC information solution 1: Registry Editor Open the Hardware Device Manager and click on the menu "view ? show hidden devices", when the list of devices shows the old hardware list. Open the "network adapter", right-click on the old network card to "uninstall", and then click "Operation ? scan hardware Changes", the NIC also restores no # the original; In addition, delete the old network card model and TCP/IP settings in the registry can also achieve the effect, location in [Hkey_local_machine\\system \\controlset001\\control\\network\\{4d36e972-e325-11ce-bfc1-08002be10318}] directory tree. 2: The system solves directly The Win2000 system can also run the control Panel ? Add/Remove Hardware Wizard to uninstall the following methods: "Control Panel ? add/Remove hardware ? uninstall/unplug device ? uninstall device", in the "Computer Installed Devices" List window, first recognize the name of the network card, so as not to delete the wrong ? check the "Show hidden Devices" item, the new network card is the old driver, select it "Next". There is no Add/Remove Hardware Wizard in winxp/2003 to copy the Hdwwiz. cpl file from the System32 directory in Win2000 to WinXP, double-click it to run the Add/Remove Hardware wizard to uninstall. 3: DOS command On the DOS command line, enter the string command "set Devmgr_show_nonpresent_devices=1", click the Enter key, and then proceed to "Start devmgmt." MSC "Command, open the system's Device Manager window; Then click the View/Show hidden Devices command in the menu bar of the window, as shown in Figure 1. Then from the device list to expand the "network card" project, then you will see a gray color network card icon, the network card is actually called "hidden" network card. 4: Find the Registry For example, your network card address is 192.168.0.1 Then start Registry Editor and look for this IP address. Find a delete one. Reboot after completion. Then you can set this address for this # NIC. ============================================================================================================ Workaround: 1. Start ? executive ?cmd 2. Input: Set devmgr_show_nonpresent_devices=12 Input: Set Devmgr_show_nonpresent_devices=1 3. Input: Start DEVMGMT MSC 4. Click "View"?"display hidden device" 5. Expand network Adapters. Remove the source of trouble! Method 2: Cause of failure: Windows $number believes that the NIC in different PCI slots is a different network card, regardless of whether they are actually the same, and even though the NIC Has been torn down, but its associated configuration file has been logged to the registry by the Windows system. So, in the "fault phenomenon" is the equivalent of the system think You now have two network cards installed in the computer, and the original one has been bound 192.168.0.1 This IP address, and then to another NIC binding this IP will naturally have error prompts! WORKAROUND: Open the registry, find the key value: [Hkey_local_machinesystemcurrentcontrolsetcontrolclass], as prompted by the original network card Information can be removed from class to find the appropriate hardware configuration information item. Note: Each item has the corresponding hardware description information, before deleting please confirm do not delete the wrong. Note: If you do not know the network card Registry information, open the network card driver folder, in the Open Drive folder XP installation directory, there are Notepad, information in the inside, such as 8139/810X network card information is {4D36E972-E325-11CE-BFC1-08002BE10318}, and then found in the subdirectory of the 8139 network card information, delete can be. Method 3: Failure Reason: Windows $number will assume that the network adapters in different PCI slots are different network adapters, regardless of whether they are actually the same; And even though the NIC is torn down, its associated configuration file has been logged to the registry by the Windows system. Therefore, in the "fault phenomenon" encountered, is the equivalent of the system that you now have two cards installed in the computer, and the original one has been bound 192.168.50.188 This IP address, and then give another card to bind this IP will naturally have error prompts! Workaround: Open the registry to find the key value: [Hkey_local_machinesystemcurrentcontrolsetcontrolclass], Press the information of the original NIC of the prompt to find the corresponding hardware configuration information item Delete. Note: Each item has the corresponding hardware description information, before deleting please confirm do not delete the wrong. If you do not know the network card registry information, you can open the properties of the Network Card dialog box, according to the network card descriptive text (if deleted net Card, according to modify IP, prompted by the network card in the dialog box part of the text, under the class item search, you can navigate to the location of the NIC configuration text Thing。 If you use the network card manufacturers, models are the same, the only difference is the "Netcfginstanceid" value under their respective items. This situation can be refreshed under the registry key by modifying the current network adapter's rate or but duplex mode. The corresponding registry key change is the current Network。 For example, the network card is Realtek 8139D network card, through the search Realtek, there are two registered entries. To modify the current working mode of using the NIC to 100M Full-duplex, and to observe two of similar network card registry entries, The value of Duplexmode under a items is changed from 1 to 5, initially confirming the current use of the network card; Confirm again, restore the NIC working mode to auto negotiation, and change the key value to 1. This is the current network card, the same another is the old network card information, the pilot backup, and then delete. Modify the IP settings again, without the previous warning window. Method 4: 1. Click Start, point to All Programs, point to Attachments, and then click the command Prompt. 2. Type the following command at the command prompt, and then press ENTER: Set Devmgr_show_nonpresent_devices=1 3. Type the following command at the command prompt, and then press ENTER (where%systemroot% is the folder where Windows XP is installed): Cd%systemroot%system32 4. Type the following command at the command prompt, and then press ENTER: Start DEVMGMT. msc 5. Troubleshoot device and driver issues in device management. Focus: In Device Manager, click Show hidden Devices on the View menu to see devices that are not connected to your computer. 6. After the problem is resolved, close the Device Manager. 7. Type exit at the command prompt. Note that when you close a command prompt window, Windows clears the Devmgr_show_nonpresent_devices=1 variable that you set in step 2nd and prevents the Phantom device from being displayed when you click Show hidden devices. Netizen reply: In Device Manager Hook select "Show hidden Device", see "Network adapter" in a gray display of the old network card device, uninstall it after the reboot system, now local connection and so on are back to normal.