When is an Error, Not An Error - Looking at Cisco's FTP client
I believe it is important for analysts to spend time on paying attention with tool or application behavior.
Picture this; something doesn’t work as expected and I look to my client and they shrug their shoulders. I ask them, “What do you do now?” They respond, ”reboot or reset”. When that doesn’t work, they start pulling on the infamous network straws to see what they can try next.
This is where I ask if I can take a few minutes to investigate and understand the problem rather than randomly guessing. In most cases, there is typically an answer to the problem, we fix, we learn and we move on.
In this article I am covering how Cisco IOS reports FTP issues. Specifically in this situation the FTP server we are trying to copy from, did not have the proper permission to download a file to the switch. When this failed the first time, we both suspected that the account was misconfigured. My client manually logged into the ftp server and successfully performed a directory or listing. At that point we were a bit confused. Why wasn’t it working?
I thought I would try to reproduce the issue and used Quick ‘n Easy Ftp Server Lite as my ftp server since it is a portable app that I can run from a flash drive. Fortunately for me I forgot to assign any permissions to my test account and got the exact same error.
I took a trace and noticed the FTP error code 550 or permission error. Funny thing, the Cisco switch only reported that the file or directory was missing? As soon as I gave the account the proper permission the copy to the switch worked.
Some may think the morale of the story is a specific issue with Cisco, but many other ftp clients have similar reporting issues.
...
https://www.youtube.com/watch?v=ABt9qZYg4JA