Windows Seven lost it's DHCP IP address
Hi, I see phenomenon on my Windows Embedded stations, when my DHCP server is down Workstations IP address are not kept but address with 169.x.x.x are configured on the Workstation this phenomenon is maybe because my workstations can't ping the gateway so a new IP is granted with 169.x.x.x address.... But why my station can't keep it's IP address assign by the DHCP until the bail expiration.... I've tried du configured in registry the key "DontPing Gateway", like proposed in M$ KB 958336 but no more results. Have you already seen this problem ? Many thank in advance for your answer. best regards Raymond
May 16th, 2013 7:56am

By default Windows attempts IP renewal when half of the lease expiry is past. It does the equivalent of ipconfig /renew, so if no dhcp server is available this will result in an APIPA address. You could lenthen the lease time for the ip leases, but better, consider making a high available DHCP setup. DHCP is a crucial infratsructure service, so you should design it to limit the amount of (possible) downtime!MCP/MCSA/MCTS/MCITP
Free Windows Admin Tool Kit Click here and download it now
May 16th, 2013 9:30am

Hi, Many thanks for your answer, I am testing right now my Windows seven workstation behavior, the lease is configured for 8 days and right now I have 8 days for the lease, but as soon as I stop my Dhcp, when I restart the workstation, adresse become 169.x.x.x. Normaly the workstation should keep the addresse lease by the Dhcp, even if this DHCP is down. NO ?
May 16th, 2013 9:47am

No, Windows does not retain IP leases across reboots or when the nic has been disabled/unplugged. That is by design; the user might have placed the system elsewhere/in another network! So the equivalent of ipconfig /renew is done in such scenarios. As far as I know, that behavior is not configurable.MCP/MCSA/MCTS/MCITP
Free Windows Admin Tool Kit Click here and download it now
May 16th, 2013 10:27am

Hi, I see phenomenon on my Windows Embedded stations, when my DHCP server is down Workstations IP address are not kept but address with 169.x.x.x are configured on the Workstation this phenomenon is maybe because my workstations can't ping the gateway so a new IP is granted with 169.x.x.x address.... But why my station can't keep it's IP address assign by the DHCP until the bail expiration.... I've tried du configured in registry the key "DontPing Gateway", like proposed in M$ KB 958336 but no more results. Have you already seen this problem ? Many thank in advance for your answer. best regards Raymond
May 16th, 2013 2:46pm

Hi, please refer to my replies on your other thread: http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/abea882f-ad7a-4007-9cf2-6702abc9aaff/#a18d8012-072b-4565-b3aa-34068de1800e Please consider cross or doubleposting is not considered good practice on most internet forums!MCP/MCSA/MCTS/MCITP
Free Windows Admin Tool Kit Click here and download it now
May 17th, 2013 12:04am

Hi, Many thanks for your answer, I am testing right now my Windows seven workstation behavior, the lease is configured for 8 days and right now I have 8 days for the lease, but as soon as I stop my Dhcp, when I restart the workstation, adresse become 169.x.x.x. Normaly the workstation should keep the addresse lease by the Dhcp, even if this DHCP is down. NO ? If the DHCP client is Windows Vista/2008 or newer, during a renewal, the IP hasn't changed, then a client will retain it's config and previously configured options until end of lease based on it's Local Storage, including options. That's why you have to release it to get a fresh configuration. Read more for specifics: ======= Windows VIsta, Windows 7, and newer, DHCP Lease Behavior is different than Windows 2000 and Windows XP upon startup DHCP Client Behavior http://blogs.technet.com/b/networking/archive/2009/01/29/dhcp-client-behavior.aspx If the DHCP client obtained a lease from a DHCP server on a previous occasion, and the lease is still valid (not expired) at system startup, the client tries to renew its lease. If, during the renewal attempt, the client fails to locate any DHCP server, it attempts to ping the default gateway listed in the lease, and proceeds with one of the following: If the ping is successful, the DHCP client assumes that it is still located on the same network where it obtained its current lease, and continues to use the lease as long as the lease is still valid. By default the client then attempts, in the background, to renew its lease when 50 percent of its assigned lease time has expired. If the ping fails, the DHCP client assumes that it has been moved to a network where a DHCP server is not available. The client then auto-configures its IP address by using the settings on the Alternate Configuration tab. When the client is auto-configured, it attempts to locate a DHCP server and obtain a lease. As a workaround, you can force a Windows Vista or Windows 7 DHCP client to keep the old DHCP lease by adding registry key DontPingGateway if connectivity fails, see the resolution in the KB article below: Windows Vista does not keep its DHCP IP address if a DHCP server is not available (works for Windows 7, too): http://support.microsoft.com/kb/958336 - References and previous discussions on this topic: Clients get autoconfig address when DHCP server is down http://social.technet.microsoft.com/Forums/en-US/winserverNIS/thread/0f1a6d43-aca1-41c7-bac8-a24632a34644 How can Windows 7 Client hold DHCP Config after reboot without DHCP Server running? http://social.technet.microsoft.com/forums/en-us/winserverNIS/thread/245EF423-F2CA-42CD-8CAF-8B12D4565633 Windows 7 machines not getting DHCP IP !!!!URGENT!!!!!! http://social.technet.microsoft.com/Forums/en-US/winserverNIS/thread/c5f0c1b3-b6bf-465c-9b96-5ea1c9198bbc - DHCP Architecture: http://technet.microsoft.com/en-us/library/dd183602(WS.10).aspx See the following for a discussion on what happens after you change a DHCP Option: Technet thread - Remove WINS from DHCP scope (10/3/2011) http://social.technet.microsoft.com/Forums/en-US/winserverNIS/thread/675d6312-8f11-4c4d-a8d4-5a6e84a5e72f/ -Ace Fekay MVP, MCT, MCITP/EA, MCTS Windows 2008/R2 & Exchange 2007, Exchange 2010 EA, MCSE & MCSA 2003/2000, MCSA Messaging 2003 Microsoft Certified Trainer Microsoft MVP - Directory Services Technical Blogs & Videos: http://www.delawarecountycomputerconsulting.com/ This post is provided AS-IS with no warranties or guarantees and confers no rights.
May 17th, 2013 11:50am

Instead of marking the post as abusive, we usually ask one of the Moderators, such as Jeremy, to merge the threads into one post. - Regarding the poster's question, whether he/she multi-posted it or not: If the DHCP client is Windows Vista/2008 or newer, during a renewal, the IP hasn't changed, then a client will retain it's config and previously configured options until end of lease based on it's Local Storage, including options. That's why you have to release it to get a fresh configuration. Read more for specifics: ======= Windows VIsta, Windows 7, and newer, DHCP Lease Behavior is different than Windows 2000 and Windows XP upon startup DHCP Client Behavior http://blogs.technet.com/b/networking/archive/2009/01/29/dhcp-client-behavior.aspx If the DHCP client obtained a lease from a DHCP server on a previous occasion, and the lease is still valid (not expired) at system startup, the client tries to renew its lease. If, during the renewal attempt, the client fails to locate any DHCP server, it attempts to ping the default gateway listed in the lease, and proceeds with one of the following: If the ping is successful, the DHCP client assumes that it is still located on the same network where it obtained its current lease, and continues to use the lease as long as the lease is still valid. By default the client then attempts, in the background, to renew its lease when 50 percent of its assigned lease time has expired. If the ping fails, the DHCP client assumes that it has been moved to a network where a DHCP server is not available. The client then auto-configures its IP address by using the settings on the Alternate Configuration tab. When the client is auto-configured, it attempts to locate a DHCP server and obtain a lease. As a workaround, you can force a Windows Vista or Windows 7 DHCP client to keep the old DHCP lease by adding registry key DontPingGateway if connectivity fails, see the resolution in the KB article below: Windows Vista does not keep its DHCP IP address if a DHCP server is not available (works for Windows 7, too): http://support.microsoft.com/kb/958336 - References and previous discussions on this topic: Clients get autoconfig address when DHCP server is down http://social.technet.microsoft.com/Forums/en-US/winserverNIS/thread/0f1a6d43-aca1-41c7-bac8-a24632a34644 How can Windows 7 Client hold DHCP Config after reboot without DHCP Server running? http://social.technet.microsoft.com/forums/en-us/winserverNIS/thread/245EF423-F2CA-42CD-8CAF-8B12D4565633 Windows 7 machines not getting DHCP IP !!!!URGENT!!!!!! http://social.technet.microsoft.com/Forums/en-US/winserverNIS/thread/c5f0c1b3-b6bf-465c-9b96-5ea1c9198bbc - DHCP Architecture: http://technet.microsoft.com/en-us/library/dd183602(WS.10).aspx See the following for a discussion on what happens after you change a DHCP Option: Technet thread - Remove WINS from DHCP scope (10/3/2011) http://social.technet.microsoft.com/Forums/en-US/winserverNIS/thread/675d6312-8f11-4c4d-a8d4-5a6e84a5e72f/ -Ace Fekay MVP, MCT, MCITP/EA, MCTS Windows 2008/R2 & Exchange 2007, Exchange 2010 EA, MCSE & MCSA 2003/2000, MCSA Messaging 2003 Microsoft Certified Trainer Microsoft MVP - Directory Services Technical Blogs & Videos: http://www.delawarecountycomputerconsulting.com/ This post is provided AS-IS with no warranties or guarantees and confers no rights.
Free Windows Admin Tool Kit Click here and download it now
May 17th, 2013 6:47pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics