Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

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

FTP with SSL connection (WS FTP pro / IIS 5) "500 'AUTH SSL': command not understood"

Issue: WS FTP Pro cannot establish FTP with SSL connection. 500 'AUTH SSL': command not understood

Environment:

 Server: IIS 5 on Windows 2000 Server (latest Updates from MS), Thawte Certificate Installed
 Client: WS FTP Pro 9.01 Client for Windows (98,2000,XP,2003...)

Problem:

 Regular FTP connection can be established with proper USERID/PASSWORD.
 "FTP with SSL" connection doesn't succeed; give following error:
==================================================================================
Finding Host ftp.starrfish-xyz.com...
Connecting to 142.35.61.118:21
Connected to 142.35.61.118:21 in 0.015625 seconds, Waiting for Server Response
Initializing SSL Session ...
220 starfish Microsoft FTP Service (Version 5.0).
AUTH SSL
500 'AUTH SSL': command not understood
==================================================================================

Any suggestion regarding problem/ solution will be greatly appreciated.


Thanks,

tjipro
0
tjipro
Asked:
tjipro
  • 2
  • 2
1 Solution
 
Dave_DietzCommented:
The Microsoft FTP service does not support SSL in any of its versions to date.

If you want to use SSL secured FTP you will need to move to a different FTP server product.

Sorry.

Dave Dietz

0
 
tjiproAuthor Commented:
Dave, this is interesting. Is it possible to use IIS web server for FTP with SSL by using any interface that you know of?

Thanks,
tjipro.
0
 
Dave_DietzCommented:
If you are looking for secure file transfers the only native way to do this in IIS is via WebDAV.

Do a search on WebDAV in the IIS Help files and you should find enough to get you started.

If you are tied to FTP for some reason you could use an SSL proxy for FTP.  There are some free and some commercial SSL proxies that can be used for secure FTP.  The general idea is that you create an SSL connection to the proxy (often installed on the same machine) which then makes an unsecure connection to the FTP server (since this happens internally the traffic is not vulnerable to sniffing on the Internet).

A couple samples on the web (I have not tested/used these go I make no guarantees):

http://www.kiesoft.com/proxy/index.htm
http://www.versiontracker.com/dyn/moreinfo/win/23472

Dave Dietz
0
 
tjiproAuthor Commented:
Dave, Thanks for this useful information.

tjipro
0

Featured Post

Put Machine Learning to Work--Protect Your Clients

Machine learning means Smarter Cybersecurity™ Solutions.
As technology continues to advance, managing and analyzing massive data sets just can’t be accomplished by humans alone. It requires huge amounts of memory and storage, as well as the high-speed power of the cloud.

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