Article ID: 811657 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
When a computer is multihomed or if multiple addresses are assigned to an interface, when you try to add a flow, the operation is unsuccessful. Also, SET_QOS does not return an error when the flow specification exceeds the interface capabilities.
This problem occurs if resource reservation protocol (RSVP) is not managing routing information correctly when the computer is multihomed or when multiple addresses are assigned to an interface. Also, RSVP is not propagating the error information between the service and the API correctly.
Service Pack InformationTo 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:
(http://support.microsoft.com/kb/260910/EN-US/ )How to Obtain the Latest Windows 2000 Service Pack
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.
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, submit a request to 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:
Date Time Version Size File Name ------------------------------------------------------------------- 10-Feb-2003 08:57 5.0.2195.6663 176,912 Rsvp.exe
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.
Article ID: 811657 - Last Review: February 27, 2014 - Revision: 2.5