Unable to View Macintosh Client Created Directories

This article was previously published under Q140066
This article has been archived. It is offered "as is" and will no longer be updated.
Directories or files on a Windows NT Server Macintosh volume, may not beaccessible by Windows or Windows 95. You may get the error "The folder[directory] does not exist". Windows NT clients will be able to read thefiles.

Directories or files on a Windows NT Server Macintosh volume, may not beaccessible by Windows or Windows 95. The following error message arepresented when Windows 95 clients attempt to copy over or open the file:

Error copying file
Cannot copy <filename> : Cannot find the specified file.
Make sure you specify the correct path and filename

Or you may get the error "The folder [directory] does not exist". WindowsNT clients will be able to read the files.

Macintosh computers can use many characters for filenames that are illegalfor x86-based clients, such as * / \ < > ? and |. These are also invalidNTFS characters. Such a file cannot be accessed by a Unicode unawareapplication. When a Macintosh client creates a filename on an SFMvolume, it is converted from Macintosh ANSI to Unicode by SFM before beingpassed to NTFS. Because SFM does the conversion, it can define Unicodevalues that invalid NTFS characters will map to. It does so by using thePrivate Use Area range of the Unicode standard.

For example:

If you save a file from a Macintosh to a Windows NT server with the filename "After 5/12/95.", the Windows NT computer shows this file as "After5|12|95|" and a Windows 95 client shows this file as "After 5_12_95_."

Since Windows and Windows 95 do not support Unicode, Macintosh file nameswhich map to illegal file name characters will result in filenames whichcannot be used to open these files.

The only workaround is to rename the files. A shareware Macintosh programcalled Drop*Rename will allow you to search on illegal PC characters andrename them automatically. It can be found on
prodnt 3.1 3.5

Article ID: 140066 - Last Review: 02/28/2014 07:59:12 - Revision: 2.1

Microsoft Windows 2000 Server, Microsoft Windows 2000 Advanced Server, Microsoft Windows NT Advanced Server 3.1, Microsoft Windows NT Server 3.5, Microsoft Windows NT Server 3.51, Microsoft Windows NT Server 4.0 Standard Edition, Microsoft Windows NT 4.0 Service Pack 4

  • kbnosurvey kbarchive kbnetwork KB140066