Clients Cannot Connect to Printer Server's Optional Name

Last reviewed: June 10, 1998
Article ID: Q187332

The information in this article applies to:

Microsoft Windows NT Workstation version 4.0
Microsoft Windows NT Server version 4.0

SYMPTOMS

When trying to connect to the OptionalNames parameter of a print server, the Windows NT client's Printer Wizard returns the following error:

   Could not connect to printer: The printer name is invalid.

CAUSE

When setting up the print server and shares, name checking did not take OptionalNames into account and returned invalid name because it differed from the local server name.

RESOLUTION

To work around this problem, on the client side, run a the following command

   net use lptx:

where x is the local lpt port to connect to the print server from a console window.

STATUS

Microsoft has confirmed this to be a problem in Windows NT version 4.0. We are researching this problem and will post additional information here in the Microsoft Knowledge Base as it becomes available.

Additional query words: spooler, localspl
Keywords : kbbug4.00
Version : WinNT:4.0
Platform : winnt
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.