File Copy to Macintosh Volume Takes Time (235543)


The information in this article applies to:

  • Microsoft Windows NT Server 4.0 Terminal Server Edition
  • Microsoft Windows NT Server 4.0
  • Microsoft Windows NT Server 4.0 SP3
  • Microsoft Windows NT Server 4.0 SP4
  • Microsoft Windows NT Server 4.0 SP5
This article was previously published under Q235543

SYMPTOMS

When files are copied to a Macintosh volume, the changes do not appear on a Macintosh client immediately. For the files to appear on the Macintosh client directory, you must wait approximately five seconds, and then refresh the Macintosh Finder. If a file is copied to a Macintosh volume on a Windows NT 4.0 server and is then immediately renamed, Services for Macintosh (SFM) does not update the index and the Macintosh client cannot see the files until the index is rebuilt.

NOTE: The SFM volume index is automatically rebuilt when SFM is started or restarted with Windows NT 4.0 SP4 or later. For additional information and troubleshooting information about SFM and volume indexing, please click the article numbers below to view the articles in the Microsoft Knowledge Base:

185722SFM Rebuilds Indexes upon Restarting of Windows NT

164138Files in Macintosh Volume Disappear from Macintosh Clients

147909Troubleshooting MacVolume Creation Errors

CAUSE

SFM does not update the volume indices if files are renamed immediately after being written to the volume.

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:

http://support.microsoft.com/directory/overview.asp


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 and Windows NT Server 4.0, Terminal Server Edition.

This problem was first corrected in Windows NT Server 4.0 Service Pack 6 and Windows NT Server 4.0, Terminal Server Edition Service Pack 6.
Modification Type:MinorLast Reviewed:9/23/2005
Keywords:kbHotfixServer kbQFE kbbug kbfix kbQFE KB235543
©2004 Microsoft Corporation. All rights reserved.