Windows NT Router May Drop IP Packets While Awaiting ARP ResponseID: Q194881
|
When Windows NT Server version 4.0 is configured as a router, some routed IP packets may be dropped while the server awaits an ARP response from the destination or next hop router.
If a Windows NT router does not have an Ethernet (media access control)
address entry for the destination or next hop router in its ARP cache, it
will have to send an ARP Request. While Windows NT awaits an ARP Response,
ARP will "queue" the IP packet that needs to be sent. When Windows NT
receives the ARP Response, it will only transmit the "latest" or last
packet that it received in its "ARP Packet Queue" for any given destination
host.
A common example of this phenomenon would be a ping (ICMP) message larger
than the MTU of a given network segment. This will force TCP/IP to fragment
the message into multiple packets. When Windows NT receives packet 1 of 2,
it will send an ARP Request for the destination or next hop router. Before
it receives the ARP Response, it will receive packet 2 of 2 of the ping
message. When Windows NT finally receives the ARP Response, it will only
transmit the "latest" or last packet it received -- the rest would be
discarded.
For detailed information about the Address Resolution Protocol (ARP) in
Windows NT Server version 4.0, please download the "TCP/IP Implementation
Details" white paper from the Microsoft FTP Site:
ftp://ftp.microsoft.com/bussys/winnt/winnt-docs/papers/TCPIMP2.EXEFor more information about the ARP Packet Queue, please see RFC 1122 - "Requirements for Internet Hosts -- Communication Layers".
Additional query words: ntrouter
Keywords : kbnetwork
Version : WinNT:4.0
Platform : winnt
Issue type : kbinfo
Last Reviewed: February 22, 1999