Tag Info

Hot answers tagged

3

Check the firewall on the client machine, or set the mode to passive. There are actually two separate connections, a data channel and a command channel. It's common for the data channel to be blocked by the client machine's firewall. This Stack Overflow answer explains it well. The comment thread above reminds me that I should probably point out ...


2

I debated deleting this, the mods might still do so, but I figured out my issue. figured it might help someone later down the road... ECHO myuser >>ftp.scr ECHO mypassword >>ftp.scr The space between the name/password and the >> was the issue. Once I changed it to: ECHO myuser>>ftp.scr ECHO mypassword>>ftp.scr It worked fine!


2

telnet myip 21 If the connection succeeds you have probably a ftp server listening, which will give you a welcome message which usually contains the version. Also, netstat -nplt helps to see, what listing sockets you have, something listening on port 21 is usually a FTP server.


2

Can't be done in DNS as DNS had no concept of ports and FTP had no concept of hosts. You could do it by binding each FTP server to a separate address if you have multiple. If not, thing get complex. Theoretically You might be able to run a sort of ftp proxy to forward based on login credentials (but then why not just configure 1 ftp server) or hack ...


1

Dealing with these types of problems can be difficult because the logs usually tell you only part of what is happening. Your best bet at this point is to use a packet capture and analysis software (like the most excellent - and free - wireshark) to see what is really going on the wire. Make sure you capture all the traffic between your machine and the ...


1

A flaky network cable shouldn't cause the transfer to stall permanently. If the problem was a network cable, the transfer should resume when connectivity was restored. The connection may break if the network connection is lost for long enough for the TCP connection to time out, which will take several minutes. The symptoms you describe are however ...


1

It's likely the most simple solution would be for you to use rsync over ssh. This requires that each user have an account on the server. For this example, assume that they're wanting to copy files from their local machine, /home/user1/folder to /home/user1/foo on the server. To do this, they'd run the following from their workstation: $ rsync -avz ...



Only top voted, non community-wiki answers of a minimum length are eligible