The Case of the Non-Working FTP Server

LobsterCowboy

Junior Member
Oct 18, 2002
5
0
0
I just got broadband, and I thought it would be fun to set up a private FTP server so I could share files with my buddies.

However, my cable company isn't a fan of servers, so I'd like to place it on a non-standard port.

Now this is when it gets tricky.

I've been trying two different servers, Bulletproof, and FileZilla Server. Both are run as programs on Windows XP, not services. For some reason, a few people I know can connect to my current port number (69), but some can't. They log in just fine, but their clients hang at LIST when it tries to show my directories.

My firewall is the one that came with XP, and I've opened 69 up for FTP. I've also tried opening 20 and 21 just in case (because I understand that FTP can use CMD on port 21, and DATA on 20), but the problem remains. Heck, I've even pulled down my entire firewall, and the same people still can't see my directories.

I did try running the server on port 21, and everyone could manoeuver into the directories. I only run into issues on non-standard ports.

Can I work around this? I don't see why Cablevision should have a problem in the first place. My server will hardly eat up any bandwidth (it only allows three users, and no anonymous logins allowed), and it won't even run all the time. Perhaps if I keep the server small, I can keep it on 21 without running into trouble?

I hope the nature of this question isn't illegal, but I don't think it falls under the DMCA ;)

Any and all help would be appreciated :)
 

dethman

Lifer
Oct 12, 1999
10,263
3
76
are both you and your friends behind routers? i've found that if both connections are behind routers, the only port that will work is port 21. if only one person is behind a router, then a nonstandard port will work fine. don't ask me why, i have no idea, as i've fiddled with this for quite awhile as well but i've just accepted this as fact. *shrug*