Submit a ticketCall us

WebinarUpcoming Webinar: Should I Move My Database to the Cloud?

So you’ve been running an on-premises SQL Server® for a while now. Maybe you’ve moved it from bare metal to a VM, and have seen some positive benefits. But, do you want to see more? If you said “YES!”, then this session is for you, as James Serra will review the many benefits that can be gained by moving your on-prem SQL Server to an Azure® VM (IaaS). He’ll also talk about the many hybrid approaches, so you can gradually move to the cloud. If you are interested in cost savings, additional features, ease of use, quick scaling, improved reliability, and ending the days of upgrading hardware, this is the session for you.

Register now.

Home > Success Center > Serv-U Managed File Transfer & Serv-U FTP Server > Serv-U - Knowledgebase Articles > 553 FTP response code

553 FTP response code

Updated May 3, 2017

Overview

This article provides information on 553 FTP response code.

Environment

All Serv-U versions

Detail

A 553 response code may be given in response to any command requiring or supporting the use of a file name as a parameter. It is a permanent negative reply, which means the client is discouraged from sending the command again since the server will respond with the same reply code. It is usually due to the file name contained as a parameter violating the file naming policies existing on the server. Issuing the command again with a different file name may result in a different reply code.

Example response

553 Requested action not taken; File name not allowed.

Possible commands

 

Last modified

Tags

Classifications

Public