問題描述：這個錯誤是由於服務器連接被中斷導致的。
If you check out the C:"Windows"system32"LogFiles"HTTPERR"httperr*.
log files on the distribution server, you'll likely see either Timer_MinBytesPerSecond
errors or Timer_ConnectionIdle errors. These are caused by IIS' default settings,
contained within its metabase, which define the minimum traffic flow rate for a
connection o be kept alive and the maximum idle time allowed before a connection
is dropped. For some reason, SUS servers seem to take their good old time while
downloading updates, and these parameters are exceeded and the distribution server drops 'em.
這個問題是由於在某些應用下，IIS的默認設置不當的
1) From IIS Manager, right click on the Internet Information
Server (IIS) Manager root level folder and go to Properties.
Check the box to enable direct metabase editing. Click OK.
1）打開Internet 信息服務（IIS）管理器，右鍵點“我的計算機”——屬性，
選上“允許直接編輯配置數據庫(N)”，確定。
2) Open the C:"Windows"system32"inetsrv"MetaBase.xml file in Notepad.
Do a search for "MinFileBytesPerSec".
Change the setting for MinFileBytesPerSec from 240 to 0.
Do another search, this time for "ConnectionTimeout" to be 600.
Save changes and exit.
2）編輯C:"Windows"system32"inetsrv"MetaBase.xml文件，
把MinFileBytesPerSec 參數值從240改爲0，
把ConnectionTimeout參數設成600。
3) Restart the IIS Admin service to effect the changes.
3）重新起動IIS服務
替代方法
如果您安裝最新 for Windows Server 2003, ServicePack 後問題仍然存在網絡連接可能太慢。
使用網絡跟蹤來確定客戶是否接收響應和重傳數據包中延遲。
要變通解決此問題, 減少或禁用 IIS 6.0 以阻止從早關閉慢速客戶連接中 MinFileBytesPerSec 屬性。