- Apr 2, 2001
- 5,661
- 5
- 81
We have a standard XP SP2 image we use at work that is installed on multiple platforms. In a recent revision we've noticed that the IP address does not stick when assigned statically. You can assign an IP, click OK and then do an ipconfig confirming what you have just configured. However, if you go back to the IP properties, it appears to be configured to use DHCP. You still have the ability to get on the network with the computer, but not being able to view it in TCP/IP properties is troubling. This is happening across all platforms with different NICs.
Looking in the system log, we see the following message:
Event: 4191
Source: TCP/IP
Description: IP could not open the registry key for adapter TCPIP\Parameters\Adapters\NDISWANIP. Interfaces on this adapter will not be initialized.
We've tried resetting the TCP/IP stack using netsh. We've also loaded hotfixes from MS concerning TCP/IP corruption issues. Reinstalling the NIC also does not change anything.
Looking in the system log, we see the following message:
Event: 4191
Source: TCP/IP
Description: IP could not open the registry key for adapter TCPIP\Parameters\Adapters\NDISWANIP. Interfaces on this adapter will not be initialized.
We've tried resetting the TCP/IP stack using netsh. We've also loaded hotfixes from MS concerning TCP/IP corruption issues. Reinstalling the NIC also does not change anything.