Quote:
Originally Posted by Weaver  Guess this answer is a little to late, anyhow, this behaviour is caused by SmartDefense. Also for example an "mkdir test227" will result in a new dir "test22_".
Smartdefense changest the string and reports a possible "FTP Bounce attack". I'm not sure but I think it doesn't look _where_ the 227 appears, but it interprets it as the 227 code for entering passive mode. Not very smart imho.
The only way I found to fix it is to make a new service, tcp port 21 with no application defined, which implies that also no other ftp checks will work. Does anyone have a better workaround? |
Ok, thank you, now I at least know what's the causing that problem. Unfortunately I cannot create blank FTP service, firewall configuration is too complicated and that would surely break something else in FTP transfers.
I found another forum where the same problem was described:
IT Resource Center forums - strange FTP behaviour through firewall Replacing 227 with 22_ everywhere sounds more like DumbDefense.