Microsoft NT 4 Security Patch Flawed

Microsoft on Tuesday acknowledged problems with a Windows NT 4.0 security patch that was first released on June 23.

Users running Windows NT 4.0 Server with the Routing and Remote Access Service (RRAS) enabled reported problems after installing patch MS03-029. Apparently after installing the patch and rebooting, RRAS would fail.

"It does not affect other non-RRAS functions, nor is there a problem with the actual fix for the security vulnerability itself," Microsoft wrote in an explanation now included in the security bulletin.

Customers who are directly affected can contact Microsoft Product Support Services for a hotfix, but the fixed patch won't be publicly released until Microsoft has tested it more thoroughly, the company said.

The occasion for the original patch was a denial-of-service vulnerability in a Windows NT 4.0 file management function. Microsoft originally gave the problem a "moderate" severity rating.

The security bulletin explaining the security vulnerability and the problems with the patch can be found here:

About the Author

Scott Bekker is editor in chief of Redmond Channel Partner magazine.


  • Azure Backup for SQL Server Now Commercially Available

    Microsoft on Monday announced that Azure Backup for SQL Server had reached "general availability" status, meaning it's deemed ready for production-environment use.

  • Insights for MyAnalytics Getting Switched On for Office 365 Users This Month

    Microsoft is planning to activate "Insights for MyAnalytics" sometime late this month for most Office 365 users, but the ability of organizations to manage this feature won't be available until possibly mid-May.

  • SharePoint Framework 1.8 Now Generally Available

    Microsoft this week announced that SharePoint Framework 1.8 had reached "general availability" status, although some features are still at the preview stage.

  • How To Create Office 365 User Accounts in Bulk

    Manual account creation can be tedious, time-consuming and prone to human error, especially if you have more than a handful of Office 365 users to set up. Brien shows you a better way.

comments powered by Disqus

Office 365 Watch

Sign up for our newsletter.

Terms and Privacy Policy consent

I agree to this site's Privacy Policy.