iis ftp: Windows 2000 Adv Server running IIS 5.0 with all the
patches. when uploading serveral small files I get the
message Connection Closed by remote host. I have tried
with multiple clients and still get the same intermittant
error. the server has minimal traffic and the connection
closeing has even happened when connecting to the same
subnet.

I have thaugh about ripping out tcp/ip and reinstalling
but I will probably will have to setup all my web sites
and ftp sites again and would like to avoid that.

Any suggestions would be appreciated.

how many small files ?
even with command line utility and 'mput *.*' ??

ftp log 426 error ?

--
Regards,
Bernard Cheah
http://www.tryiis.com/
http://support.microsoft.com/
http://www.msmvps.com/bernard/



[quoted text, click to view]

[quoted text, click to view]

With several transfers over a short period of time, it's possible that the
range of ports in use can get clogged up. If you're using active mode
transfers (the PORT command gets sent from the client to the server), the
pool of ports being used up is smaller, because the port at the server side
is fixed at 20, and if you proceed through all the available ephemeral ports
at the client side, inside of four minutes, the server will be unable to
make a data connection to the client.

If you're using passive mode transfers (the PASV command is sent from client
to server), the connection is made in the other direction - the client
connects to the server. In such a case, although the client is _supposed_
to bind to a static port (RFC 959 states that the default client port should
be the same as its control connection is already bound to), nobody does
that. As a result, you're unlikely to get the same problem, as sockets are
prevented from reuse only if both ends of the socket match one that's
already in "TIME_WAIT" state.

Either way, you may want to increase the number of ephemeral ports available
using the advice in the KB article http://support.microsoft.com/?id=196271

To see if this might be the problem, when you find your transfer is denied
after too many small files, try running the command "netstat -a | findstr
TIME_WAIT" at the command prompt. If you don't have very many such
connections, this is likely not to be your problem. [Note that the
TIME_WAIT sockets expire four minutes after they are closed, so be quick to
send the command!]

Alun.
~~~~