496608d1   
   XPost: comp.arch.embedded, sci.electronics.design   
   From: FatBytestard@somewheronyourharddrive.org   
      
   On Thu, 10 Sep 2009 13:07:05 -0700 (PDT), Dimiter Popoff    
   wrote:   
      
   >On Sep 10, 11:25 pm, "Paul Hovnanian P.E."  wrote:   
   >> You might have to adjust your system's MTU, MSS, or other networking   
   >> parameters. I'm not certain how to do this in Windows, or why you would   
   >> be having problems on a 100 Mbps Ethernet link.   
   >   
   >I did play with them - and they are nothing special anyway (e.g. 1460   
   >bytes   
   >tcp segment size etc.), things are pretty much "normal".   
   >   
   > And I must say it only happens with the ftp server, so it may be its   
   >fault after all (get clogged at some point and stays stuck with the   
   >socket buffer being full, hence the constant 0 window - while the rest   
   >of the network is OK and other tcp connections keep on working).   
   >   
   > I'll try to locate and install some other ftp server and see what   
   >happens.   
   >   
   >Dimiter   
   >   
      
     There are also some settings on the card itself usually (the device).   
      
     In the device settings dialogs, there is a page where hard 100Mb/s is   
   selected or "auto", which is what the whole world typically uses.  Hardly   
   anyone hard sets a link to 100Mb/s. Auto negotiation has usually been the   
   rule.  Anyway, there are quite a few other settings there as well.   
      
     This is not registry settings, it is for the card itself in device   
   manager (there are also other ways to get to this device dialog).   
      
   Try examining that. Perhaps you hard set it to 100Mb/s, which was "auto".   
   If so, that is one of your mistakes.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)