Hi, I am experiencing a strange problem running on two Windows 2008 64bit Standard servers. Upon each reboot, the multiple ip addresses assigned to the servers disappear after rebooting host. Only the the latest three ip address that were assigned recently remain, all other ip address dissappear. I checked the Event Viewer logs and do not see any errros regarding this issue. Does anyone have any tips on why this could be happening ? Thanks!

Hello, make sure to use the latest NIC drivers. Is teaming used on the NICs? What server roles are installed that you need multiple ip addresses? Please post an unedited ipconfig /all from the server in question.Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

Hi Meinolf, The latest NIC drivers are installed. The NIC is an HP NC373i Multifunction Gigabit Server Adapter and is currently Teamed. Here is an ipconfig/all from the server: Microsoft Windows [Version 6.0.6002] Copyright (c) 2006 Microsoft Corporation. All rights reserved. ipconfig/all Windows IP Configuration Host Name . . . . . . . . . . . . : hostnamehidden Primary Dns Suffix . . . . . . . : dnshidden Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : dnshidden Ethernet adapter main: Connection-specific DNS Suffix . : dnshidden Description . . . . . . . . . . . : HP Network Team Physical Address. . . . . . . . . : Masked DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::8988:d0ea:60e0:8945%12(Preferred) IPv4 Address. . . . . . . . . . . : 10.128.122.14(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 IPv4 Address. . . . . . . . . . . : 10.128.122.16(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 IPv4 Address. . . . . . . . . . . : 10.128.122.37(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 IPv4 Address. . . . . . . . . . . : 10.128.122.52(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 IPv4 Address. . . . . . . . . . . : 10.128.122.59(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 IPv4 Address. . . . . . . . . . . : 10.128.122.85(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 IPv4 Address. . . . . . . . . . . : 10.128.122.86(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 IPv4 Address. . . . . . . . . . . : 10.128.122.87(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 IPv4 Address. . . . . . . . . . . : 10.128.122.92(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 IPv4 Address. . . . . . . . . . . : 10.128.122.100(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 IPv4 Address. . . . . . . . . . . : 10.128.122.105(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 IPv4 Address. . . . . . . . . . . : 10.128.122.106(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 IPv4 Address. . . . . . . . . . . : 10.128.122.108(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 IPv4 Address. . . . . . . . . . . : 10.128.122.110(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 IPv4 Address. . . . . . . . . . . : 10.128.122.112(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 IPv4 Address. . . . . . . . . . . : 10.128.122.122(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 IPv4 Address. . . . . . . . . . . : 10.128.122.124(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 IPv4 Address. . . . . . . . . . . : 10.128.122.125(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 IPv4 Address. . . . . . . . . . . : 10.128.122.126(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 IPv4 Address. . . . . . . . . . . : 10.128.122.127(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 IPv4 Address. . . . . . . . . . . : 10.128.122.128(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 IPv4 Address. . . . . . . . . . . : 10.128.122.142(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 IPv4 Address. . . . . . . . . . . : 10.128.122.144(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 IPv4 Address. . . . . . . . . . . : 10.128.122.146(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 IPv4 Address. . . . . . . . . . . : 10.128.122.148(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 IPv4 Address. . . . . . . . . . . : 10.128.122.150(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 IPv4 Address. . . . . . . . . . . : 10.128.122.152(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 IPv4 Address. . . . . . . . . . . : 10.128.122.158(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 IPv4 Address. . . . . . . . . . . : 10.128.122.159(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 IPv4 Address. . . . . . . . . . . : 10.128.122.160(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 IPv4 Address. . . . . . . . . . . : 10.128.122.163(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 IPv4 Address. . . . . . . . . . . : 10.128.122.164(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 10.128.122.1 DHCPv6 IAID . . . . . . . . . . . : 452992523 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-11-E8-A5-3F-00-1E-0B-C3-D8-82 DNS Servers . . . . . . . . . . . : 10.128.122.19 NetBIOS over Tcpip. . . . . . . . : Enabled Tunnel adapter Local Area Connection* 8: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : dnshidden Description . . . . . . . . . . . : isatap.dnshidden.noone Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes The server is an IIS web server with multiple websites running using ASP. No host headers are used. Thank

Hi Customer, Can you test just assign 7 IP address to the NIC if still disappeared, is there any abnormal eventlog when the server rebooting?Regards, Rick Tan

Hi Rick, I have tested assigning only a few ip addresses and they still dissappear after rebooting the host. There are no abnormal event logs in Event viewer at all. Windows does not think there is an issue with the ip assignmnets. I have also reset TCPIP and then re-assigned the Ip addresses but they still dissappear after some reboots but not all reboots. Very strange and annoying issue. Any help is apreciated. Thanks!

Hi Customer, According to my test, win2008 NIC could keep 7 ip address after rebooted. So please use no teaming NIC to test on your server, I guess the issue caused by NIC teaming software. Regards, Rick Tan

Thanks for the tip, Rick! I will disable NIC Teaming and test it out. If it does not resolve issue, will ask again.

Hi Rick Tan, I removed NIC Teaming software and rebooted hosts multiple times and after each reboot, the ip addresses still disappear. Is this a known issue with 2008 ? Any help is appreciated. Thanks!

Ahmed, there are limitations on IPs for NIC when those IP addresses arebound by IIS. IIS has a limitation - although I am not 100% sure what it is. I see this from time to time and have to rebuild my bindings. I think you have reached your limit for a web server. So, lets take a step back - why so many IP addresses? Why not host headers?*a

Hi Alex, Thanks for the feedback! We had been using over 35 Ip addresses, per NIC, for a similar webserver running Windows 2003 without any issues (using IIS6 and ASP .NET). Curious why there would be such a limitation in 2008 when it was not in 2003. And the reason for the absence of Host Headers are different domain names and seperate login security, per customer, as these individual Ip's are for individual customers. I also have another 2003 webserver running over 40 Ip addresses via IIS and have not had a single issue like I am seeing in 2008. Here is an article with a somewhat similar issue: http://social.technet.microsoft.com/Forums/en-US/winserverPN/thread/225327ef-89c8-41fb-8316-175f8718e2da/ I am beginning to suspect, something is very different about 2008 as these issues were not present in 2003.

Hi Customer, I test 7 ip address assign to one NIC and bind four websites (default site copy) with difference ip 80 port in IIS. It works after server reboot. I recommend you change your NIC slot on your server to reinstall NIC driver, configure server like my test to see if it work. Regards, Rick Tan

Ahmed, I am running different domain names and separate login security per customer. I use static IPs but also with host header. I should mention, most the sites are also using wildcard SSL. Either way, I think that if you add host headers, IIS will scan for that first and more effeciently - and you should not see an issue with the IP addresses. I agree with your school of thought, that it worked in 2003 - it should work in 2008. But is a change in not just config, technology but also archtiecture. 2008 is just different, soone should expect different results. Alex*a

Hi Rick Tan, I removed NIC Teaming software and rebooted hosts multiple times and after each reboot, the ip addresses still disappear. Is this a known issue with 2008 ? Any help is appreciated. Thanks! Hello All! Ahmed, this really isn't a fix but more of a work around for your situation but it should relieve your stresses as an admin. Create a startup script for your system. If the address already exists, it will be ignored and move to the next line. netshipfix.bat @echo off netsh interface ipv4 add address “Local Area Connection” 10.128.122.14 255.255.255.0 netsh interface ipv4 add address “Local Area Connection” 10.128.122.16 255.255.255.0 netsh interface ipv4 add address “Local Area Connection” 10.128.122.37 255.255.255.0 .... .... .... you get the picture... Now you can find yourself with a range of IP addresses that are sequential or consecutive... so you can use the "For /L" command to get the range started with one line. Since you are putting it in a batch file, you will need double %% to represent your variable. The example listed below shows the format... and a sample from 10.128.122.210 through 10.128.122.230.(21 IPs) For /L %%A (IPstart,Increment,IPend) do (netsh interface ipv4 add address “Local Area Connection” 10.128.122.%%A 255.255.255.0 EXAMPLE: For /L %%A (210,1,230) do (netsh interface ipv4 add address “Local Area Connection” 10.128.122.%%A 255.255.255.0 I hope that helps with your concerns in KEEPING the IP addresses on the server active as they need to be. Add this as a Startup script for the computer account with GPedit.msc. Computer Configuration\ Windows Settings\ Scripts (Startup\Shutdown) Best Regards,Steve Kline Microsoft Certified IT Professional: Server Administrator Microsoft Certified Technology Specialist: Active Directory, Network Infrastructure, Application Platform, Windows 7 Microsoft Certified Product Specialist & Network Product Specialist Red Hat Certified System Administrator This posting is "as is" without warranties and confers no rights.

Hi Rick Tan, I removed NIC Teaming software and rebooted hosts multiple times and after each reboot, the ip addresses still disappear. Is this a known issue with 2008 ? Any help is appreciated. Thanks! Hello All! Ahmed, this really isn't a fix but more of a work around for your situation but it should relieve your stresses as an admin. Create a startup script for your system. If the address already exists, it will be ignored and move to the next line. netshipfix.bat @echo off netsh interface ipv4 add address “Local Area Connection” 10.128.122.14 255.255.255.0 netsh interface ipv4 add address “Local Area Connection” 10.128.122.16 255.255.255.0 netsh interface ipv4 add address “Local Area Connection” 10.128.122.37 255.255.255.0 .... .... .... you get the picture... Now you can find yourself with a range of IP addresses that are sequential or consecutive... so you can use the "For /L" command to get the range started with one line. Since you are putting it in a batch file, you will need double %% to represent your variable. The example listed below shows the format... and a sample from 10.128.122.210 through 10.128.122.230.(21 IPs) For /L %%A (IPstart,Increment,IPend) do (netsh interface ipv4 add address “Local Area Connection” 10.128.122.%%A 255.255.255.0 EXAMPLE: For /L %%A (210,1,230) do (netsh interface ipv4 add address “Local Area Connection” 10.128.122.%%A 255.255.255.0 Add this as a Startup script for the computer account with GPedit.msc. Computer Configuration\ Windows Settings\ Scripts (Startup\Shutdown) I hope that helps with your concerns in KEEPING the IP addresses on the server active as they need to be. Best Regards, Steve Kline Microsoft Certified IT Professional: Server Administrator Microsoft Certified Technology Specialist: Active Directory, Network Infrastructure, Application Platform, Windows 7 Microsoft Certified Product Specialist & Network Product Specialist Red Hat Certified System Administrator This posting is "as is" without warranties and confers no rights.

Hello Again Ahmed, Just wanted to also make a note, your Nic Name may be different and Local Area Connection may not apply. Run this command to see what yours is... as you can see below. Local Area Connection applies to my system. netsh int ipv4 show interfaces Idx Met MTU State Name --- ---------- ---------- ------------ --------------------------- 1 50 4294967295 connected Loopback Pseudo-Interface 1 11 10 1500 connected Local Area Connection 13 5 1500 disconnected Local Area Connection 2Steve Kline Microsoft Certified IT Professional: Server Administrator Microsoft Certified Technology Specialist: Active Directory, Network Infrastructure, Application Platform, Windows 7 Microsoft Certified Product Specialist & Network Product Specialist Red Hat Certified System Administrator This posting is "as is" without warranties and confers no rights.

Hi Steve, Thank you very much for this helpful batch script! I have modified it to match the NIC name of the affected servers and set it up as a Startup Batch script via GPEDIT.MSC. It is a great workaround till we find out what is causing this issue. I would also like to add all Ip addresses manually to the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{NAME_OF_YOUR_SERVERS_ACTIVE_INTERFACE} Will get to test this out on Friday and post my results. Regards, Ahmed Jehanzeb

Just an update to this issue. Last Friday, I added all ip addresses manually in the registry, on both servers. The registry key is located here: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\ Rebooted both servers and was able to retain all 41 and 35 ip addresses, respectively, on both servers. Will reboot both servers again this Friday to confirm whether this worked permanently or not.

Just an update to this issue. Last Friday, I added all ip addresses manually in the registry, on both servers. The registry key is located here: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\ Rebooted both servers and was able to retain all 41 and 35 ip addresses, respectively, on both servers. Will reboot both servers again this Friday to confirm whether this worked permanently or not. Thanks for the update Ahmed, Will look forward to the results! Best Regards,Steve Kline Microsoft Certified IT Professional: Server Administrator Microsoft Certified Technology Specialist: Active Directory, Network Infrastructure, Application Platform, Windows 7 Microsoft Certified Product Specialist & Network Product Specialist Red Hat Certified System Administrator This posting is "as is" without warranties and confers no rights.

Final update to this issue - Last Friday I rebooted both webservers again, after applying windows updates, and both servers retained all ip addresses assigned to them, post reboot. At this point, I believe this ip issue is resolved. If the issue reoccurs, I will update this thread. For all future ip address additions, I am going to add them directly to the registry key noted previously instead of adding them via the normal Network Connections section. Just wanted to thank everyone for their input, especially Steve Kline, for the very helpful script which I have saved as a Backup fix in case the ip issue returns.