LFNs Do Not Display Correctly Using FTP with Internet Explorer (136471)



The information in this article applies to:

  • Microsoft Internet Explorer 5.0 for Windows NT 4.0
  • Microsoft Internet Explorer 4.01 for Windows NT 4.0 SP 1
  • Microsoft Internet Explorer 3.02 for Windows NT 4.0
  • Microsoft Internet Explorer 3.01 for Windows NT 4.0
  • Microsoft Internet Explorer 3.0 for Windows NT 4.0
  • Microsoft Internet Explorer 5.0 for Windows 95
  • Microsoft Internet Explorer 4.01 for Windows 95 SP 1
  • Microsoft Internet Explorer 4.0 for Windows 95
  • Microsoft Internet Explorer 3.02 for Windows 95
  • Microsoft Internet Explorer 3.01 for Windows 95
  • Microsoft Internet Explorer 3.0 for Windows 95
  • Microsoft Internet Explorer 4.0 for Windows 98
  • Microsoft Internet Explorer 4.01 for Windows 98
  • Microsoft Internet Explorer 5.0 for Windows 98
  • Microsoft Internet Explorer 5.01 for Windows 98
  • Microsoft Internet Explorer 2.0 for Windows 3.1
  • Microsoft Internet Explorer 2.01 for Windows 3.1
  • Microsoft Internet Explorer 2.1 for Windows 3.1
  • Microsoft Internet Explorer 3.0 for Windows 3.1
  • Microsoft Internet Explorer 3.01 for Windows 3.1
  • Microsoft Internet Explorer 3.03 for Windows 3.1
  • Microsoft Internet Explorer 4.0 for Windows 3.1
  • Microsoft Internet Explorer 4.01 for Windows 3.1
  • Microsoft Internet Explorer 4.5 for Windows 3.1
  • Microsoft Internet Explorer 5.0 for Windows 3.1
  • Microsoft Internet Explorer 3.02a for Windows 3.1

This article was previously published under Q136471

SYMPTOMS

When you use Microsoft Internet Explorer to view files on a File Transfer Protocol (FTP) site, filenames containing spaces do not display correctly, and cannot be retrieved.

CAUSE

Internet Explorer does not parse the file list properly using FTP, and cannot display long filenames (LFNs) that contain spaces.

RESOLUTION

Use the Ftp.exe tool that is included with Windows 95 or another FTP software program with Windows 3.1 to view and retrieve these files.

STATUS

Microsoft has confirmed this to be a problem in the products listed at the beginning of this article. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Modification Type:MajorLast Reviewed:12/5/2003
Keywords:KB136471