The information in this article applies to:
SYMPTOMS
You may want to use the NETBIOS interface made available in SNARAS to
employ Microsoft networking over your existing SNA network, which consists
mainly of 9600 SDLC multidrop links. This would allow you to use Systems
Management Server remote control facilities and manage your computers
running Windows NT Server through the Windows NT Administrative Utilities
and the SNA Administrator UI.
At this point, you have the option to cancel or retry. If you click Retry, after about 5 seconds the following error message may appear:
CAUSE
The very low network bandwidth being used is insufficient to host the
complex protocols employed to achieve Microsoft networking. The low
bandwidth is further eroded as peer entities in all the protocol stacks
being used time out request and initiate their retransmission routines.
RESOLUTIONUpgrade slow links to links that can adequately handle NetBIOS/Server Message Block (SMB) traffic. MORE INFORMATIONWithin the SNARAS components connection timeouts can be seen by employing the checked versions of Snaras.dll and Rassna.dll to produce internal tracing, as demonstrated below: RASSNA.DLL internal tracing
SNARAS.DLL internal tracing
However, these failures occur as a result of an underlying network failure
which can be seen if RAS PPP logging is enabled. The logs will show PPP
packets get received a very long time after they are sent, causing PPP LCP
to come down and re-negotiate. So LCP goes up and down for a long time
until it disconnects. This is called a cross connection.
Although there are Microsoft Knowledge Base articles that describe how to
tune timing parameters in the network protocols right up to SMB layer,
Microsoft network architecture is not designed to work over networks
offering such low bandwidth.
STATUSAdditional query words: prodsna
Keywords : kbnetwork kbbug2.00 kbbug2.10 kbbug2.11 snaras |
Last Reviewed: November 16, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |