KnowledgeBase Archive

An Archive of Early Microsoft KnowledgeBase Articles

View on GitHub

Q258443: Cluster Spooler Reports Node Name Instead of Virtual Name

Article: Q258443
Product(s): Microsoft Windows NT
Version(s): 4.0; winnt:1.1
Operating System(s): 
Keyword(s): kbprint
Last Modified: 07-SEP-2001

-------------------------------------------------------------------------------
The information in this article applies to:

- Microsoft Windows NT Server, Enterprise Edition version 4.0 
- Microsoft Cluster Server, version 1.1 
-------------------------------------------------------------------------------

SYMPTOMS
========

When you use Windows NT 4.0 Enterprise Edition with Microsoft Cluster Server
(MSCS) and you receive a print spooler notification, the notification reports
the node name of the print server instead of the virtual name.

CAUSE
=====

MSCS registers clustered printers with the local Spooler service. Because
notification is the responsibility of the Spooler service, this behavior occurs.

STATUS
======

Microsoft has confirmed that this is a problem in Microsoft Windows NT Server
Enterprise Edition version 4.0.

Additional query words:

======================================================================
Keywords          : kbprint 
Technology        : kbWinNTsearch kbWinNT400search kbWinNTSsearch kbWinNTSEntSearch kbWinNTSEnt400 kbWinNTS400search kbAudDeveloper kbClustServSearch kbClustServ110
Version           : :4.0; winnt:1.1
Issue type        : kbbug
Solution Type     : kbpending

=============================================================================

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.