DLC connections fail to restart after outage (247353)
The information in this article applies to:
- Microsoft SNA Server 2.11 SP1
- Microsoft SNA Server 2.11 SP2
- Microsoft SNA Server 3.0 SP1
- Microsoft SNA Server 3.0 SP2
- Microsoft SNA Server 3.0 SP3
- Microsoft SNA Server 3.0 SP4
- Microsoft SNA Server 4.0
- Microsoft SNA Server 4.0 SP1
- Microsoft SNA Server 4.0 SP2
- Microsoft SNA Server 4.0 SP3
- Microsoft SNA Server 4.0 SP4
- Microsoft Host Integration Server 2000
- Microsoft Host Integration Server 2000 SP1
This article was previously published under Q247353 SYMPTOMS
If a network problem causes an SNA Server DLC 802.2 connection to fail (causing event ID 23 to be logged by SNA Server), the connection should automatically recover to an "Active" state after the problems are gone. However, under certain conditions, the connection may not recover, and the status may stay at "Pending" when you use one of the following token ring adapters:
IBM 16/4 Token-Ring PCI Adapter 2IBM 16/4 Token-Ring PCI AdapterCompaq Netelligent Token-Ring AdapterCompaq Netflex Token-Ring Adapter CAUSE
This problem is caused by the IBM token ring driver Ibmtrp.sys, dated 11/4/96 (version 1.08). This problem is described on the IBM Web site; for information, go to the following location:
The Ibmtrp.sys driver is used for the following network adapters: IBM 16/4 Token-Ring PCI Adapter 2IBM 16/4 Token-Ring PCI AdapterCompaq Netelligent Token-Ring Adapter Microsoft is not aware of a fix for the Compaq Netflex Token-Ring Adapter, which uses a different driver.
Note that Microsoft is not able to confirm that a switch is failing when this problem occurs. The DLC connections drop (indicated by the SNA Server Event 23 Outage xAF errors), and at the time of the
failures, network errors are occurring (Token Ring soft errors). Updating the driver allows the connections to recover after an outage.
RESOLUTION
Update the token ring driver (Ibmtrp.sys) to version 2.22, dated 7/21/97 or later.
STATUS
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.
Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
MORE INFORMATION
The outage that initiated the problem is logged in the Application event log as event ID 23 with an outage code of 0xAF. This event is almost always an indicator of a network problem.
The token ring re-insertion problem is not specific to DLC connectivity. In a lab environment, the problem was recreated with the PING utility over IP.
| Modification Type: | Major | Last Reviewed: | 8/17/2004 |
|---|
| Keywords: | kbprb KB247353 |
|---|
|