The Internet Protocol Version 4 (TCP/IPv4) Properties dialog box might display 0.0.0.0 after you upgrade to Windows Vista SP1 and after you manually configure a static IP address

Consider the following scenario:

• You upgrade Windows XP or the release version of Windows Vista to Windows Vista Service Pack 1 (SP1).
• You manually configure the TCP/IP properties to add a static IP address.

In this scenario, the Internet Protocol Version 4 (TCP/IPv4) Properties dialog box might display 0.0.0.0 for the IP address and for the subnet mask.

This problem occurs because of an issue that involves the network adapter driver. This issue causes the incorrect information to be displayed by the network adapter.

Note Despite this display problem, the correct information is used to handle and to route traffic through this network connection.

To work around this problem and to view the correct information for the network adapter, follow these steps:

1. Click Start
   Collapse this imageExpand this image

   
   , type cmd in the Start Search box, and then click cmd in the Programs list.
   
   
   Collapse this imageExpand this image

   
   If you are prompted for an administrator password or for confirmation, type your password, or click Continue.
2. At the command prompt, type ipconfig /all, and then press ENTER. The correct IP address information is displayed for the network adapter.

To resolve this problem, uninstall and then reinstall the network adapter. To do this, follow these steps:

1. Click Start
   Collapse this imageExpand this image

   
   , type Device Manager in the Start Search box, and then click Device Manager in the Programs list.
   
   
   Collapse this imageExpand this image

   
   If you are prompted for an administrator password or for confirmation, type your password, or click Continue.
2. Expand Network Adapters.
3. Right-click the network adapter, and then click Uninstall.
   
   Note If you are prompted to delete files, click No.
4. Restart the computer. The network adapter is automatically detected and reinstalled.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.