- MSS file names are case sensitive. Turn off any file name
case mapping in your FTP Client.
-
The binary (or image) transfer format must be used for all
MSS file transfers. Set the correct file transfer type and
try again (see the section called “Selecting the Correct File Transfer Mode.”). For example:
ftp> get ftptest2
local: ftptest2 remote: ftptest2
200 PORT command ok.
504 TYPE A not supported for RETR.
ftp> bin
200 TYPE command ok.
ftp> get ftptest2
local: ftptest2 remote: ftptest2
200 PORT command ok.
125 Data connection open; transfer starting.
226 Binary Transfer complete.
359984 bytes received in 0.00298 secs (1.2e+05 Kbytes/sec)
-
The restart parameter is not supported for writes to
the MSS. Correct the problem and resend the entire
file again. for example:
ftp> put testfile9
local: testfile9 remote: testfile9
200 PORT command ok.
550 REST not supported for STOR.
ftp> restart 0
restarting at 0.
ftp> put testfile9
-
The read and/or write passwords are wrong or are set
when they should be empty. Correct the problem and try
again (see also the section called “Setting the Read Password” and
the section called “Setting the Write Password”. For example:
ftp> put testfile9
local: testfile9 remote: testfile9
200 PORT command ok.
550 write password mismatch
ftp> site wpwd
200 Command okay. Write password turned off.
ftp> put testfile9
-
Your FTP Client is running on a system outside the UCAR
security perimeter. You must use a TLS enabled FTP Client
and your FTP Client does not conform to the requirements
of RFC 4217.
If your FTP Client supports data connection protection,
turn it off (
PROT C).
See Chapter 7, Compatible TLS-enabled FTP Clients for some compatible FTP Clients.