Hi All,
I think Windows 2016 is a end game for GENE6FTP. It is not running on it even with DEP configuration. Is anyone have any idea on migration from GENE6 to any other FTP server with the same functions and possibility to decrypt passwords from ini files?
Gene6 FTP Server is an advanced FTP server software for Windows developed specifically for security and high performance requirements. Gene6 FTP Server is a professional Windows FTP Server featuring speed, reliability and customization. Its main assets are remote administration, encrypted (SSL 128 bits) connection, and ease of use. Its fast performances allow it to run heavily loaded files servers worldwide but this does not make it out of range of smaller companies who will find in it a customizable, trustable and easy to administer FTP server at an affordable price.
So, I can connect without issue and list directories on the FTPS server when I connect to the server while I am connected to the LAN (actually, RDP'd into the Win 2k8 box, you get the idea), but when I try to connect remotely to the FTPS site I can't seem to list the home directory of the user that I have configured on the server
Now, I am well aware that FTP requires both a DATA (TCP/20) and SESSION (TCP/21) port to be opened, but considering I am not using port 21 - how do I determine what data port I am using considering I am using port 990 over SSL (FTPS)?
I have opened port 20, port 21 and port 990 as a test on both the internet facing firewall and the windows server firewall but I still can't get a directory listing when I connect over the internet. I have attempted to connect using both ACTV and PASV methods in Filezilla and still no dice. I remember back in the day that this sort of issue is usually due to active and passive connections, but the details are murky in my mind. And if this was all due to active or passive, why would I be able to get a directory listing when I connect from the LAN side of the network?
Additionally, the FTP server will/should have a place in its passive setup to specify the outside IP address (not sure about G6, but FileZilla offers an IP resolver service for dynamic IPs as well), this will also need to be provided.
We need to move off traditional FTP for security purposes (it transmits it's passwords unencrypted). I am hearing SSH touted as the obvious alternative. However I have been driving FTP from an ASP.NET program interface to automate my web-site development, which is now quite a highly web-enabled process.
The secure version of old FTP exists - it's called FTP/SSL (plain old FTP over SSL encrypted channel). Maybe you can still use your old deployment infrastructure - just check whether it supports the FTPS or FTP/SSL.
When you choose whether to use SFTP or FTPS you have to deploy the proper server. For FTP/SSL we use the Gene6 ( ) on several servers without problems. There is plenty of FTP/SSL Windows servers so use whatever you want. The situation is a bit more complicated with SFTP server for Windows - there is only a few working implementations. The Bitvise WinHTTPD looks quite promising ( ).
Last part of the solution is secure file transfer from asp.net. There is several components on the market. I would recommend the Rebex File Transfer Pack - it supports both FTP (and FTP/SSL) and SFTP (SSH File Transfer).
The traditional secure replacement for FTP is SFTP, but if you have enough control over both endpoints, you might consider rsync instead: it is highly configurable, secure just by telling it to use ssh, and far more efficient for keeping two locations in sync.
I think it works great... and they have SQL and RDP - it was tough finding something that didn't have to be scripted and require 1/2 days work to install. I know it's $199, but to me for a 1 time license for a server.. it's an insurance policy because it's saving on bandwidth and resources..
Some of the FTP sites which I had have implemented TLS 1.2 on various linux systems, however I really needed to implement this on my G6 FTP which i still like to use and have found it a top performance FTP server on windows systems. So to do this we do the following:
Drop in OpenSSL >=1.0 (libeay32.dll, ssleay32.dll, libssl32.dll) as a replacement in your G6 installation directory, and add the following line to your settings.ini files for SSL-enabled FTP domains, you can find the files in the Accountsyourdomainname subfolders of your G6 FTP installation (scroll across for the full line to copy):
I know this is an old post (and old software); however, I appreciate your efforts to create it. When you have time, I would like to see if you could update it based on the latest OpenSSL files and cipher string.
Thanks again,
Ron
I suddedly got the error mentioned here when clients connect to a g6 ftp server.
-project.org/viewtopic.php?f=1&p=172705
It seems certificates created within the admin module are not properly signed.
I have tried my best to create this key and certificate using tools outside of the g6 ftp server, but when i put them in the G6 ftp server folder and select them for the domains I am no longer able to connect to the server.
Has anyone tried to create certificates for the server without using the buildin tool?
G6 FTP server is no longer supported by the developer, people should move away from it, as no patches have been provided for a few years or updates, and is a security risk if you run it exposed externally.
I am calling the Delete method on Rebex.Net.Ftp and am getting an error message of "Could not find source path ('File Name.txt').". It works without a problem if there is no space in the file name. I have tried quoting the file name in double/single quotes and prefixing the name with a slash (/) but none of this helps.
How can I use Rebex FTP to delete a file that contains a space? I have searched across the forums for someone facing the same issue but couldn't find an answer. I also had the same problem when using FileExists, but in that case I quoted the file name with double quotes and it started working. However the Delete method doesn't seem to obey the same rules.
This turned out to be a problem only with certain ProFTPD server (namely versions 1.3.2x and older which require the filename with spaces to be quoted when issuing the MLST command.)However, in newer versions of ProFTPd (1.3.3 and newer) the quoting workaround cannot be applied anymore.
We have improved the MLST quoting workaround to handle both scenarios based on the ProFTPD server version. The improved workaround is available as part of version 2014R3 version of Rebex FTP/SSL.
Thanks for the reply, changing the traversal mode from NonRecursive to MatchFilesShallow has solved the problem! Much appreciated. Is there a valid reason why NonRecursive wouldn't work with file names containing white space?
Well, TraversalMode.NonRecursive should make no difference. For me it is also working fine. Could you please create two logs using my code above - one with NonRecursive mode and another one with MatchFilesShallow mode?
For other users - from the logs we have received (thanks, DrBrain!) we have found, that ProFTPD server needs the filenames being quoted when issuing MLST command. The fix will be released as part of 2013R1. Hotfix is available on demand.
We just deployed Gene6 FTP Server onto our shared platform. It performs pretty well (1200-1300 sites per server), it's not expensive, and it has a COM API so you can script pretty much all of the configuration without too much fuss.
The two biggies are Filezilla (free) and Serv-U. I've had really good luck with both of them. Serv-U has gotten progressively more expensive over the years. I seem to remember it being really cheap at some point.
7fc3f7cf58