0

I have a small Win2003 server that I need to allow remote file uploads. It is behind a router with port forwarding. Is there something simpler than setting up FTP on IIS and making the necessary changes to both IIS and the router to allow the passive connections through? Is there something more secure (like SCP/SSH) that doesn't get complicated and/or expensive?

3
  • If the router is bothering you, you could use FTP with a VPN solution like OpenVPN which is easy to setup. Aug 24, 2009 at 19:53
  • i really wonder how could scp/ssh be considered 'complicated' or 'expensive'
    – Javier
    Aug 24, 2009 at 19:59
  • Javier, back in the day Windows SSH daemons were few and far between, and fairly expensive. Times have changed though, thank goodness. Aug 26, 2009 at 0:41

5 Answers 5

3

A free alternative to WinSSHD is FreeSSHD- it also support SFTP, ssh, and so forth. Filezilla is a great client- supports FTP, SFTP, and FTPS.

2
  • Thanks Tim. FreeSSHD was just what I was looking for. Very simple to install and setup. Aug 25, 2009 at 15:14
  • Excellent! Also, it looks like freesshd now supports port forwarding, so you can use it as a poor man's VPN, just like Unix sshd. Aug 26, 2009 at 0:40
1

One method would be to install WinSSHD. It's an SSH server for Windows. It allows you to connect from an SSH client (the same company has a free one). Once connected, there is an SFTP manager that allows you to transfer files over the SSH tunnel.

As an added benefit, you can also RDP to the server and create port-forwarding rules so that you can tunnel other traffic through your server.

I should point out that the software is free for non-commercial use, or $100 for commercial use.

1

WebDAV might work for what you need. Everyone says it is dead, or dying, or depreciated as a protocol, but nothing strong has replaced it yet.

1

Tim mentioned the Filezilla Client. I would like to mention the Filezilla Server.

From the Filezilla Server Wiki:

FileZilla Server is an FTP server that supports FTP and FTP over SSL/TLS. FTP over SSL/TLS provides secure encrypted connections to the server.

I already installed the server once and it is pretty easy to install and configure. (But I did not use the SSL functionality. I don't think it gets that much more complicated.)

0

You can also use FTPS or SFTP The first one use SSL encryption the second one use SSH in order to perform the transfers.

You can under windows run Serv-u (not that expensive) and good for production which allows you to choose either FTPS or SFTP.

Mmoreover it provides a secure webinterface, that's a point if your client don't have any client.

Personnally I prefer SFTP because I only need to forward one port (usually 22) while in FTP you need : the 20 for the datas / 21 for command and a range of high port for passive transferts

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .