The information in this article applies to:
SYMPTOMSPrograms using the Microsoft 32-bit DLC protocol may not be able to connect to the host over the network, especially when first starting up. CAUSEIf the client receives a large number of DLC packets in an extremely short period of time, the MSDLC32 protocol may be unable to dynamically allocate additional buffers quickly enough to successfully receive all incoming packets. RESOLUTIONThis issue is resolved by the following updated file for Windows 95 and OEM Service Release 2 (OSR2), and later versions of this file:
STATUS
Microsoft has confirmed this to be a problem in Microsoft Windows 95 and
OEM Service Release 2 (OSR2). An update to address this problem is now
available, but is not fully regression tested and should be applied only
to computers experiencing this specific problem. Unless you are severely
impacted by this specific problem, Microsoft does not recommend
implementing this update at this time. Contact Microsoft Technical Support
for additional information about the availability of this update.
MORE INFORMATION
When MSDLC32 initializes, it allocates a certain number of buffers
(specifically, Read CCB2 buffers) for incoming DLC packets. Over time, as
additional buffers are needed, they are allocated dynamically. In the
original release of MSDLC32, the initial number of Read CCB2 buffers
allocated is 16. In this update, that number is increased to 64. By
allocating more buffers initially, the buffers are available to be used
immediately, without the delay incurred with dynamic allocation.
Additional buffers are dynamically allocated later as needed.
Q161020 Implementing Windows 95 Updates Additional query words: attachmate 3270 sna
Keywords : kbnetwork kbpolicy win95 kbAPI kbDLC kbSDKPlatform kbGrpNet |
Last Reviewed: January 10, 2000 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |