We setup vsftp on an Ubuntu server for our customers. We had a few customers ask for a secure option, so we setup explicit FTP over TLS and we removed the ability to connect unsecured. Now we are having customers ask how they can connect using the Windows command line FTP client, for which they have already created automated scripts around. Is it possible to use the Windows command line FTP client to connect to an FTP server that requires explicit TLS? We have searched the web and it seems that the solution is to use another client, such as FileZilla, but some of our customers do not want to use another client. We also do not want to force them to use another client. Maybe TLS isn't the best option for secure FTP?
Dan Polites's questions
I've been stuck on this FTP issue for a while now. I have IIS 7 setup with an IIS 6 FTP server running on a Windows Server 2008 box. The problem I am running into is that I can't download certain files from the FTP server, even though I uploaded those files to the FTP server. The connection times out after 120 seconds. I have used Wireshark and checked the log files. The only message I see is the timeout message. The first thing that came to my mind was permission issues, however I have probably tried every combination of permissions that I can think of, with the end goal of getting the permissions to be the same for the files that work and the files that do not work. With the list of files I have now, I can download the zip, war, and msi files, but not the txt or sql files. It almost seems like a binary thing, but I've changed my transfer mode on the FTP client and also toggled the Active/Passive options around.
I have a 2950 blade server setup with Red Hat 4.6 installed. I cannot get the NIC to work properly after reinstalling Linux. I activated the NIC, but the NIC light will not turn on when I plug the network cable into the hub. The status light on the hub will not turn on either. If I run ifconfig, the NIC status is UP. Also I can ping the IP address that I assign to the Linux machine, but I can't ping anything else that is plugged into the hub. When I reboot the system, the NIC light will stay on until the system fully boots and then it will turn off again. Is there something else that I need to do to get the NIC working? It appears to be disabled even though ifconfig says that it is UP. Maybe I need to configure something within the blade server (iDRAC)?