FTP Files Problem

[#1]

I' m having a weird problem with FTP. If I send a file using a client like Filezilla it will send the file over to an FTP server without a problem. However if I send the file over via windows command line ftp it will send the file short some bits. Example if I send putty.exe 454,656 filesize ... when it' s done sending to the ftp server I will have a file with the size of 453,598 on the server. Something is shaving my files off when I send by command line. The files are not getting logged a viruses. Any thoughts?

[abelio]

It smells like a cache somewhere giving a broken version file of putty.exe.. Not FTG because Filezilla use the same firewall policy and transfer ok. Verify checksum of putty.exe file to confirm the broken binary.

[#3]

I' ve confirmed this problem with several different file with the same result as the example. Weird huh?

[#4]

Sorry, I picked this up a bit late. I think you problem here may be caused by your use of the Windows FTP client not the FortiGate. By default, it starts in ASCII not Binary mode and will break any binary file transfer. Try the following: >ftp ftp.yoursite.com User: <username> Pass: ********* >bi >hash >get filename.exe This should result in a complete transfer. Let us know Carl

[#5]

Same thing. If I ftp through the Unfiltered protection profile I get " Connection closed by remote host." after most of the file gets sent. If I run through a policy without any protection profile it goes fine.

[rwpatterson]

Perhaps FTP client comfort settings?

[#7]

Have you seen this apply if the FTP protocol is not even selected in the protection profile? Looking at the unfiltered profile I see that Interval is 10 and Amount is 1. I' ll try playing with those. Any recommendations? Thanks.

[rwpatterson]

If it' s not selected, then the A/V will read the entire file before passing it. Could be your issue. Leave the settings as they are, and check the FTP box...see what happens.

[#9]

Selecting FTP under AV fixed it. I didnt want to apply the AV layer at the point this is deployed. So the questions are: 1) Why is this causing the file transfer to fail? 2) Why is it scanning AV if it' s not configured in the Protection Profile? 3) Would this apply to other protocols in AV?

[rwpatterson]

Create a policy for FTP alone, and skip the PP... Don' t have the answers, but a temporary solution.