Sponsored Content
Full Discussion: Working with FTP
Operating Systems Linux Red Hat Working with FTP Post 302711515 by admin_xor on Saturday 6th of October 2012 05:33:11 PM
Old 10-06-2012
Well, what is the ftp client you are using? Have you opened ftp related ports on firewall i.e iptables?

Accessing your FTP server from Internet can be done of course. You have to enable NAT in your router and for that you have to consult your router's manual.
This User Gave Thanks to admin_xor For This Post:
 

10 More Discussions You Might Find Interesting

1. Cybersecurity

FTP is not working.

Hi, I'm getting the following error while trying to use the ftp command. ---------------- 331 Password required for prodofsa. Password: 230 User prodofsa logged in. ftp> ftp> ftp> ftp> ls 200 PORT command successful. 425 Can't build data connection: Connection timed out. ftp>... (10 Replies)
Discussion started by: ronald_brayan
10 Replies

2. AIX

FTP is not working

Upto last month my script was working fine, Now I am getting following error, any one help me? Tcl_Init failed: Can't find a usable init.tcl in the following directories: /usr/local/lib/tcl8.0 ./lib/tcl8.0 ./tcl8.0/library ./library This probably means that Tcl wasn't installed... (0 Replies)
Discussion started by: redlotus72
0 Replies

3. Shell Programming and Scripting

why the mv is not working in an FTP

Why when I mv $UpLoadFileName supfinaid.DSB does not work, it is getting the $UpLoadFileName and it is moving it to the right location, but not the move, Let me know if you want to see the all script, I just want to rename $UpLoadFileName, it is moving $UpLoadFileName to the right... (6 Replies)
Discussion started by: rechever
6 Replies

4. Web Development

is wget working in ftp ?

I get ftp> wget ?Invalid command. ftp> 0 * * * * wget -O - -q -t 1 http://www.example.com/cron.php ?Invalid command. thanks (6 Replies)
Discussion started by: aneuryzma
6 Replies

5. UNIX for Dummies Questions & Answers

FTP not working, need some help

I am trying to set up an account for a user on our network to ftp into and access his folder for his web site. I have been tossed into the previous web hosting server without really knowing much about how it has or is set up, but I've been following most of the tutorials I have seen around the... (0 Replies)
Discussion started by: nlraley
0 Replies

6. Linux

FTP not working under Linux but working under any other OS ??? Very strange

Dear all, I am totally despaired and puzzled. Using Filezilla under Windows under the same network as our Linux servers is working. Using FTP command-line client under any of our Linux debian servers is not working ! I tried with different FTP servers -> same problem ! All commands are... (12 Replies)
Discussion started by: magix_ch
12 Replies

7. Solaris

All i/o (ftp) not working on this SunOS 5.10

Hi everyone: I have been trying to simply FTP a file over to this SunOS 5.10 (which is same as Solaris 10 now) and nothing works! I can only Telnet to this via SSH (with my own account/uid), and I can also send simple mail out with mailx, that's all!!! I cannot FTP to it (I think FTP... (7 Replies)
Discussion started by: steve701
7 Replies

8. Shell Programming and Scripting

Script not working after FTP

Hi Gurus, I prepared a script to process some files and then ftp the output file to mainframe directory. Here is the code snippet for the same. # Perform FTP echo "put $TGT_DR/$K.$F.$I.$K1.$RUN_TYPE '$K.$F.$I.$K1.$RUN_TYPE'" >> $LogFile ftp -i -n <<EOF >> $LogFile open... (2 Replies)
Discussion started by: svajhala
2 Replies

9. Solaris

FTP not working Solaris 10

Hi All, I have a problem with FTP service on Solaris 10. Whenever I try to FTP to one machine locally (ftp localhost) or from other machine I don't get any response, I see the ftp service on the machine is online and listening to port 21 but ftp is not responding. Also it seems i can't... (16 Replies)
Discussion started by: belal84
16 Replies

10. Solaris

Why is sftp working but ftp not

I am not very familiar with the use of FTP, and trying to run it I found out that standard "ftp" is not working" but "sftp" is. If sftp is allowed will that block ftp ? and if so where is this set ? I thought there is no relationship, is that right ? If so look here: inetadm | grep ftp enabled... (11 Replies)
Discussion started by: manni2
11 Replies
FTP-PROXY(8)						    BSD System Manager's Manual 					      FTP-PROXY(8)

NAME
ftp-proxy -- Internet File Transfer Protocol proxy daemon SYNOPSIS
ftp-proxy [-6Adrv] [-a address] [-b address] [-D level] [-m maxsessions] [-P port] [-p port] [-q queue] [-R address] [-T tag] [-t timeout] DESCRIPTION
ftp-proxy is a proxy for the Internet File Transfer Protocol. FTP control connections should be redirected into the proxy using the pf(4) rdr command, after which the proxy connects to the server on behalf of the client. The proxy allows data connections to pass, rewriting and redirecting them so that the right addresses are used. All connections from the client to the server have their source address rewritten so they appear to come from the proxy. Consequently, all connections from the server to the proxy have their destination address rewritten, so they are redirected to the client. The proxy uses the pf(4) anchor facility for this. Assuming the FTP control connection is from $client to $server, the proxy connected to the server using the $proxy source address, and $port is negotiated, then ftp-proxy adds the following rules to the various anchors. (These example rules use inet, but the proxy also supports inet6.) In case of active mode (PORT or EPRT): rdr from $server to $proxy port $port -> $client pass quick inet proto tcp from $server to $client port $port In case of passive mode (PASV or EPSV): nat from $client to $server port $port -> $proxy pass in quick inet proto tcp from $client to $server port $port pass out quick inet proto tcp from $proxy to $server port $port The options are as follows: -6 IPv6 mode. The proxy will expect and use IPv6 addresses for all communication. Only the extended FTP modes EPSV and EPRT are allowed with IPv6. The proxy is in IPv4 mode by default. -A Only permit anonymous FTP connections. Either user "ftp" or user "anonymous" is allowed. -a address The proxy will use this as the source address for the control connection to a server. -b address Address where the proxy will listen for redirected control connections. The default is 127.0.0.1, or ::1 in IPv6 mode. -D level Debug level, ranging from 0 to 7. Higher is more verbose. The default is 5. (These levels correspond to the syslog(3) levels.) -d Do not daemonize. The process will stay in the foreground, logging to standard error. -m maxsessions Maximum number of concurrent FTP sessions. When the proxy reaches this limit, new connections are denied. The default is 100 ses- sions. The limit can be lowered to a minimum of 1, or raised to a maximum of 500. -P port Fixed server port. Only used in combination with -R. The default is port 21. -p port Port where the proxy will listen for redirected connections. The default is port 8021. -q queue Create rules with queue queue appended, so that data connections can be queued. -R address Fixed server address, also known as reverse mode. The proxy will always connect to the same server, regardless of where the client wanted to connect to (before it was redirected). Use this option to proxy for a server behind NAT, or to forward all connections to another proxy. -r Rewrite sourceport to 20 in active mode to suit ancient clients that insist on this RFC property. -T tag The filter rules will add tag tag to data connections, and not match quick. This way alternative rules that use the tagged keyword can be implemented following the ftp-proxy anchor. These rules can use special pf(4) features like route-to, reply-to, label, rtable, overload, etc. that ftp-proxy does not implement itself. -t timeout Number of seconds that the control connection can be idle, before the proxy will disconnect. The maximum is 86400 seconds, which is also the default. Do not set this too low, because the control connection is usually idle when large data transfers are taking place. -v Set the 'log' flag on pf rules committed by ftp-proxy. Use twice to set the 'log-all' flag. The pf rules do not log by default. CONFIGURATION
To make use of the proxy, pf.conf(5) needs the following rules. All anchors are mandatory. Adjust the rules as needed. In the NAT section: nat-anchor "ftp-proxy/*" rdr-anchor "ftp-proxy/*" rdr pass on $int_if proto tcp from $lan to any port 21 -> 127.0.0.1 port 8021 In the rule section: anchor "ftp-proxy/*" pass out proto tcp from $proxy to any port 21 SEE ALSO
ftp(1), pf(4), pf.conf(5) CAVEATS
pf(4) does not allow the ruleset to be modified if the system is running at a securelevel(7) higher than 1. At that level ftp-proxy cannot add rules to the anchors and FTP data connections may get blocked. Negotiated data connection ports below 1024 are not allowed. The negotiated IP address for active modes is ignored for security reasons. This makes third party file transfers impossible. ftp-proxy chroots to "/var/empty" and changes to user "proxy" to drop privileges. BSD
February 26, 2008 BSD
All times are GMT -4. The time now is 05:38 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy