I encountered this same problem this morning.
However, in my case, the cause turned out to be a dead virtual-directory mapping that was attempting to over-ride a local folder that contained data.
This event occurred due to the fact that my NAS lost a drive yesterday, and last evening, I evacuated all of the recoverable data from my NAS to my much older file server, where I host G6FTPd integrated with Active Directory. Fortunately, I had anticipated the need to remove the old mappings from the group-profiles I had created much earlier.
Once the dead VDIR mappings were removed from the groups, I simply refreshed my connection and was able to proceed with the MLSD command and get a successful directory listing.
Sometimes, you just have to hack around at the problem to find the right answer.
However, in my case, the cause turned out to be a dead virtual-directory mapping that was attempting to over-ride a local folder that contained data.
This event occurred due to the fact that my NAS lost a drive yesterday, and last evening, I evacuated all of the recoverable data from my NAS to my much older file server, where I host G6FTPd integrated with Active Directory. Fortunately, I had anticipated the need to remove the old mappings from the group-profiles I had created much earlier.
Once the dead VDIR mappings were removed from the groups, I simply refreshed my connection and was able to proceed with the MLSD command and get a successful directory listing.
Sometimes, you just have to hack around at the problem to find the right answer.