Incoming X.25 Host Connection Indicates Primary Link Role

• Microsoft SNA Server, versions 3.0, 3.0SP1, 3.0SP2, 4.0

SYMPTOMS

When an SNA Server X.25 connection is configured for Remote End: Host and Allowed Directions is configured for Incoming or Both Directions, the SNA Server notifies the X.25 link service that it has a primary link role when it should have indicated a secondary link role.

The incorrect X.25 link role is reported to the X.25 link service in the SNA Server's Open(Link) request. This problem was found by Eicon Technology, though may occur with any X.25 link service supported by SNA Server.

CAUSE

The SNA Server configuration DLL (SNACFG.DLL) was incorrectly defaulting the X.25 link role when the X.25 connection is configured to support incoming calls. This caused the SNA Server to indicate a primary link role in error.

STATUS

Microsoft has confirmed this to be a problem in SNA Server versions 3.0, 3.0 Service Pack 1 (SP1), 3.0 SP2, and 4.0.

A supported fix is now available for SNA 3.0 and 4.0, but has not been fully regression-tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Product Support Services for more information.

MORE INFORMATION

The SnaBase service must be stopped in order to apply the updated SNA Server configuration DLL (<snaroot>\system\SNACFG.DLL). Once the updated SNACFG.DLL is applied, the SNA Server Manager program must be run and the configuration file must be resaved.

Keywords          : kbbug3.00 kbbug3.00.sp1 prodsna snaserverservice snax25 kbbug3.00.sp2 kbbug4.00
Version           : WINDOWS:3.0,3.0SP1,3.0SP2,4.0
Platform          : WINDOWS
Issue type        : kbbug
Solution Type     : kbfix