Solved

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

Posted on 2004-10-09
4
2,394 Views
Last Modified: 2013-12-04
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
Comment
Question by:tjipro
  • 2
  • 2
4 Comments
 
LVL 34

Expert Comment

by:Dave_Dietz
ID: 12267701
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
 

Author Comment

by:tjipro
ID: 12272687
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
 
LVL 34

Accepted Solution

by:
Dave_Dietz earned 125 total points
ID: 12273548
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
 

Author Comment

by:tjipro
ID: 12278069
Dave, Thanks for this useful information.

tjipro
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Recently, a new law in my state forced us to get a top-to-bottom analysis of all of our contract client's networks. While we have documentation, it was spotty at best for some - and in any event it needed to be checked against reality. That was m…
Article by: btan
The intent is not to repeat what many has know about Ransomware but more to join its dots of what is it, who are the victims, why it exists, when and how we respond on infection. Lastly, sum up in a glance to share such information with more to help…
With Secure Portal Encryption, the recipient is sent a link to their email address directing them to the email laundry delivery page. From there, the recipient will be required to enter a user name and password to enter the page. Once the recipient …
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the admini…

679 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question