Hi, > Message: 9 > Date: Wed, 17 Jan 2001 22:26:24 +0100 > From: mouss <[EMAIL PROTECTED]> > Subject: RE: Problems with Fragment bit Set in big packets! > At 09:20 17/01/01 -0600, Stitzel, Jon wrote: >>We had the same kind of problem and discovered a "feature" in Windows. It >>seems >>that Windows (NT at least, I don't know about 2000) always sets the Don't >>Fragment" bit. We had to lower the MTU on our firewalls to accommodate >>this, >>since our NT guys said we couldn't set a static MTU on the servers. Perhaps the following can help. Please try it! It is from the WindowsNT-FAQ: ============================================================================================== A. By default, NT will use a Maximum Transmission Unit (MTU) (packet size) over the path to a remote host of 576. Problems can arise if the data is sent over routes etc that cannot handle data of this size and the packets get fragmented. The parameter EnablePMTUDiscovery set to 1 forces NT to discover the maximum MTU of all connections that are not on the local subnet. To change this perform the following: 1. Start the registry editor (regedit.exe) 2. Move to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters 3. From the Edit menu select New-DWord value 4. Enter a name of EnablePMTUDiscovery and press enter 5. Double click on this new value and set to 1 then click OK 6. Close the registry editor and reboot the machine. By discovering the Path MTU and limiting TCP segments to this size, TCP can eliminate fragmentation at routers along the path that connect networks with different MTUs. Fragmentation adversely affects TCP throughput and network congestion. =============================================================================================== best regards TOM - [To unsubscribe, send mail to [EMAIL PROTECTED] with "unsubscribe firewalls" in the body of the message.]
