Description of Address Resolution Protocol (ARP) caching behavior in Windows Vista TCP/IP implementations
| Article ID | : | 949589 |
| Last Review | : | March 25, 2008 |
| Revision | : | 2.0 |
INTRODUCTION
MORE INFORMATION
The ArpCacheLife and ArpCacheMinReferencedLife registry entries determine how the ARP cache is maintained in Windows XP and in Windows Server 2003. These registry entries no longer apply to Windows Vista.
In the new Windows Vista TCP/IP stack implementation, hosts create the neighbor cache entries when there is no matching entry in the neighbor cache. ARP cache entry for IPv4 is an example of a neighbor cache entry. After the entry is successfully created in the neighbor cache, the entry may change to the Reachable state if the entry meets certain conditions. If the entry is in the Reachable state, Windows Vista TCP/IP hosts do not send ARP requests to the network. Therefore, Windows Vista TCP/IP hosts do not use the information in the cache. If entry is not used and stays in the Reachable state for longer than its Reachable Time value, the entry changes to the Stale state. If an entry is in the Stale state, the Windows Vista TCP/IP host must send an ARP request to reach that destination.
The Reachable Time value is calculated as follows:
RFC provides the following calculated results.
| BaseReachable Time | 30,000 milliseconds (ms) |
| MIN_RANDOM_FACTOR | 0.5 |
| MAX_RANDOM_FACTOR | 1.5 |
Therefore, the Reachable Time value is somewhere between 15 seconds (30 × 0.5 seconds) and 45 seconds (30 × 1.5 seconds). If an entry is not used for a time between 15 to 45 seconds, it changes to the Stale state. Then, the host must send an ARP Request for IPV4 to the network when any IP datagram is sent to that destination.
To see the current Reachable Time value, follow these steps:
| 1. | Click Start, type cmd in the Start Search box, and then click cmd in the Programs list. |
| 2. | If you are prompted for an administrator password or for confirmation, type your password, or click Continue. |
| 3. | At the command prompt, type the following command:
netsh interface ipv4 show interfaces
Example result: Idx Met MTU State Name--- --- ----- ----------- ------------------- 1 50 4294967295 connected Loopback Pseudo-Interface 1 9 20 1500 connected Local Area Connection |
| 4. | In step 2 the Local Area Connection Idx is 9. Therefore, you can show interface 9 by typing the following command at the command prompt:
netsh interface ipv4 show interface 9
Example result: Interface Local Area Connection Parameters----------------------------------------------IfLuid : ethernet_7IfIndex : 9Compartment Id : 1State : connectedMetric : 20Link MTU : 1500 bytesReachable Time : 19000 ms Base Reachable Time : 30000 ms Retransmission Interval : 1000 ms DAD Transmits : 3 Site Prefix Length : 64 Site Id : 1 Forwarding : disabled Advertising : disabled Neighbor Discovery : enabled Neighbor Unreachability Detecion : enabled Router Discovery : dhcp Managed Address Configuration : enabled Other Stateful Configuration : enabled Weak Host Sends : disabled Weak Host Receives : disabled Use Automatic Metric : enabled Ignore Default routes : disabled |
| 5. | You can change the BaseReachable Time value by typing the following example command at the command prompt:
netsh interface ipv4 set interface 9 basereachable=60000
|
| 6. | To see the result of step 4, type the following command at the command prompt:
netsh interface ipv4 show interface 9
Example result: Interface Local Area Connection Parameters----------------------------------------------IfLuid : ethernet_7IfIndex : 9Compartment Id : 1State : connectedMetric : 20Link MTU : 1500 bytesReachable Time : 61500 msBase Reachable Time : 60000 ms Retransmission Interval : 1000 ms DAD Transmits : 3 Site Prefix Length : 64 Site Id : 1 Forwarding : disabled Advertising : disabled Neighbor Discovery : enabled Neighbor Unreachability Detecion : enabled Router Discovery : dhcp Managed Address Configuration : enabled Other Stateful Configuration : enabled Weak Host Sends : disabled Weak Host Receives : disabled Use Automatic Metric : enabled Ignore Default routes : disabled Note The Base Reachable Time value has changed to 60000 ms. |
| 7. | You can increase the neighbor cache limit by typing the following command at the command prompt:
netsh interface ipv4 set global neighborcachelimit = 4096
Note The default neighbor cache limit is 256. |
For more information about the neighbor cache entry states, visit the following Web site:
For more information about TCP/IP registry values for Windows Vista and for Windows Server 2008, visit the following Web site:
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.
Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
APPLIES TO
| • | Windows Vista Business |
| • | Windows Vista Enterprise |
| • | Windows Vista Home Basic |
| • | Windows Vista Home Premium |
| • | Windows Vista Ultimate |
| • | Windows Vista Business 64-bit Edition |
| • | Windows Vista Enterprise 64-bit Edition |
| • | Windows Vista Home Basic 64-bit Edition |
| • | Windows Vista Home Premium 64-bit Edition |
| • | Windows Vista Ultimate 64-bit Edition |
Keywords:Â |
kbexpertiseinter kbinfo KB949589 |
Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
Microsoft Corporation. All rights reserved. Terms of Use | Trademarks
You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.
Back to the top
Leave a Reply