D Strittmatter (Customer) asked a question.

August 26, 2026 at 6:16 PM
WS_FTP Professional connecting to WS_FTP Server using FTP shows wrong folder names

We have the Client software WS_FTP Professional 13.0.1 - Jun 23, 2026

We have WS_FTP Server 10.0.2

 

When connecting with FTP protocol the folder names are displayed wrong.

Example folder ABC

Shows as 01 2024 ABC

folder EFG

Shows as 05 2025 EFG

 

However when connecting by SFTP the folder names are displayed correct as

ABC

EFG

 

When the folder name is wrong you can not navigate by clicking on the folder.

 

This was verified using two different PCs running WS_FTP Professional client.

 

If we connect with other brand software clients the folders display correctly for both FTP and SFTP

 

What am I doing wrong or what setting do we need to change ?

  • 2 answers
  • 44 views

  • Deviprasad Madapala (Progress Software)

    @D Strittmatter (Customer)​ Hi, Based on the behavior described, this appears to be related to how the FTP directory listing format (LIST/MLSD) is being interpreted by the client. Since the folder names display correctly when using SFTP and with other FTP client applications, we would reqeust opening a Technical Support case for further investigation.

    Selected as Best

  • Deviprasad Madapala (Progress Software)

    @D Strittmatter (Customer)​ Hi, Based on the behavior described, this appears to be related to how the FTP directory listing format (LIST/MLSD) is being interpreted by the client. Since the folder names display correctly when using SFTP and with other FTP client applications, we would reqeust opening a Technical Support case for further investigation.

    Selected as Best

    • D Strittmatter (Customer)

      Well WS_FTP Professional is the client software. So it is your own client interacting with the server.

       

      Regardless, new iformation has come to light.

      The problem goes away if we use a different user account on the WS_FTP Server. So it would appear this particular user account is corrupt/mis-handled somehow within the WS_FTP Server implementation.

       

      We created a new client account to work around the issue. The old account still exists at this time.