Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 199
  • Last Modified:

Encrypted file size increases using ftp client but stays same when e-mailing.

No idea how to troubleshoot this.  An encrypted proprietary file type is roughly 7,000kb when created by the application.  When e-mailed using groupwise the file is the correct size and seems to be ok (it imports but with errors)  and e-mailing secure files is not a viable option.

When the file is transferred using Glub Tech secure ftp 2.5.9 the file size changed to over 12,000 kb and was totally un usable, would not import.  
We have done this exact process at other sites without this problem.  This is specific to this machine/network/firewall/os.  Where do I begin to check settings to find out why this happened from this site?  The file itself is not readable or comparable but I do know when its unencrypted its an .xml file.

I have over 75 files to get transferred and ftp is the only approved way.  I'd rather not just use a different ftp client but instead get to the bottom of why this happens from this site.
0
KathleenR
Asked:
KathleenR
1 Solution
 
JMBowersCommented:
Try the simple things first: make sure you are doing a binary transfer and not ascii.
Look in your ftp log files - if unexpected characters have been found and/or translations applied you will probably get error messages.
As an experiment you could try uuencoding the file before ftping it then uudecode at the other end.
0
 
Rich RumbleSecurity SamuraiCommented:
You can FTP via the cmd line, or with a script/batch file. you may need to check to see if your using Binary mode or Ascii mode... if your transferring text files, ascii is good to use, if your transferring a word doc or excel spread sheet, binary is better to use, same for an .exe, .zip, etc... most transfers should be binary.
http://security.sdsc.edu/software/secureftp/docs/options.shtml

open a cmd window (you can use the same commands they do... copy and paste ;)
http://www.nsftools.com/tips/MSFTP.htm
https://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/ftp__ascii.mspx?mfr=true
https://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/ftp__binary.mspx?mfr=true

Since version
# 2.0.9 [CLI] [20030721]:
# Allow for auto transfer mode (we determine binary/ascii transfer).
They seem to use auto-detect, I have a feeling it's not working correctly, and you can set it manually, or try it via the cmd line or via a browser.
-rich
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Firewall Management 201 with Professor Wool

In this whiteboard video, Professor Wool highlights the challenges, benefits and trade-offs of utilizing zero-touch automation for security policy change management. Watch and Learn!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now