New answers tagged

1

Addendum to Martin Bøgelund's answer: The why-question (which I assume is "why did the original attempt do what it did") is interesting, and simple when you think about it the right way: it's the same dir [remote-directory] [local-file] syntax, where the remote directory happens to be >. The ftp client is not a shell. Commands typed into it are not shell ...


0

The simplest way is open Computer folder where you see all your drives. Here you need to create a shortcut for ftp server. To do this, on empty space in computer folder right click and click on 'Add a network location' click on it and follow the prompt to create shortcut for your network ftp server. If you have password for it or is anonymous do that. You ...


0

Unfortunately you can't use UNC paths to refer to locations on FTP. UNC paths imply SMB/local Windows paths. An alternative would be to mount a FTP site as a local drive, and then pass that local path to your tool. See e.g. http://www.thewindowsclub.com/map-an-ftp-drive-windows


0

Many people don't care about %SystemRoot%\system32\inetsrv\inetinfo.exe While creating the FTP server on Windows Machine. The application must be white listed before you access the connection from your sub-net or the internet. First you allow these ports: 80, 20, 21 for both HTTP and FTP. Then add exception for "inetinfo.exe"


0

We have faced a similar problem in our enterprise setup; it was caused by following line in configuration of the Cisco ASA on the way between the involved machines: inspect ftp strict Removal of the strict did the trick.


0

What I find most interesting about this issue is that neither the proftpd nor vsftpd source code bases have the string "Contact admin". This, to me, suggests that the error message your FTP client is receiving is not, in fact, coming from the FTP server. A search on Google for that error string turned up a few different posts, all of which point toward the ...


0

There's no better solution. Your solution with the goto loop is the easiest solution you can get to get reconnected for keepuptodate command. Of course your WinSCP script needs to end with exit command, so that it automatically closes.


0

What you think of for UNC paths \\server\share are typically for SMB/CIFS aka "Windows file shares", not FTP. You can use a free Samba server to host the files you need and they'll be accessible by a UNC path: Some links for you: https://www.samba.org https://www.samba.org/samba/docs/using_samba/ch01.html Here is Samba file server setup for Ubuntu: ...


1

You can have different server software handle the same port number of different subdomains, if the subdomains have different IP addresses only. In the end, the web browser connects to the IP address and port number, not to the domain name. So if the IP address and port number is the same for different (sub)domains, the operating system on the target server ...


0

Don't forget to find the line UsePAM yes and comment it: #UsePAM yes Without disabling this, your SSH server would crash on reloading/restarting. Since you do not need fancy functions of PAM, this is fine.


0

I think the culprit here is that your ldap.conf file has both LDAPGenerateHomedir and CreateHome: LDAPGenerateHomedir on 0700 CreateHome on 0700 Only one of these directives is needed to actually create home directory. The CreateHome directive is the newer, more recommended path; the howto to which I linked has more examples/descriptions of what you can ...


1

The most frequent causes for login delays with proftpd are: Reverse DNS resolution of client IP (disabled via UseReverseDNS off) RFC1918 lookups (disabled via IdentLookup off) Timing delays added via mod_delay (disabled via DelayEngine off) Hopefully one of these tweaks will help!


0

Now that proftpd has its own SFTP implementation via the mod_sftp module, using that for your SFTP needs (rather than OpenSSH) might neatly address this issue.


0

To get proftpd to listen only on localhost, you would use both DefaultAddress and SocketBindTight, like so: DefaultAddress localhost SocketBindTight on By default, proftpd will listen on all interfaces for a given port (e.g. "*:21"). The SocketBindTight directive tells proftpd to bind "tightly" to the address/socket, rather than using a wildcard socket ...


0

You can use the bind option of mount to remount the other folder so the FTP server sees the files as being within the root of the website. ...You could mount /home/shared/files/ under /home/website/files/ like this. Create a mount point ( a directory ) in /home/website mkdir /home/website/files/ Mount the other directory under this mount point mount ...


0

man ftp says: ls [remote-directory] [local-file] Print a listing of the contents of a directory on the remote machine. The listing includes any system-dependent information that the server chooses to include; for example, most UNIX systems will produce output from the command ‘ls -l’. (See also nlist.) ...


0

Please check on below links- : http://linuxpoison.blogspot.in/2008/09/split-and-merge-large-files.html http://unix.stackexchange.com/questions/24630/whats-the-best-way-to-join-files-again-after-splitting-them


0

ProFTPD did not, until seeing your post, have this capability. However, I filed it as a feature request, and the code implementing this has been merged. So now I'm happy to say that proftpd would meet your needs/requirements.


0

For anyone else looking for this sort of functionality, the mod_proxy module for ProFTPD supports proxying of FTP and FTPS, and can be configured to require FTPS connections only. Full disclosure: I'm the author of mod_proxy and ProFTPD.


2

AWS has a feature called VPC Flow Log that captures all the traffic coming to a VPC or a particular subnet or a particular network interface. You can setup VPC Flow log and these logs are then populated to AWS CloudWatch. It gives a very descriptive Log information and you can filter your query from that. Check more on AWS VPC Flow Log


0

It's been a while since this was first asked, but ProFTPD does support FTP, FTPS (via mod_tls), and SFTP (via mod_sftp) now. And to answer the question, you can configure ProFTPD to simultaneously allow both FTP and SFTP, or just SFTP only. The same rich, configurable logging that ProFTPD does for FTP transfers is done for SFTP transfers.


1

If you want to see dropped traffic you'll need to do the whitelist using a firewall running on your EC2 instance, not the AWS infrastructure. (Your server cannot log/see traffic that it doesn't receive). You may want to look into something like Fail2Ban. A word of advice, there are bot nets that will try to connect to your IP (especially on EC2) via SSH ...


1

While it is commonly used, it's not defined anywhere, afaik. The CLNT has been added to ProFTPD server recently. Note how it is referred to in its release notes: Support for the common CLNT FTP command. Comparing to for example: Support the HOST command (see RFC 7151). (emphasis mine)


0

For VSFTPD, You can specify passive port ranges pasv_min_port=1024 pasv_max_port=1048 Credit: Setting up FTP on Amazon Cloud Server Additionally, I was seeing wget fail, but curl succeed when the pasv_address did not match the IP of the request -- e.g. the request was using the external network IP, but the pasv_address was the internal network IP. ...


1

You have to open the port range 64000-64321 in the local firewall on the server. And if there are any external firewalls or NAT's, configure these to allow/route the port range too. See also a relevant WinSCP article to understand a network configuration needed for passive FTP.


1

Check your VSFTPD logs and take appropriate action. If SELinux is enabled check /var/log/audit.audit.log for relevant messages and take appropriate action. Ensure that your firewall is configured to allow port 21 and RELATED connections.



Top 50 recent answers are included