Hi Chris,
WS_FTP Server expects the SSL connection to be sent with the request for an FTP Connection.
If you try to change the ports that SSL is runing on from the ports that the FTP Connection is being sent on, the connection will fail.
 

Paul Lupo
Technical Sales Engineer
Ipswitch, Inc
www.ipswitch.com
 
 
----- Original Message -----
Sent: Monday, December 17, 2001 12:23 PM
Subject: [WS_FTP Forum] WS_FTP Server 2.03 setup

I am trying to setup a copy of WS_FTP server (version 2.03, purchased last year by my company) with SSL.  My machine setup (all of this on one machine):

 

Win2K Server, SP2 (acting as a DC)

IIS 5.0 (specifically uninstalled the FTP server that comes with IIS)

Microsoft ISA Server Standard Edition

 

Microsoft ISA is configured to correctly allow ports 21, 20 for regular FTP traffic, and ports 990 and 989 for FTPS traffic.

 

The machine uses ISA to share the one internet connection in that office.  I am able to install WS_FTP Server without any problems.  It functions normally when I connect (using WS_FTP Pro 6.7 client) to port 21.

 

My next step was to create a certificate, then setup the server to use the new certificate (I used a common name that is the same as the server's internet name) - the server reports that the key and cert files exist, and that the passwords are identical.  It looks like I could not apply changes if this were an incorrect setup.

 

However, the server is not listening on ports 990 and 989 (using netstat AND TCPViewPro to verify this), and I cannot connect via SSL (the usual error from the ftp client: This site was configured to use a secure connection, but the remote server does not support SSL).

 

Disabling ISA server, then restarting the service does not cause the service to start listening on the FTPS ports, nor does it help the client connect to the server.

 

Anyone seen this before, or have any ideas?

 

Chris

 

 

Reply via email to