On Fri, 16 Jul 2004 08:51:40 -0700, "Vidal" <vidalito3@hotmail.com>
[quoted text, click to view]

This doesn't sound like an IIS issue. IIS4 can easily handle files of
3MB or more. It sounds more like a network issue to me. What error do
you see in the IIS log files ? Is there enough free disk space on the
drive where the FTP folder is located ?


Regards,

Paul Lynch

On Fri, 16 Jul 2004 09:40:44 -0700, "Vidal" <vidalito3@hotmail.com>
[quoted text, click to view]

So then its isn't an IIS issue I'm afraid. You need to fix your
network problem.


Regards,

Paul Lynch

[quoted text, click to view]

One possible cause for this could be a router, firewall or NAT (which is a
kind of router) in between the client and server. FTP, as you know, uses
two network connections - one, the "control connection" for commands and
responses to those commands; the other, the "data connection" is used when
transferring files, or file listings.

When you're transferring a file, the control connection is not generally
doing anything. As a result, some routers / firewalls decide that the
connection has been "idle too long", and they disconnect that connection.
This looks, to server and client, as if the other has disconnected them,
and so one or both of them will terminate the transfer.

You can fix this by a couple of methods:
1. Increase the length of the timeout at whichever router is terminating
the connection.
2. Use an FTP client that sends intermittent commands during a file
transfer in order to keep the connection open.
3. Find a router that will recognise that the data and control connections
represent a single logical connection.

Option 3 may be as easy as downloading and installing a new firmware update
for your router. Contact your router manufacturer for details.

Alun.
~~~~