Article ID: 906278 - Last Review: March 25, 2007 - Revision: 3.6 An external serial modem does not return to autoanswer mode and incoming connections do not succeed after you turn off and then turn on the modem in Windows Server 2003 SP1
On This PageSYMPTOMSOn a computer that is running Microsoft Windows Server 2003 with Service Pack 1 (SP 1), an external serial modem does not return to autoanswer mode after you turn off and then turn on the modem. Incoming connections do not succeed. Note This problem does not occur after you turn off and then turn on the computer. CAUSEThis problem occurs because of a race condition in the Windows Telephony API (TAPI). A race condition occurs when a resource is accessed by two or more threads at the same time. RESOLUTIONService pack informationTo 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:889100
(http://support.microsoft.com/kb/889100/
)
How to obtain the latest service pack for Windows Server 2003 Hotfix informationA 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, contact Microsoft Customer Service and Support to obtain the hotfix. 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. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support
(http://support.microsoft.com/contactus/?ws=support)
Note The "Hotfix download available" form displays 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.PrerequisitesTo apply this hotfix, you must have Windows Server 2003 Service Pack 1 (SP1) installed on the computer.Restart requirementYou must restart the computer after you apply this hotfix.Hotfix replacement informationThis hotfix does not replace any other hotfixes.File informationThe 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, 32-bit versionsCollapse this table
Windows Server 2003, Enterprise Edition for Itanium-based SystemsCollapse this table
Windows Server 2003, Enterprise Edition for x64-based SystemsCollapse this table
WORKAROUNDTo work around this problem, restart the Routing and Remote Access service. STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Server 2003 Service Pack 2. MORE INFORMATION For more information about the terminology that is used in this article, click the following article number to view the article in the Microsoft Knowledge Base: 824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updates APPLIES TO
| Article Translations
|
Back to the top
