Use of "&" Symbol in Server Names Causes Logon Scripts to Fail

 Last reviewed: August 8, 1997
Article ID: Q142691
The information in this article applies to:
  • Microsoft Windows NT Server versions 3.51 and 4.0
  • Microsoft Windows NT Workstation versions 3.51 and 4.0

SYMPTOMS

When you install a Domain Controller with the ampersand character (&) in the server name, Microsoft Windows NT clients cannot process logon scripts. You may see a command shell opened with an error message that the specified file was not found.

Additional symptoms include the inability to map network drives from a command prompt. For example, net view \\server&name will fail with the following errors: 

   System error 53 has occurred. The network path was not found.
-and- 

   The name specified is not recognized as an internal or external command,
   operable program or batch file.
If, however, you encapsulate the \\server&name in quotes, the command will process correctly.

CAUSE

The ampersand is a logical continuation operator within the Windows NT default command interpreter, Cmd.exe. This is why the second error message is generated in the above example of the net view \\server&name.

For example, type "notepad&write" or "notepad&wordpad" at a Cmd.exe shell under Windows NT, and Windows NT will open Notepad; when it closes, Windows NT will open Write or WordPad.

WORKAROUND

Rename the server to a name that does not contain special characters. 

Keywords          : ntdomain NTSrvWkst kbnetwork
Version           : WinNT:3.51,4.0
Platform          : winnt
Issue type        : kbprb
Solution Type     : kbworkaround

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

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.

Last reviewed: August 8, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.