The information in this article applies to:
SYMPTOMSIf an SNA Client system does not receive a Host data stream after successful session initialization, a problem with pacing may have occurred between the Host and the SNA Server. Users will not receive data from the Host, even though the session is still active in SNA Manager. CAUSE
When a host sends a pacing indicator (Byte 2 of the RH set to 81) in an FMI
message, SNA Server changes it to a value of 80 (no pacing). The Host is
then unable to send the data because it has not received a pacing response.
RESOLUTIONSnaservr.exe has been modified so that pacing is not disabled. STATUSMicrosoft has confirmed this to be a problem in SNA Server 3.0 and 3.0 Service Pack 1 (SP1). This problem was corrected in the latest SNA Server version 3.0 U.S. Service Pack. For information on obtaining this Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces): S E R V P A C K Additional query words:
Keywords : kbnetwork prodsna kbbug3.00 snaprog kbbug3.00.sp1 snaeis snaserverservice kbfix3.00.sp2 |
Last Reviewed: December 3, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |