Gmail Calendar Documents Reader Web more »
Recently Visited Groups | Help | Sign in
Google Groups Home
Reassembly timeout limit on Win2K and Win XP
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  2 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Tomer Peleg  
View profile  
 More options Sep 21, 11:08 am
Newsgroups: microsoft.public.win32.programmer.networks
From: Tomer Peleg <Tomer Pe...@discussions.microsoft.com>
Date: Mon, 21 Sep 2009 08:08:09 -0700
Local: Mon, Sep 21 2009 11:08 am
Subject: Reassembly timeout limit on Win2K and Win XP

Hello,

We have developed a communication system which is composed of two parts:
Application layer, and Data link layer.
The two layers are developed as two different systems. The application layer
is developed using a standard PC, running a Win2K or Win XP operating systems.

The data link supports UDP-IP as the communication protocol. Due to the size
of the messages, and the time it takes the data link to transfer the
messages, it takes a single message more than 60 seconds from the time the
first IP packet is been received to the last IP packet (The entire UDP
message).

Due to the Reassembly time out limitation of the operating system in the
receiving station, the application layer does not receive the message.
We have changed the IpReassemblyTimeout in the registry (under
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters) to be
180 seconds (D4 hex value).
We found out that despite the change we made, the actual Reassembly time out
is limited to around 120 seconds (trial and error).
We would like to know the following:
1. Is there a Reassembly time out maximum value ? What is the limitation?
2. Is there a way to overcome this limitation?
3. Are there any other parameters that are relevant to the reassembly
mechanism?

Thank you for your help,
Tomer Peleg,
Senior communication system engineer
Elbit Systems limited


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
K. Amlah  
View profile  
 More options Oct 22, 2:28 pm
Newsgroups: microsoft.public.win32.programmer.networks
From: K. Amlah <K. Am...@discussions.microsoft.com>
Date: Thu, 22 Oct 2009 11:28:01 -0700
Local: Thurs, Oct 22 2009 2:28 pm
Subject: RE: Reassembly timeout limit on Win2K and Win XP
This is a security constraint (like you said). Reducing this value is
possible but increasing it beyond 60 is impossible. This is Windows specific
and has nothing to do with the protocol (timeout periods are not a part of
the specification in the UDP standard), so on Linux for example, this would
not have been a limitation.

Your only option is to work directly with the network subsystem (either the
NDIS or TDI layers). There are many SDK's available for this out there.


    Reply    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2009 Google