Use of "&" Symbol in Server Names Causes Logon Scripts to Fail (142691)
The information in this article applies to:
- Microsoft Windows 2000 Server
- Microsoft Windows 2000 Advanced Server
- Microsoft Windows 2000 Professional
- Microsoft Windows NT Server 3.51
- Microsoft Windows NT Server 4.0
- Microsoft Windows NT Workstation 3.51
- Microsoft Windows NT Workstation 4.0
This article was previously published under Q142691
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.
| Modification Type: | Major | Last Reviewed: | 5/7/2003 |
|---|
| Keywords: | kbnetwork kbprb KB142691 |
|---|
|