No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.

Knowledge Base

Statically Configured IP Address Was Displayed as Dynamic Obtaining

Publication Date:  2014-07-15  |   Views:  249  |   Downloads:  0  |   Author:  d00515714  |   Document ID:  EKB1000046690


Issue Description

After the IP address was statically configured on a Win2012 R2 VM, the IP address took effect and could be pinged successfully. The NIC attribute, however, showed that the IP address must be dynamically obtained.
Figure 1 shows the network connection details.
Figure 1 Network connection details

The protocol stack attribute tab is displayed abnormally, and the configuration cannot be obtained properly, as shown in Figure 2.
Figure 2 Dynamic obtaining

Alarm Information


Handling Process

This problem does not recur, and therefore cannot be further diagnosed. Currently, it can only be mitigated by deleting the registry key value. The procedure is as follows:
1. Choose Start > Run, and enter regedit to open the registry.
2. Delete the registry key value HKEY_LOCAL_MACHINE\System\CurrentcontrolSet\Control\Network\config.
3. Restart the VM.

Root Cause

1. The NIC settings on the device manager are normal, the IP address information can be obtained by running ipconfig, and the registry information is normal. The incorrect information, however, cannot recover even after the VM is restarted. The fault may be caused by the Windows OS.
2. Contact Microsoft technical support to locate the fault. By comparing the information captured by the process monitor with the normal information, it is found that in normal cases, DllHost.exe reads registry key values from HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters, while in this abnormal case, DllHost.exe reads registry key values from HKEY_LOCAL_MACHINE\System\CurrentcontrolSet\Control\Network\config. Compare the config key values in the normal and abnormal cases. The difference is found. This may be caused by unknown programs.
3. Manually delete the registry key value HKEY_LOCAL_MACHINE\System\CurrentcontrolSet\Control\Network\config, and restart the VM. The fault is rectified.
This problem does not recur and therefore cannot be further diagnosed. Currently, it can only be mitigated by deleting the registry key value.