Support Forum
The Forums are a place to find answers on a range of Fortinet products from peers and product experts.
Shredders
New Contributor

FTP failing for specific filetypes and only from Macs

Hi,

We have just had our old SonicWall firewall swapped out for a Fortigate 60F and we are now experiencing some strange issues with FTP uploading from Macs.

Certain filetypes such as PDFs will consistently upload fine. Others, such as .docx or .html files consistently fail.

The same files when uploaded on a PC using Filezilla have no problems.

We have tried both Transmit and Filezilla on a Mac, and tried both active and passive modes, but no difference.

The error on Transmit is "Error -132: could not send file to remote host"

On Filezilla it just says "Could not start transfer"

 

Now, here's the weirdest part of the issue. If we upload a .docx file via a PC, then download it on a Mac then delete it from the server, we are able to upload the downloaded file on a Mac! Almost as if the file has been changed in some way?!

 

We've tried disabling anti-virus but that failed to help.

 

Anyone have any idea what could be the cause and how we can fix this?

 

Thanks

 

3 REPLIES 3
Dave_Hall
Honored Contributor

What 1) fgt model and firmware version is your company using?, 2) what UTM features enabled on fgt and/or are firewall policies separated into covering different traffic (e.g. web filtered traffic vs ftp traffic).  4) this issue affect wireless or wired connections? 5) is ftp-proxy explicit enabled on the fgt? 6) Are the Mac ftp clients uploading in binary mode?

 

Sounds odd, but sounds like the mac clients are trying to upload in asc mode based on the file type and is getting confused.  But try enabling debug mode on your mac ftp clients to see what exact errors are being returned. 

 

 

 

 

NSE4/FMG-VM64/FortiAnalyzer-VM/6.0 (FWF30E/FW92D/FGT200D/FGT101E/FGT81E)/ FAP220B/221C

NSE4/FMG-VM64/FortiAnalyzer-VM/6.0 (FWF30E/FW92D/FGT200D/FGT101E/FGT81E)/ FAP220B/221C
emnoc
Esteemed Contributor III

the "diag debug flow" is your friend, you should use it. Since these are macosx I would use curl as a netural ftp client and see what happens

 

e.g 9 from shell

 

   curl -v -T the_local_file_name   ftp://<ftp-server-name-or-ip/directory/

 

Does it work? if yes then it's not the firewall!

 

ken Felx

PCNSE 

NSE 

StrongSwan  

PCNSE NSE StrongSwan
Shredders

Hi,

We ended up swapping the old firewall back in for now. Will put the suggestions from this thread to the managed services company for when they send someone out to try again. Thanks

Announcements

Select Forum Responses to become Knowledge Articles!

Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.

Labels
Top Kudoed Authors