Article ID: 235543 - Last Review: November 1, 2006 - Revision: 1.5 File Copy to Macintosh Volume Takes TimeThis article was previously published under Q235543 On This PageSYMPTOMS
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: 185722
(http://support.microsoft.com/kb/185722/EN-US/
)
SFM Rebuilds Indexes upon Restarting of Windows NT
164138
(http://support.microsoft.com/kb/164138/EN-US/
)
Files in Macintosh Volume Disappear from Macintosh Clients
147909
(http://support.microsoft.com/kb/147909/EN-US/
)
Troubleshooting MacVolume Creation Errors
CAUSE
SFM does not update the volume indices if files are renamed immediately after being written to the volume.
RESOLUTIONWindows NT Server or Workstation 4.0To 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:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS
(http://support.microsoft.com/default.aspx?scid=fh;en-us;cntactms)
Windows NT Server 4.0, Terminal Server EditionTo 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
(http://support.microsoft.com/kb/152734/EN-US/
)
How to Obtain the Latest Windows NT 4.0 Service Pack
STATUSMicrosoft 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. | Article Translations
|
Back to the top
