Secure FTP for Windows 2000 Server - windows

Can someone recommend a secure FTP implementation that works well on Windows Server 2000? I'm uploading files into virtual directories and web applications under IIS and the existing provider, obviously, isn't secure or encrypted.

Did you try filezilla server? http://filezilla-project.org/
It supports FTP over SSL/TLS
Check out -
http://wiki.filezilla-project.org/FileZilla_FTP_Server

http://www.serv-u.com/
Is good. They support both ftp/ssl and Sftp.

This solution cost money; nonetheless, we've recommended it to some clients before as it's pretty simple to setup. http://www.serv-u.com/

Free SSHD works well. It supports remote console as well as file transfer, plus secure port forwarding.

CrossFTP Server, free and provides FTP/TLS support as a secure FTP server.

Try CompleteFTP. It's a fast, compact, easy to install Windows server that supports SFTP and FTPS.
And you don't need to purchase the most expensive edition to get SFTP support - for $199 you get FTP, FTPS and SFTP.

Related

How login FTP server using ssh private key and credential

Hope everyone is doing well,
I have one new request from the client.
We sends files from our server to one FTP server.
But now client want to use new credential and private ssh key for that FTP server and he shared the same with us.
We have opened the new port also, but I am unable to login into FTP server. Did I need to do something to login or is their different ways to login for the same.
Regards,
Mustafa
FTP can use SSL, which supports client authentication using X.509 certificates. However, while many FTP servers support FTPS, I don't know of any which support client certificates. (In addition, client authentication is complicated in SSL – in many cases, you would have to create and maintain your own certificate authority and stuff. Not many clients support this kind of authentication, either.)
Much easier is to use SFTP, the SSH file transfer protocol. It uses exactly the same keys as "normal" SSH would. On Windows, WinSCP and FileZilla support SFTP.

ftp-authssl:// - what does it mean?

One of our programs uploads data to external FTP servers.
Connection (credentials and/or data) is encrypted.
It worked well until one of these external FTP servers installed one of the latest MS patches which has broken the encryption.
I am trying to set up a test environment to reproduce the issue.
The URL which is used by our program is
ftp-authssl://123.123.123.123:21
(actual IP is replaced by 123.123.123.123)
What does ftp-authssl:// mean?
The program is written in C#. It uses Eldos Secure Black Box (https://www.eldos.com/sbb/) library to upload data to FTP server. FTP server is IIS running on Windows Server 2008 R2.
This is explicit TLS mode for FTP, where you start with a plain connection and then issue a AUTH TLS (or older AUTH SSL) command and then upgrade the plain connection to TLS. This is similar to STARTTLS with other protocols like SMTP or IMAP.
See Wikipedia article to FTPS for more details.

How to enable enable messaging queue (MSMQ) on a ftp server

I have a website hosted on a ftp server, I dont have access to that server except ftp credentials and a plex panel support. I want to use MSMQ to use queues so basically on local I have enabled MSMQ through windows features. But when I publish site on ftp server, it gave error:
Message Queuing has not been installed on this computer
So please help me to sort out this.
Thanks in advance.
If you only got FTP-credentials you are stuck with what the system administrator has set up for you. There is no chance you can get MSMQ running there without the sysadmin doing the installation work.

Receive File via SFTP/SSH and automatically forward to FTP on another server

I'm currently in a situation where I receive flat files via FTP from my clients. A couple of clients have insisted on the need to use SSH Private Key SFTP rather than regular FTP.
What I want to do is setup a web server (preferably in linux/unix but I guess I can do it on a windows server and purchase SFTP server software) that will do the following:
Allow me to setup an SFTP directory for each client with unique user/pass. Each directory also has to have the public/private key SSH "stuff" I'm a little new to this but I've googled it.
Once the file is completely uploaded by the client, I want to kick off an event that ftp's that file via regular FTP to my Windows cloud.
These files can be up to 10mb so the even that ftp's to the other server can't fire until the file is completely uploaded.
Has anyone set something like this up? Any guidance would be appreciated.
Thanks!
In Linux, you can use incron to monitor the directory the files will be SFTP'd to and have it trigger your ftp job. It's kind of like cron except that instead of triggering jobs based on time, it does so based on filesystem modifications. In order to only trigger once the entire file has been written, I think you can use IN_CLOSE_WRITE in the inotify mask. Failing this, I suggest configuring events for each of the events individually to echo a message to a log file and see if you can identify one which reliably happens only at the end of the SFTP transfer.
If you're using RedHat, it's not in the standard distribution, but it is in EPEL.
On Windows you could use Titan FTP Server Enterprise Edition, which supports SFTP as well as allows you to define various types of events. When the event is triggered, you could kick off anything you need on a per folder/per account basis.
PS. AFAIK, when it comes to SFTP it is either password authentication or public key authentication (SSH key), but not both.
In your UNIX server, you can configure SSH to use a custom sftp server that instead of handling SFTP protocol itself, opens a new SSH connection to to the Windows SFTP server using password authentication and forwards the SFTP traffic there.
Writting the proxy is easy with the right tools, for instance, in Perl using the Net::OpenSSH module:
#!/usr/bin/perl
# this is the sftp-proxy-server
use Net::OpenSSH;
my $ssh = Net::OpenSSH->new($windows_server, $user, $passwd);
$ssh->system({ssh_opts => '-s'}, 'sftp');
$ssh->error and die $ssh->error;
You can instruct the SSH server to use that alternative SFTP server changing the configuration in /etc/ssh/sshd_config. For instance:
Subsystem sftp /usr/local/bin/sftp-proxy-server
Did you try apache FTP Serveur ?
I think you can do what you need with the ftplet API.
see :
http://mina.apache.org/ftpserver-project/index.html

How do I implement support for ftp in WP7?

Hi
I would like to retrieve documents from an ftp in my Windows phone 7 application (built with XNA in my case).
As far as I understand WP7 does not support ftp due to port and protocol(?) contraints.
Is there any way to get ftp support working?
I guess I will be able to implement it my self once socket support is added but I dopn't wan't to wait for that.
Cheers
/Jimmy
Since there are no supported socket capabilities in the initial release of WinPhone , you cannot directly FTP. You would have to create an "FTP Proxy" web service which your phone would call and have the service do the actual FTP and relay the files.
FTP and Sockets are not supported by the platform at the moment.
If you want to get remote files on to your phone you'll have to use HTTP(S).
You can do this either with the HttpWebRequest or WebClient classes depending on your specific needs.
Do you want to retrieve files fromn the phone, and over the cellular network? If so you need to confirm your operator allows ftp connections to your phone, which they probably do not.
If you're connecting over wifi, you've got more chance of this working.
Otherwise, you could implement a dropbox-style approach where the phone and your file-retrieving application both connect to a remote server
If this is for development purposes, you can get access to the phones storage and copy in files by using Microsoft's SmartDevices API.
I'm trying to do the same but so far the only way I've found around it is to create a web service to run on my own server which retrieves the FTP files on behalf on the phone.
Wish MS would hurry up and give us sockets - calling a web service is fine but I'm pretty sure it would be slower than directly getting the FTP files from the phone itself.

Resources