We has this problem that happens from time to time, and if anyone has had a similiar any information or help would be helpful.
The problem is with ftp, everything will be fine, no one will have made any changes. Then you will be able to ftp out to an external site, login and use cmds that reply back on port 21. However if you use a cmd that replies on port 20, we receive connection closed by remote host.
We are seeing the sesssion run through the correct rule, and there are no drops or reject associated to the session.
any ideas.
The problem is with ftp, everything will be fine, no one will have made any changes. Then you will be able to ftp out to an external site, login and use cmds that reply back on port 21. However if you use a cmd that replies on port 20, we receive connection closed by remote host.
We are seeing the sesssion run through the correct rule, and there are no drops or reject associated to the session.
any ideas.