Policy Editor Does Not Read SNMP Communities Correctly

ID: Q228543

The information in this article applies to:

Microsoft Windows NT Server version 4.0 SP4

SYMPTOMS

Simple Network Management Protocol (SNMP) communities are enhanced in Windows NT 4.0 Service Pack 4 to include permissions for communities. Policy Editor (Poledit.exe) cannot read these permissions or community names correctly because of changes made in the registry to support community security.

CAUSE

Because Policy Editor reads all of the necessary registry entries at startup and then writes all of the entries when saved, whether the entry was changed or not, the SNMP configuration information was removed from Policy Editor to prevent the SNMP communities from being written in the previous format and because the SNMP configuration is not a policy.

RESOLUTION

To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual software update. For information on obtaining the latest service pack, please go to:

http://www.microsoft.com/Windows/ServicePacks/

Q152734 How to Obtain the Latest Windows NT 4.0 Service Pack

For information on obtaining the individual software update, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://www.microsoft.com/support/supportnet/overview/overview.asp

STATUS

Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. This problem was first corrected in Windows NT 4.0 Service Pack 6.

MORE INFORMATION

To configure SNMP communities, use the SNMP Manager tool in Control Panel. To open SNMP Manager, in the Control Panel Network tool, click Services, and then click SNMP Services.

Additional query words:

Keywords : kbbug4.00 kbfix4.00
Version : winnt:4.0 SP4
Platform : winnt
Issue type : kbbug