WSUS clients may receive invalid responses from a Windows Server 2003 SP1-based computer that is running WSUS, and the clients cannot connect to the WSUS server

Windows Server Update Services (WSUS) clients try to connect to a Microsoft Windows Server 2003 Service Pack 1 (SP1)-based computer that is running WSUS. When the WSUS clients try to connect, the WSUS server may send invalid responses. Therefore, the WSUS clients cannot establish a connection with the WSUS server because the WSUS clients received invalid responses.

This problem occurs because of a race condition that occurs in the Microsoft Internet Information Service (IIS) 6.0 HTTP service.

To resolve this problem, install the hotfix that is described in the Microsoft Knowledge Base article 898708. For more information about the KB898708 hotfix, click the following article number to view the article in the Microsoft Knowledge Base:

To work around this issue, follow these steps on the WSUS server:

1. Disable HTTP compression in IIS 6.0.
   
   Note For information about how to disable and to enable HTTP compression in IIS 6.0, see the "More Information" section.
2. Click Start, click Run, type %windir%\system32\inetsrv, and then click OK.
3. In the Inetsrv folder, locate and right-click the suscomp.dll file, and then click Rename.
4. Type suscompold.dll, and then press ENTER.
5. Close the Inetsrv folder.
6. Click Start, click Run, type cmd, and then click OK.
7. To restart IIS, type iisreset at the command prompt, and then press ENTER.
8. To stop WSUS, type net stop wsusservice at the command prompt, and then press ENTER.
9. To start WSUS, type net start wsusservice at the command prompt, and then press ENTER.
10. Close the Command Prompt window.
11. Enable HTTP compression in IIS 6.0.

Microsoft has confirmed that this is a problem in Internet Information Services 6.0. .

For information about how to enable and to disable HTTP compression, visit the following Microsoft Web site: