FTP Clients Cannot Rename Files on Remote FTP Virtual Directory

ID: Q240253


The information in this article applies to:
  • Microsoft Internet Information Server version 4.0
  • Microsoft Commercial Internet System version 2.5


SYMPTOMS

When you map a virtual directory to a UNC path and allow Anonymous Access, you may be able to PUT a file to the FTP site, but the GET command fails.


CAUSE

When handling a PUT command, FTP uses the credentials configured in the virtual directory configuration dialog. The GET command uses the credentials of the user who is logged on. The result is that you can send and delete the file to or on the FTP server, but cannot get it back.


WORKAROUND

On the UNC path that the virtual directory is mapped to, grant the correct permissions to the Windows NT account used for Anonymous Access.


RESOLUTION

A supported fix that corrects this problem is now available from Microsoft, but it has not been fully regression tested and should be applied only to systems experiencing this specific problem. If you are not severely affected by this specific problem, Microsoft recommends that you wait for the next Windows NT service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. 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://www.microsoft.com/support/supportnet/overview/overview.asp
The English version of this fix should have the following file attributes or later:

   Version      Size    File name     Platform
   --------------------------------------------
   8.0.351.0    85264   Ftpsvc2.dll   (x86)
   8.0.351.0   150288   Ftpsvc2.dll   (alpha) 


STATUS

Microsoft has confirmed this to be a problem in Internet Information Server 4.0.

Additional query words: MCIS hotfix hot fix qfe quick engineering patch

Keywords :
Version : winnt:2.5,4.0
Platform : winnt
Issue type : kbbug


Last Reviewed: September 23, 1999
© 2000 Microsoft Corporation. All rights reserved. Terms of Use.