exhuser
asked on
TCP Settings on Windows 2008 Server
For some reason, after configuring a static IP on Windows 2008 server, the address is showing as 0.0.0.0 and 0.0.0.0 subnet. Ipconfig, however, shows the correct address as "
Preferred". Moreover, the advanced property of IP shows both 0.0.0.0 and the actual address at the bottom.
Any idea?
Preferred". Moreover, the advanced property of IP shows both 0.0.0.0 and the actual address at the bottom.
Any idea?
ASKER
This is different:
Looks like it adds another address 0.0.0.0 and subnet 0.0.0.0 However, the correct static address is listed at the bottom (in advanced settings) and is showing in ipconfig.
Looks like it adds another address 0.0.0.0 and subnet 0.0.0.0 However, the correct static address is listed at the bottom (in advanced settings) and is showing in ipconfig.
Do you have a Health policy Server restricting this server? Maybe it doesn't meet requirements like virus signature.
Something like this?
http://www.trainsignal.com/blog/nap-network-access-control-server-2008
http://www.trainsignal.com/blog/nap-network-access-control-server-2008
Dynamic Host Configuration Protocol (DHCP) is one of the easiest NAP enforcements to deploy because all DHCP client computers must lease an IP address. Therefore if the client computer does not meet the health policy requirements the DHCP server will either assign an invalid IP address, such as 0.0.0.0., to the client or route the client to the remediation server for updates. This way the client can only access the IP address of the network if all health requirements are met.
ASKER
I don't think ther is a helth policy restricting this. After all DHCP works -- it is just the static IP settings
Have you tried rebooting?
I would say release/renew ip but it should be a static ip. I would issue the command just to see what it tells you.
Only 1 NIC involved?
ipconfig /release
ipconfig /renew
I would say release/renew ip but it should be a static ip. I would issue the command just to see what it tells you.
Only 1 NIC involved?
ipconfig /release
ipconfig /renew
ASKER
Yes only one NIC
Is this a physical machine or a virtual?
This might help. You can run it manually with netsh or use their Fix it link. Either way you need a reboot which might fix the problem all by itself.
How to reset Internet Protocol (TCP/IP)
http://support.microsoft.com/kb/299357
ASKER
Physical machine, 2 adaptors, one disabled.
ASKER
Looks like it has something to do with IP v 6: when I try to ping the localhost, IP v 6 responds...
Maybe something here but most require a reboot. Again it refers to DHCP which you are not using but it seems like your machine is in limbo between DHCP and static ip.
http://support.microsoft.com/kb/822123
http://support.microsoft.com/kb/822123
Method 1: Turn Off Firewalls
Method 2: Verify That Your Network Card Is Installed Correctly
Method 3: Verify That the Dynamic Host Configuration Protocol (DHCP) Client Service Is Started
Method 4: Modify the Registry
ASKER
My Iconfig reports the correct address, it is when I go to TCP/IP settings I see 0.0.0.0 as the first address.
Try disabling IPv6
ASKER
Disabling IPv6 did not help...
OK so it's not an IPv6 problem. It's just that IPv4 is not working so IPv6 responds. Can you reboot?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Glad you got it. It was a very strange symptom
ASKER
Found solution by re-installing the driver
http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/cafe29bb-d5f2-449c-9bd2-18014d278b3d/