Article ID: 328089
Article Last Modified on 10/26/2006
APPLIES TO
- Microsoft Windows 2000 Advanced Server
- Microsoft Windows 2000 Advanced Server
- Microsoft Windows 2000 Advanced Server
- Microsoft Windows 2000 Service Pack 3
- Microsoft Windows 2000 Service Pack 2
- Microsoft Windows 2000 Service Pack 1
- Microsoft Windows 2000 Service Pack 3
- Microsoft Windows 2000 Service Pack 2
- Microsoft Windows 2000 Service Pack 1
- Microsoft Windows 2000 Professional Edition
- Microsoft Windows 2000 Server
- Microsoft Windows 2000 Advanced Server
This article was previously published under Q328089
SYMPTOMS
You may create a dial-up connection by doing the following in the Connection name Properties dialog box:
- You click the General tab, and then you click to select the check boxes of multiple modems in the Connect using list.
- You click the Options tab, and then you click Dial only first available device in the Multiple devices list.
However, when you try to create a remote access connection, and the telephone number that you dial is busy or does not answer, the dial-up connection continues to use the other modems to try to establish the connection.
You do not expect the dial-up connection to retry the number by using the other devices because you configured it to dial by using only the first available device.
CAUSE
This problem occurs when the remote access service dials the first entry in the modem list but experiences an error, such as a busy signal, before it connects (before it reaches the RASCS_DeviceConnected state). In this case, the service tries the next device in the list of selected modems.
RESOLUTION
Service Pack Information
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
Hotfix Information
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Windows 2000 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this fix has the file attributes (or later) 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.
Date Time Version Size File name ----------------------------------------------------------- 25-Sep-2002 22:32 5.0.2195.6034 194,832 Rasapi32.dll 25-Sep-2002 22:32 5.0.2195.6034 58,128 Rasman.dll 25-Sep-2002 22:32 5.0.2195.6050 152,848 Rasmans.dll 25-Sep-2002 22:32 5.0.2195.6034 54,032 Rastapi.dll 13-Jun-2001 05:05 5.0.2195.3727 3,856 Svcpack1.dll
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.
MORE INFORMATION
For additional information about how to obtain a hotfix for Windows 2000 Datacenter Server, click the article number below to view the article in the Microsoft Knowledge Base:
265173 The Datacenter Program and Windows 2000 Datacenter Server Product
Keywords: kbbug kbfix kbwin2000presp4fix kbqfe kbwin2ksp4fix kbhotfixserver KB328089
