Port 21 used in Jaguar ?

badtz

I'm trying to set up a ftp server with either Rumpus or CrushFTP and it states that port 21 [jaguar] is in use and can't be used?





i don't have anything running that i know of that would use this port?





anyone else with this problem? and a remedy?



thanks!

xaqtly

Did you check your built in firewall to make sure it wasn't blocking port 21? That's all I could think of.

chucker

Also make sure that FTP access is disabled in Sharing. That's the built-in FTP server.

madmax559

cat /etc/services



or

netstat -an



see whats already running....

prolly ipfw may be blocking 21

badtz

the cat /etc/services brought up.....



ftp 21/tcp #File Transfer [Control]

ftp 21/udp #File Transfer [Control]



?????



even with ftp sharing off [or even with the firewall off] rumpus/crushFTP still says I'm unable to use that port. Only when I change to any other port, does it work ....... ???

badtz

okay, now the problem is fixed [i used the readme in crushftp, turn off ftp sharing BEFORE doing it]





one problem now ......





I'm unable to use Transmit to log into my own FTP [on the same mac]......???



The router is forwarding port 21 to me, and the server is running on port 21......



i don't see where the problem could be?

bunge

[quote]Originally posted by badtz:

<strong>okay, now the problem is fixed [i used the readme in crushftp, turn off ftp sharing BEFORE doing it]





one problem now ......





I'm unable to use Transmit to log into my own FTP [on the same mac]......???



The router is forwarding port 21 to me, and the server is running on port 21......



i don't see where the problem could be?</strong><hr></blockquote>



You could try to FTP to 'localhost' or 127.0.0.1



I've had problems hosting a page in the past when using AirPort for NAT routing. My browser couldn't see my own machine when I used a DNS name.

torifile

[quote]Originally posted by badtz:

<strong>okay, now the problem is fixed [i used the readme in crushftp, turn off ftp sharing BEFORE doing it]





one problem now ......





I'm unable to use Transmit to log into my own FTP [on the same mac]......???



The router is forwarding port 21 to me, and the server is running on port 21......



i don't see where the problem could be?</strong><hr></blockquote>



If you're on Airport, you need to configure your ABS to allow connections. I'm not sure how to do it, but I know that's what needs to be done. I've been trying (or have tried, unsuccessfully) to get a carracho server running behind my ABS. If you figure it out, lemme know.

thinkingdifferent

The ftp server must be run as root. Any port below 1024 is considered privledged and processes not being executed by root will not be able to open it.

badtz

Thanks! 127.0.0.1 did the trick!



but now there's one more problem :::



I'm unable to log in...



my home directory for the ftp account goes to....



my home directory.....





is it maybe because the permissions might not be set right?



i know I'm entering the log/pass right........ ???

torifile

If I'm reading you right, you can only go as high as your home directory through ftp. You can't go to the root level of your HD, right? That's intentional because you don't want ftp users going any higher than the top of their directory for security reasons.



It's definitely a good thing, though it's a hassle when it's your own computer. Have you tried just using AFP to mount the drive if you want to access the root level of your drive?



In the finder, cmd+k and type afp://localhost/ (or your ip if you're connecting remotely). Log in and tell it to mount the HD and not your home directory.

badtz

I'm trying to let FTP go into my home directory [not root].



It won't let the FTP user log in saying password is incorrect, even though I know it is. It IS attempting to log in though, so I guess that's a good sign?



Hopefully it's not a permission conflict???

bunge

I'm not sure about the login conflict, but I think I can help with the base station problem. You need to use PORT MAPPING in the AirPort software. That means you have to give a static I.P. to each machine on your network (10.0.1.?) and map port 21 coming to to IP 10.0.1.? port 21. The same would go for a web server, but on port 80.



I'm having a similar login problem when I attempt to FTP from work. My thought was that Apple had updated their FTP software to require a secure client to login with, but I honestly don't know. I haven't had a chance to try using a secure client to test out my theory.

eugene

You probably can't connect to an ftp server behind a firewall using PASV. Instead you probably want to change your FTP client settings to use the PORT connection scheme. You also want to map the ftp-data port 20 to your machine behind the router as well.