SYMPTOMS
When you use Serial Line Internet Protocol (SLIP) functionality to connect to a server after you are already connected to another server by using SLIP in another dial-up networking connection, you may receive an error message that is similar to the following:
Error 31
As a result, you cannot establish a connection to the second server by using SLIP.
RESOLUTION
Hotfix Information
Windows Server 2003
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Windows Server 2003 that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. 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 usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.PrerequisitesThis hotfix requires either Windows Server 2003 or Windows 2000 Service Pack 4 (SP4).Hotfix Replacement Information This hotfix does not replace any
other hotfixes.File Information 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
------------------------------------------------------
31-Jul-2003 16:33 5.2.3790.73 167,936 Rasmans.dll
Windows 2000
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.
To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. 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 usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.PrerequisitesThis hotfix requires either Windows Server 2003 or Windows 2000 Service Pack 4 (SP4).Hotfix Replacement Information This hotfix does not replace any
other hotfixes.File Information 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
--------------------------------------------------------
28-Jul-2003 21:29 5.0.2195.6738 417,552 Oakley.dll
28-Jul-2003 21:29 5.0.2195.6738 58,128 Rasman.dll
28-Jul-2003 21:29 5.0.2195.6794 153,872 Rasmans.dll
28-Jul-2003 21:29 5.0.2195.6738 54,032 Rastapi.dll