download problem with IIS 6.0 on Win 2003 server

downloads timeout after a while

[flying monkey]

when a visitor visits my site and tryu to download a file, the download starts then all of sudden the download freezes. you have to keep restarting it. what is the cause of it.

[txbakers]

Not sure, but it could be permissions. W2003 is very, very tight with allowing things to happen. It's one of the new features - everything is locked until you specifically open it.

Check the permissions on the directory trying to be downloaded and make sure IUSR_XXXXXX has privileges on it.

[flying monkey]

well the download starts and completes 25% persent of the download then just freezes. so its able to access the file and is not a permmisions issue.

[bignet]

certainly not a permission issue. looks like bandwidth/connection timeout issue

What type of connection do you have?
Are you sure you have good enough bandwidth
also try increasing the connection timeoout value

[flying monkey]

i have cable modem and i have tried upping the timeout value it just makes the down load go further but it still freezes

[bignet]

which confirms imo the bandwidth/connection cause of this issue

[bignet]

time for a t1 upgrade?

[dhall]

Hey flying monkey:
These guys don't know what they are talking about. The downloads are freezing because your IIS Client Requests is timing out. This is normally due to large file sizes being downloaded through a HTTP connection. This option can be changed. The two options you need to change are:

ConnectionTimeout: Specifies the amount of time, in seconds, that the server will wait before disconnecting an inactive connection.

MinFileBytesPerSec: When IIS responds to a client request, the MinFileBytesPerSec property determines the length of time the client has to receive the entire response. If the client machine takes too long to receive the entire response, the kernel-mode driver, HTTP.sys, terminates the connection.

The ConnectionTimeout can be configured in the IIS Manager and the MinFileBytesPerSec needs to be configured in the MetBase file.

First, open the IIS Manager and change the Connection timeout in seconds to a reasonable amount for your website. Next, go to the Properties of your IIS and enable the "Enable Direct Metabase Edit" option. Now open the metbase.xml file which is located in the %systemroot%\system32\inetsrv folder. This file can be edited with NotePad, but be careful. Do a search for MinFileBytesPerSec. You'll find one entry for this with a default of 240. Increase this to a suitable amount and save the file. The change will take affect immediately. You'll need to fine tune these settings to your preference.

This will fix your problem. Good Luck!

[dhall]

Sorry, I fat fingered the file name. It's the MetaBase.xml file.