Some Share Names May Not Work Correctly (225255)



The information in this article applies to:

  • Microsoft Windows NT Server, Enterprise Edition 4.0, when used with:
    • Microsoft Cluster Server
  • Microsoft Windows NT Server 4.0
  • Microsoft Windows NT Workstation 4.0

This article was previously published under Q225255

SYMPTOMS

If you use one of the following names as a share name, some API operations on this share will fail:

M, MA, MAI, MAIL, MAILS, MAILSL, MAILSLO, MAILSLOT

While MAILSLOT is a reserved name, the other share names are legal regardless of case.

A known API call is FindFirstFile(). It may fail with an error 1 "Incorrect function". Unfortunately, Microsoft Cluster Server uses this API call to verify if the share name is alive.

CAUSE

The share name was compared against the string "MAILSLOT" and found identical, even if the share name was shorther than eight characters.

RESOLUTION

Windows NT Server or Workstation 4.0

To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual software update. For information on obtaining the latest service pack, please go to:
For information on obtaining the individual software update, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

Windows NT Server 4.0, Terminal Server Edition

To resolve this problem, obtain the latest service pack for Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

152734 How to Obtain the Latest Windows NT 4.0 Service Pack


STATUS

Microsoft has confirmed that this is a problem in Windows NT 4.0. This problem was first corrected in Windows NT Server version 4.0 Service Pack 6.

Modification Type:MinorLast Reviewed:9/23/2005
Keywords:kbHotfixServer kbQFE kbbug kbfix kbQFE KB225255