Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

On a Windows 2008 server that is running under ESX 3.5 we see an issue for the NIC whereby it has multiple IP's. One is its normal IP 10.2.x.x, the other is the 0.0.0.0 address (subnet 0.0.0.0, gateway as per normal nic).

Heres the ipconfig /all dump

Windows IP Configuration

   Host Name . . . . . . . . . . . . : server
   Primary Dns Suffix  . . . . . . . : domain.local
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
  DNS Suffix Search List. . . . . . : domain.local

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . : domain.local
   Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection
   Physical Address. . . . . . . . . : 00-50-56-B0-3B-AC
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 10.2.81.71(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 10.2.81.254
   DNS Servers . . . . . . . . . . . : 10.2.81.57
                                       10.2.81.49
   Primary WINS Server . . . . . . . : 10.2.81.57
   Secondary WINS Server . . . . . . : 10.2.81.49
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection*:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : domain.local
   Description . . . . . . . . . . . : isatap.domain.local
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

IPV6 is unselected in properties, and IPV4 is selected.

If I manually remove the 0.0.0.0 address it sticks until a reboot, then it reappears again when viewing the NIC properties.

share|improve this question

2 Answers 2

up vote 1 down vote accepted

I'm with Dave, I don't see the 0.0.0.0 that you're talking about.

You may, however, see a route to 0.0.0.0 in the route print command, which is the default gateway for your NIC. Your default gateway is where you go for access to any networks you don't know about.

Is this 0.0.0.0 address causing an actual problem?

share|improve this answer
    
I am unsure if the 0.0.0.0 is causing any problem. We have one oustanding issue relating to a file copy operation that stalls but in general use the server displays no major problems. IPv6 was linked to the adapter but it is currently deselected. I might see if we can remove IPv6 entirely to keep the issue simple. Its not the route we're seeing it is an IP of 0.0.0.0. –  jafin Aug 10 '09 at 7:40
    
thanks. It looks like i truncated the ipconfig output when I originally asked this question –  jafin Dec 18 '10 at 3:31

Where are you seeing 0.0.0.0 because it's not in the ipconfig /all output? Windows uses 0.0.0.0 to mean 'listen on all IPs' so if you're looking at netstat output you're just seeing services that are listening on all IPs. If this isn't the case, please tell us where you are seeing this IP.

share|improve this answer
    
See thats the strange thing, the output doesn't appear in ipconfig. You only get to see this 0.0.0.0 address when opening Control Panel Network Config and the TCPv4 properties for the NIC start with 0.0.0.0, gateway same as per normal. Under Advanced settings for the NIC it lists 2 IP's. The correct IP and the 0.0.0.0 –  jafin Aug 10 '09 at 7:39

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.