An Attack on Port 1720 May Cause NetMeeting to Refuse Incoming Connections

This article was previously published under Q315092
This article has been archived. It is offered "as is" and will no longer be updated.
SYMPTOMS
An attack on port 1720 may cause NetMeeting to refuse incoming connections after more than approximately 200 Transmission Control Protocol (TCP) connections are opened. If you apply the fix that is mentioned in the following Microsoft Knowledge Base article, this problem is not resolved:
273854 MS00-077: Denial of Service Can Occur with Microsoft NetMeeting
CAUSE
This problem occurs because of the way that NetMeeting handles TCP connections in the Callcont.dll dynamic link library.
RESOLUTION
To resolve this problem, obtain the latest service pack for Microsoft Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft Windows 2000 Service Pack 4.
kbSecurity kbAppCompat
Properties

Article ID: 315092 - Last Review: 10/24/2013 09:08:25 - Revision: 3.3

Microsoft NetMeeting 3.01 Standard Edition, Microsoft NetMeeting 3.01 Standard Edition, Microsoft NetMeeting 3.01 Standard Edition, Microsoft NetMeeting 3.01 Standard Edition, Microsoft NetMeeting 3.01 Standard Edition, Microsoft NetMeeting 3.01 Standard Edition

  • kbnosurvey kbarchive kbwin2ksp4fix kbappcompatibility kbbug kbenv kbfix kbsecurity KB315092
Feedback
ERROR: at System.Diagnostics.Process.Kill() at Microsoft.Support.SEOInfrastructureService.PhantomJS.PhantomJSRunner.WaitForExit(Process process, Int32 waitTime, StringBuilder dataBuilder, Boolean isTotalProcessTimeout)