Microsoft KB Archive/90176

= Printing Problems with XNSNB =

Article ID: 90176

Article Last Modified on 9/30/2003

-

APPLIES TO


 * Microsoft LAN Manager 2.1 Standard Edition

-



This article was previously published under Q90176



SYMPTOMS
If you are connecting to a printer share using the XNSNB protocol,you may experience problems when you attempt to print from MS-DOS applications such as Harvard Graphics, FoxPro, and MS-DOS PRINT. Usually printing from these applications will cause the workstation to enter a perpetual beeping state. If this happens, you will need to reboot to get out of this state. On the server, either a print job of zero length or no print job at all will appear in the queue.



CAUSE
XNSNB was developed by 3Com Corporation. 3Com has determined that there is a problem in XNSNB with the way that it chains the timer interrupt.



RESOLUTION
Change the order that the workstation service and XNSNB are loaded. In a default configuration, this means changing the following lines in the AUTOEXEC.BAT file from:

NET START WORKSTATION LOAD XNSNB

to:

LOAD XNSNB NET START WORKSTATION

The result is that the LAN Manager workstation service will appear in the interrupt chain before XNSNB, avoiding the chaining problem in XNSNB entirely. Unfortunately, this results in the inability to unload and reload XNSNB dynamically.



STATUS
3Com Corporation has confirmed this to be a problem in XNSNB 2.0 that is shipped in the Microsoft Upgrade Toolkit for 3Com Networks version 2.0. They are currently researching this problem. We will post new information here as it becomes available.

Additional query words: 2.1 2.10 xns 3station 3server netbios

Keywords: KB90176

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.