FTP error on site commands as400 to as400 transfer
I disribute files between a number of AS400's. As part of the procedure I send a remote command to restore the files. The remote command stopped working. The time difference between the two transfers (successful and not) was 2 hours and in the middle of a busy work day. No changes were made to operating systems of firewalls.
This is the error message:
505 Security server forbids SITE commands. Contact admin.
this is received immediately after log on
Software/Hardware used:
Software/Hardware used:
ASKED:
December 8, 2005 9:22 AM
UPDATED:
November 21, 2009 9:40 AM
Answer Wiki:
1 - Did it fail on ALL of the 400's or just some?
If it failed on 'ALL' then the change was at your end - authentication (you did say right after login).
If it only failed on some systems, then they changed. Patch or Antivirus or malware blocker, or updated ACL.
Good luck.
============================================================
You might manage the AS/400s, but you apparently don't manage the network. The message isn't coming from one of your as/400s; it's coming from a firewall. See the <a href="https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=10022.0.2917673.2504701">Forcing the File Transfer Protocol (FTP) Security Server to allow unsafe commands from the client</a> document from Check Point for instructions on how to handle the situation.
Note that "handling" it might not be possible. It makes good sense not to allow your technique to work over FTP. Use a better method of applying updates.
Tom
To see all answers submitted to the Answer Wiki: View Answer History.
It has failed on 2 of my systems one a few months ago and the other two weeks ago.
I manage both networks and am the only one to apply changes – there were none.
I even detached firewalls to check the problem – and it still exists.
Do you need to use the SITE command to initiate the job on the remote AS/400? I’ve always used the QUOTE RCMD sbmjob() to get something going on the remote site, and never had a problem with it.