Using FTP

I’ve setup an FTP server some time ago but I can’t seem to get it working. I’ve blogged about FTP’ing before, where I asked you people what application to use. I’m using BulletProof which seems like a great server!

Maikel has given me this great url,, from where I can test my FTP server. I did a test, it gives an error immediatly! 🙂

Now I’m having some problems.
First one is that nobody from outside seems to be able to connect to it. I’m running a NAT service as well and have mapped port 21 to my internal ip address. That raises question one, found below.

Second is, at work we’re behind a proxy which doesn’t allow FTP’ing. It’s not just port 21, as I believe. When I try servers located on different ports, I also can’t connect. That raises question two.

1. Are there any other ports used when FTP’ing, besides port 21?
2. Is there a solution for FTP’ing through HTTP or HTTPS or anything?

Question 2 probably doesn’t have an answer. As I think of it, 1 doesn’t have one either, probably… Anyway, I’ll have another look. Maybe someone can help me.

You may also like...

5 Responses

  1. Carlo Poli says:

    To start with question 2, I assume that you opened up FTP to allow bloggers to upload images. There are lots of tools that allow upload from a HTML-from and then be written to disk. I have used such a tool quite a lot in ASP, I think it was called ASPUpload or something like that. Haven’t used it yet in ASP.NET. It suprised me that .Text doesn’t offer such a feature, because publishing pictures is something you need to do quite often.

    To answer question 1, I don’t think that standard FTP uses any other port than port 21.

    BTW, why don’t you use the standard IIS FTP Server?

  2. It definitly should be a part of a blogging engine with wysiwyg editor capabilities. But unfortunatly it doesn’t.

    Fortunatly BlogJet provides this in sending the pictures to an FTP account. The great thing is, it transforms the url in the img tag to the location where the image is on the http server. Ofcourse the image should be available on http after ftp’ing it, but that’s logical.

    I’ve also thought about building a special tool for .Text or something. I’m also planning this for my own website. A tool where you can wysiwyg your postings in, include pictures and the works and then upload them (later, if you want) to the server. It will then be implemented by webservice, including the picture part.

    I don’t use the standard IIS FTP server because BulletProof is much more flexibel. If I’m not mistaken, I have to setup multiple accounts on my windows machine to have IIS FTP running with multiple accounts. I don’t want that. Besides that, I can set up- and download speed per user, which I seriously want!

  3. Paul Gielens says:

    bpftp lets you configure you’re port… first switch of all ip homes in setup/user accounts/home ip/

    Then check your port in setup/main/general/ make sure you’re isp isn’t scanning your ports, setting a port other then 80 would be fine.

    You could run ssh/cygwin on your windows box and tunnel traffic.

  4. The port 21 not being reachable was my fault. I just discovered I hadn’t mapped port 21.

    The reason for this is I had my FTP server on port 81 because I hoped it would work at work (great, work at work 😉 but it didn’t. When I changed the port in the server back, I didn’t do it in the mapping table.

    I just tested the ftp server with net2ftp and it worked like a charm. Better yet, what I didn’t expect, I can browse the ftp server, upload files, create directories, everything! Just two things:

    – I can’t upload files that take longer then 20 seconds to upload. This means I seriously have to higher to max upload speed for my bloggers.

    – There’s something about the supplying my FTP password to net2ftp that I don’t seem to like. Can you imagine? 🙂

  5. Mischa Kroon says:

    Question 2: there is something called secure ftp which does ssl FTP don’t know which clients support this.

    Or which servers for that matter.

    If your ever in a jam for a port to use for an FTP server try 8080.

    Thats an alternative http port which isn’t used to often, but is still open on almost all locked down situations.

Leave a Reply

Your email address will not be published. Required fields are marked *