Microsoft KB Archive/184229

= Copying Files to a Macintosh Volume Changes Date and Time Stamp =

Article ID: 184229

Article Last Modified on 11/1/2006

-

APPLIES TO


 * Microsoft Windows NT Server 4.0, Terminal Server Edition
 * Microsoft Windows NT Server 3.51
 * Microsoft Windows NT Server 4.0 Standard Edition

-



This article was previously published under Q184229



SYMPTOMS
When you copy a file from a computer running Windows NT 3.51 or 4.0 to a Macintosh accessible volume that is also shared for Windows networking clients, the file's modified date and time stamp may change to the current date and time on the server.



Windows NT 3.51
To resolve this problem, contact Microsoft Technical Support to obtain the following fix.

This fix should have the following time stamp:

  12/02/97  02:26p               337,696 Kernel32.dll (Intel) 12/02/97 02:24p               525,072 Kernel32.dll (Alpha)

Windows NT 4.0
To resolve this problem, obtain the latest service pack for Windows NT 4.0 or 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 this to be a problem in Windows NT version 3.51. A supported fix is now available, but has not been fully regression tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next service pack that contains this fix. Contact Microsoft Technical Support for more information.

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

Additional query words: mac sfm

Keywords: kbhotfixserver kbqfe kbbug kbfix KB184229

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.