no route to host
Posted: Fri Jan 05, 2007 8:43 am
hi. i'm having trouble logging into my business ftp server from home. i set the router up on the server side to forward from port 8021 on the router to port 21 on the ftp server. i did this to protect the server from port scanners which often seek out devices on port 21.
at home, i set cyberduck to connect using active mode and port 8021. it logs in fine, but it is unable to list the directory on the server. i get a "no route to host" error. here's the transcript from cyberduck:
the problem seems related to the port forwarding. when i used to have the router on the server side set to pass port 20 to port 20, i was able to connect fine in active mode.
do i need to open up some additional ports? does anyone have any suggestions?
one suggestion i received was to not use the router to do the port reassignment (8021 to 21). i was told it is better to change the port assignment from within apache on the server itself. but, i'm just using the standard apache ftp server built into the mac and i don't know how to configure it to change port assignments. if someone knows the terminal command, i'll try that fix. thanks for your help.
- josh
at home, i set cyberduck to connect using active mode and port 8021. it logs in fine, but it is unable to list the directory on the server. i get a "no route to host" error. here's the transcript from cyberduck:
220 pj-graphics-G5.local FTP server (tnftpd 20040810) ready.
USER josh
331 Password required for josh.
PASS ********
230-
Welcome to Darwin!
230 User josh logged in.
SYST
215 UNIX Type: L8 Version: tnftpd 20040810
PWD
257 "/Users/josh" is the current directory.
NOOP
200 NOOP command successful.
CWD /Users/josh
250 CWD command successful.
PORT 10,0,1,3,222,178
500 Illegal PORT command rejected
PASV
227 Entering Passive Mode (192,168,15,102,233,199)
the problem seems related to the port forwarding. when i used to have the router on the server side set to pass port 20 to port 20, i was able to connect fine in active mode.
do i need to open up some additional ports? does anyone have any suggestions?
one suggestion i received was to not use the router to do the port reassignment (8021 to 21). i was told it is better to change the port assignment from within apache on the server itself. but, i'm just using the standard apache ftp server built into the mac and i don't know how to configure it to change port assignments. if someone knows the terminal command, i'll try that fix. thanks for your help.
- josh