NNTP server does not work correctly on a Windows Server 2003-based computer

When you use a Microsoft Exchange-based Network News Transfer Protocol (NNTP) server on a Microsoft Windows Server 2003-based computer, you may experience the following symptoms:

�	When a post is rejected, a half-sent file or a rejected file is left on the computer. This file will be picked up in the next NNTP hash table rebuild.
�	Connection size limit and post size limit are not applied to feed connections.
�	During the NNTP hash table rebuild, feed posting is permitted. This causes hash table problems and missing messages.
�	When the size of the NNTP hash table file is large, the NNTP service cannot start successful because the Service Control Manager (SCM) is not notified in time.
�	The NNTP hash table requires contiguous memory, but the computer cannot allocate such a big block of memory.
�	The NNTP hash table becomes corrupted.
�	The NNTP server stops responding when you enable certain protocols and configure logon options for these protocols.

Service pack information

To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site: Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" section and the online request forms display the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

No prerequisites are required.

Restart requirement

You must restart the NNTP service.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

Windows Server 2003, 64-bit Itanium-based versions

   Date         Time   Version            Size  File name
   --------------------------------------------------------
   28-Jul-2004  12:18  6.0.3790.196    356,864  Nntpfs.dll
   28-Jul-2004  12:18  6.0.3790.196  1,659,392  Nntpsvc.dll

Windows Server 2003, 32-bit versions

   Date         Time   Version          Size  File name
   ------------------------------------------------------
   29-Jul-2004  00:30  6.0.3790.196  139,264  Nntpfs.dll
   29-Jul-2004  00:30  6.0.3790.196  567,296  Nntpsvc.dll

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

For more information about how to configure NNTP service, click the following article numbers to view the articles in the Microsoft Knowledge Base: For more information about the standard terminology that is used to describe Microsoft software updates, click the following article number to view the article in the Microsoft Knowledge Base: