<p>We have a problem with serveral windows 7 clients where they will not hold a persisent route after a reboot of the machine. For those same machines they do not pick up Static routes passed from DHCP using option 249 in DHCP scope options.</p><p>It seems to me that something is causing them to be wiped from the routing tables, as when you do a route print after adding the Persistent route it is there and soon as you reboot it disappears.</p><p></p><p></p> Some further Info after testing. It looks as though what is happening is that DHCP Server (on windows 2003) is assinging ip address to my Windows 7 clients the lease is meant to be 6 days, and when you check the lease in DCHP server or the client using IPconfig details look fine. In the routing table all info looks correct lease times and expiry dates all look ok, option 249 (static routes are pulled through). Then when you reboot windows 7 client it gets a new 6 day lease at the reboot time and looses the option 249 static route. for the next 2 days the same happens on Reboot, and then on day 3 (50% of the original leae time) the option 249 comes back again until you reboot again. I am still in the middle of testing this but I thought this might be helpful. It seems to me that windows 7 clients are somehow renewing the lease each reboot without taking all details from DHCP server which causes these routes to be lost until 50% lease time again.

Hi, Firstly, please let us know whether all the persistent routes are lost or the persistent routes are changed after a reboot. Meanwhile, based on my research, please try the following: 1. Please check whether the persistent routes are exist in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\PersistentRoutes after rebooting. 2. Please refer to How to reset Internet Protocol (TCP/IP), reset TCP/IP and see how it works. 3. Please try to disable accepting ICMP redirect messages by setting the value of EnabledICMPRedirect to 0 which under HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters\ Note: please backup your registry first. 4. Please boot into Safe Mode with Networking and test the issue again. In addition, based on my knowledge, this issue may be also caused by the incorrect setting in your DHCP Server. Therefore, it is also recommended to post the thread in Windows Server Forums. Hope this helps. Jeremy Wu TechNet Community Support

Thank you this was useful. I so far have 2 things to report back 1. PersistentRoutes are lost, they are not in the registry after a reboot either. (I thought I would look at the permisssions of this key to see if there was something unusal, but I have checked against the regisrty keys where this is working correct and cannot see any differences). Point 3. On the First workstation I checked in the problem site this registry key does not exist. I thought this could be relavant. Any further info would be useful, in the meantime I am working through the rest of your post. Thank you Steve Frost

Hi, Firstly, please let us know whether all the persistent routes are lost or the persistent routes are changed after a reboot. Meanwhile, based on my research, please try the following: 1. Please check whether the persistent routes are exist in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\PersistentRoutes after rebooting. 2. Please refer to How to reset Internet Protocol (TCP/IP), reset TCP/IP and see how it works. 3. Please try to disable accepting ICMP redirect messages by setting the value of EnabledICMPRedirect to 0 which under HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters\ Note: please backup your registry first. 4. Please boot into Safe Mode with Networking and test the issue again. In addition, based on my knowledge, this issue may be also caused by the incorrect setting in your DHCP Server. Therefore, it is also recommended to post the thread in Windows Server Forums. Hope this helps. Jeremy Wu TechNet Community Support

Thank you this was useful. I so far have 2 things to report back 1. PersistentRoutes are lost, they are not in the registry after a reboot either. (I thought I would look at the permisssions of this key to see if there was something unusal, but I have checked against the regisrty keys where this is working correct and cannot see any differences). Point 3. On the First workstation I checked in the problem site this registry key does not exist. I thought this could be relavant. Any further info would be useful, in the meantime I am working through the rest of your post. Thank you Steve Frost

Hi Frostyman65, Have you got any update about this issue? Meanwhile, based on my further research, please refer to DHCP Option Code 249 (0xF9) - Microsoft Classless Static Route Option and note The length and the data format for the Microsoft Classless Static Route Option are exactly the same as those specified for the Classless Static Route Option in [RFC3442]; the only difference is that Option Code 249 SHOULD<11> be used instead of or in addition to Option Code 121. Also, please refer to RFC3442 and note the DHCP Client Behavior section in Page 4. Therefore, based on my understanding, Im afraid that the issue is more related to the configuration in your DHCP Server than Windows 7. It is also recommended to post the thread in Windows Server Forums. Hope this helps. Jeremy Wu TechNet Community Support

Hi Frostyman65, Have you got any update about this issue? Meanwhile, based on my further research, please refer to DHCP Option Code 249 (0xF9) - Microsoft Classless Static Route Option and note The length and the data format for the Microsoft Classless Static Route Option are exactly the same as those specified for the Classless Static Route Option in [RFC3442]; the only difference is that Option Code 249 SHOULD<11> be used instead of or in addition to Option Code 121. Also, please refer to RFC3442 and note the DHCP Client Behavior section in Page 4. Therefore, based on my understanding, Im afraid that the issue is more related to the configuration in your DHCP Server than Windows 7. It is also recommended to post the thread in Windows Server Forums. Hope this helps. Jeremy Wu TechNet Community Support