asked on

Windows 2008 r2 server with 0.0.0.0 primary IP

I have a Windows 2008 r2 server that has 0.0.0.0 as its primary IP now. Not sure if this a stack problem like Windows PCs sometimes get or is there a possibility that some program on the server actually needs that in place to function? Everything obvious seems to be working fine on the server, it is the server side of the AV security solution and runs a few Shares as well. And remote control works fine on it as well. Anyone seen this on a server and know what my options are to repair it? thanks.

SOLUTION

DonConsolio

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

SOLUTION

Sommerblink

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

SIDESHOWBLAH

ASKER

It has static IP assignments.

Sommerblink

Can you please provide the output from "ipconfig /all"

Thanks.

SIDESHOWBLAH

ASKER

It does not show up in ipconfig. Just in the GUI Network properties. Below is the ipconfig /all resulst and I attached screen copy of the GUI data.
Windows IP Configuration

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

Ethernet adapter Local Area Connection 2:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection #2
Physical Address. . . . . . . . . : 00-11-43-FD-99-9E
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection
Physical Address. . . . . . . . . : 00-11-43-FD-99-9F
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 172.16.11.191(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IPv4 Address. . . . . . . . . . . : 172.16.11.239(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IPv4 Address. . . . . . . . . . . : 172.16.11.240(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 172.16.11.1
DNS Servers . . . . . . . . . . . : 172.16.11.254
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection* 10:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : isatap.{8CE9701C-6FC0-4980-AFEE-ECB02742FFEC}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 11:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : isatap.{9E4EDB35-BC08-4F04-B5B9-C383331DB670}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
zero-ips2.jpg

ASKER CERTIFIED SOLUTION

SIDESHOWBLAH

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

SIDESHOWBLAH

ASKER

The reason for the 0.0.0.0 IP has yet to be deterrmined, but it is definitely not a corruption.