Sponsored Content
Top Forums UNIX for Dummies Questions & Answers FTP/TELNET on linux, not working Post 35919 by norsk hedensk on Tuesday 13th of May 2003 05:39:32 PM
Old 05-13-2003
when you do attempt to connect via ftp to your server, do you get any error messages at all? or does the ftp client program just hang?
 

10 More Discussions You Might Find Interesting

1. IP Networking

FTP or Telnet

Dumb question I'm sure but how on earth do I transfer files from a sco unix machine to my windows 2000 machine. I'm typing commands on my Win2000 machine. All I can seem to do is move files around on the unix system? (8 Replies)
Discussion started by: Timbash
8 Replies

2. UNIX for Dummies Questions & Answers

FTP is not working after installing Linux 7.3

hi all, After installing Linux 7.3, when I wasn't be able to FTP to this machine from another machine; however, I do get the reply back when I ping this machine. All I want is able to transfer file on my local machine to this server using FTP comand and it's not working. Could someone please... (1 Reply)
Discussion started by: lapnguyen
1 Replies

3. Cybersecurity

One accout for FTP other to TELNET

Hi All, If I want to have two user accounts from the same grop in UNIX Solaries. However, I want one of them to be used only for FTP while the other for TELNET. Can anybody tell me how to do that? Best Regards (13 Replies)
Discussion started by: omran
13 Replies

4. Solaris

after patch, telnet not working

The problem: I installed the Solaris 8 recommended patch cluster 117350-11 over 108528-15 before the Christmas break. The server is a SunFire V100. Here is the situation: Before the patch install, there was a working cron job that did daily, weekly, and monthly backups of the V100 filesystems... (3 Replies)
Discussion started by: antalexi
3 Replies

5. Red Hat

telnet & ftp in linux AS4 with root account

hi, i installed linux as4, i need telnet and ftp with root account. anybody show me how to configure. TIA, Bong (3 Replies)
Discussion started by: bong02
3 Replies

6. UNIX for Dummies Questions & Answers

Telnet is not working properly

telnet at my system is behaving stange. Some times I am able to telnet to other machines but sometimes it stop doing that. Then i have to reboot the machine and most of the time (not 100%) it works. SImilar is the case with SSH. Sometime it works , some time it don't. i am new to Unix and I do not... (1 Reply)
Discussion started by: deepak_pathania
1 Replies

7. Red Hat

FTP on Linux is not working as expected

Hi, I need to write a Linux shell script which will perform an FTP operation to another server. main.sh will contain - ftp -nd Dest.IP.address < ftpScript.sh Contents of ftpScript.sh is given below - user userid passwd prompt lcd /vidya/Input cd vidya/Output mput *.* close ... (1 Reply)
Discussion started by: vidyak
1 Replies

8. 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

9. Windows & DOS: Issues & Discussions

ANT: Telnet is not working

I am trying the below ANT telnet task: <telnet userid="appldev" password="techm123" server="${BT_Server}"> <read>/u01/appldev/devappl/po/11.5.0/reports</read> <!--write>cd /u01/appldev/devappl/po/11.5.0/reports/</write--> <write>ls</write> <read... (0 Replies)
Discussion started by: Dip
0 Replies

10. Solaris

telnet and ssh not working .... but it pinging in Solaris 8

hi Everyone telnet and ssh not working in Solaris 8 .... but it pinging.... i also checked /etc/services /etc/inet/inetd.conf ps -ef | grep telnet ans default router ... everythinking is ok .... when i connect telnet then suddently closed ... and ssh is connection refused ... help... (1 Reply)
Discussion started by: coolboys
1 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] [-i netif] [-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 ipnat(4) or 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, unless the option -i is specified, it will then use the ipnat(4) interface. 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. -i netif Set ftp-proxy for use with IP-Filter. The argument netif should be set to the name of the network interface where rdr is applied on. -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 Automatically tag packets passing through the pf(4) rule with the name supplied. -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 using pf(4), 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 To make use of the proxy using ipnat(4), ipnat.conf(5) need the following rule: rdr $int_if any port 21 -> 127.0.0.1 port 8021 tcp SEE ALSO
ftp(1), ipnat(4), pf(4), ipnat.conf(5), pf.conf(5) CAVEATS
ipnat(4) and pf(4) does not allow the ruleset to be modified if the system is running at a securelevel 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/chroot/ftp-proxy" and changes to user "_proxy" to drop privileges. BSD
August 1, 2007 BSD
All times are GMT -4. The time now is 01:20 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy