Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have an application that uses ftp on windows 7 or 8 and it fails trying to upload a file (time out, server sends back RST packets so it's definitely the server that's unhappy) to a specific server. Same problem with command line ftp. With filezilla it also fails unless I turn on the speed limit (upload at 2kB/sec) and then it works fine.

So, how do I slow down the generic ftp, that I assume the application is using? (That may be a bad assumption as I don't really know how the application calls ftp.) Or is there another way to configure packet size or some other way to throttle the data. I did look at packets through my firewall and when they are uploading with 576 byte packets from my linux box it works fine but when it's at 596 from my windows box it fails. I don't know if the size of the packets has anything to do with it. It is uploading to a windows server that is not apparently very new.

UPDATE: It has nothing to do with speed so much as packet size. The default server packet allows for 536 bytes of data and the default client size is much larger, so the server complains when it receives a too large packet by sending RST packets and the client doesn't try again with a smaller size, it just tries again with the same size, or if it does then somehow my firewall does not allow it to work. If someone could explain that I'd appreciate it. In the meantime the owner of the server flipped a switch that allows "fragmented packets" and now it works.

share|improve this question

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.