Datasets:

---

clips

/

mqa

like 52

Follow

CLiPS 10

[ { "text": "There is considerable confusion when using the term \"secure FTP\". There are two different types of secure file transfer protocols available. edtFTPnet/PRO supports both. \n\n \n\nFirstly, there is an enhancement to standard FTP (as defined in RFC 959), which uses the same FTP commands (and protocol) over secure sockets, i.e. over SSL/TLS. This is variously known as FTPS, FTP-SSL, and FTP-over-SSL. There are many FTP servers that support FTPS. \n\n \n\nThere is also another protocol, unfortunately known as SFTP, which also provides secure file access, but which is not related to the standard FTP protocol. This is implemented using SSH (Secure SHell), a suite of secure network connectivity tools (when used with SSH2 this is known as SFTP). The primary purpose of SSH is to enable users to remotely log into a machine over a secure connection. The two protocols are completely different and not related.", "name": "", "is_accepted": true } ]

[ { "text": "To retrieve the latest version number, the CompleteFTP manager must contact the enterprisedt.com webserver. If access is blocked on your machine to this server, the manager will display this error. To diagnose the problem, please examine the manager's debug log file - it should tell you what the issue is. See [here](https://enterprisedt.com/products/completeftp/doc/guide/html/howtogetdiagnostics.html) on how to obtain the log. \n\nApart from the URL being blocked, another possibility is that HTTPS is not working correctly. Our server requires the TLS 1.2 protocol to be used for HTTPS, and if the manager is being run on earlier versions of the .NET framework, TLS 1.2 will not be supported.  You'll see a message in the manager log about TLS 1.2 not being supported. For example, the .NET 4.0 framework does *not* support TLS 1.2 (it only supports TLS 1.1). To get the update function to work again, the machine the manager is running on, must be running the .NET 4.5 or .NET 4.6 frameworks.  In this case, you will need to update the .NET framework on the manager machine to either .NET 4.5 or .NET 4.6 (preferably the latter).\n\n", "name": "", "is_accepted": true } ]

[ { "text": "Yes, you can still use SSL 3.0 but as you say it isn't recommended. You'll need to open a support ticket to resolve this particular issue, see enterprisedt.com/support.", "name": "", "is_accepted": false } ]

[ { "text": "No, Microsoft's Internet Information Server (IIS) does not currently support SFTP or FTPS, but our completely FTP server, [CompleteFTP](http://www.completeftp.com), supports FTPS.\n\n", "name": "", "is_accepted": true } ]

[ { "text": "This sounds super interesting.  We'd be happy to work with you to get that going.\n\nI think there are two main hurdles: one is the authentication issue, which you mentioned, and the other is cross-site protection built into browsers.  Perhaps the best way to overcome both of these is to have your app act as a proxy for the CompleteFTP file-manager's API.  \n\nThe next version of CompleteFTP, 12.0.0, which is due out next month, will include a new file-manager.  It's an open-source fork of [angular-filemanager](https://github.com/joni2back/angular-filemanager).  The repository in on GitHub at [github.com/EnterpriseDT/completeftp-filemanager](https://github.com/EnterpriseDT/completeftp-filemanager).  The server-side API is written entirely in Javascript ([JSS](https://enterprisedt.com/products/completeftp/doc/guide/jssapi/index.html)).  It's invoked from the browser via JSON-RPC and all calls pass through a single point ([index.jss](http://github.com/EnterpriseDT/completeftp-filemanager/blob/master/index.jss)).  For example, a file-list request looks like this:\n\n\n```\n{\n \"method\": \"list\",\n \"id\":0,\n \"params\": {\n \"path\": \"/MyFiles\"\n }\n}\n```\nand the response looks like this:\n\n\n```\n{\n \"id\": 0,\n \"result\": {\n \"canWrite\": true,\n \"canRemove\": true,\n \"canRename\": true,\n \"files\": [{\n \"name\": \"file001.dat\",\n \"rights\": \"drwxr-xr-x\",\n \"size\": 79,\n \"date\": \"Wed, 17 Oct 2018 03:22:37 UTC\",\n \"type\": \"file\"\n }, {\n \"name\": \"file002.dat\",\n \"rights\": \"drwxr-xr-x\",\n \"size\": 37,\n \"date\": \"Wed, 17 Oct 2018 03:22:37 UTC\",\n \"type\": \"file\"\n }\n ]\n }\n}\n```\nI imagine that you could host all of the AngularJS code on your server and replace index.jss with your own code that acts as a dumb proxy, forwarding the requests to CompleteFTP and sending the responses back to the client.  To get the client code to call your URL instead of index.jss is done by changing the values in the values array defined on line 49 of [template.html](https://github.com/EnterpriseDT/completeftp-filemanager/blob/master/template.html).\n\nYou'll see that there's a login method in the API, so if the credentials for your app are the same as those for CompleteFTP, then you can perhaps just call that using the credentials that the user enters when logging into your app.  You could probably also use SAML if you like.\n\nAnd yes, CompleteFTP runs fine on Azure.\n\nHow does that sound?\n\n", "name": "", "is_accepted": true } ]

[ { "text": "Hi,\n\n*For edtFTPnet/PRO version 9.6.0:*\n\nFor SSL (FTPS & HTTPS) please see [here](https://enterprisedt.com/products/edtftpjssl/doc/api/com/enterprisedt/net/ftp/ssl/SSLFTPCipherSuite.html).\n\nFor SSH (SFTP & SCP):\n\nClient Algorithms: [diffie-hellman-group1-sha1, diffie-hellman-group14-sha1, diffie-hellman-group-exchange-sha1, diffie-hellman-group-exchange-sha256]\n\nClient Algorithms: [ssh-dss, ssh-rsa]\n\nClient Ciphers: blowfish-cbc,3des-cbc,aes128-cbc,aes192-cbc,aes256-cbc,aes128-ctr,aes192-ctr,aes256-ctr,arcfour\n\nClient HMACS: hmac-md5,hmac-md5-96,hmac-sha1,hmac-sha1-96,hmac-sha2-256,hmac-sha2-512\n\nSupported Compression Client-none,zlib,[email protected]\n\n", "name": "", "is_accepted": false } ]

[ { "text": "In the CompleteFTP Manager, under \n\n*SFTP Settings>Advanced SFTP Settings>Algorithms>Available Key Exchange Methods* \n\nclick in the box and deselect 'Diffie-Hellman-Group1-sha1' (key exchange). \n\nUnder \n\n*SFTP Settings>Advanced SFTP Settings>Algorithms>Available Ciphers*, \n\nclick in the box and deselect 'Blowfish-cbc' (cipher). \n\nBoth of these settings sometimes show up when a vulnerability scan is run, and are shown by some scans as 'deprecated'.\n\n", "name": "", "is_accepted": false } ]

[ { "text": "Please take a look at [CompleteBox](https://enterprisedt.com/products/completebox/), which is a client application for creating shareable links.\n\n", "name": "", "is_accepted": false }, { "text": "CompleteFTP's web-based [FileManager](https://enterprisedt.com/products/completeftp/doc/guide/filemanager_Overview) is able to [share files](https://enterprisedt.com/products/completeftp/doc/guide/filemanager_ShareFilePrivate) in the manner you're describing. If you need a user interface exactly like you're describing then you can develop it with CompleteFTP (see [here](https://enterprisedt.com/products/completeftp/doc/guide/jssoverview)). Our server-side scripting language is JSS, which is Javascript + an extensive [API](https://enterprisedt.com/products/completeftp/doc/guide/jssapi/index.html) for integrating with CompleteFTP and performing common operations. Although it's not currently documented, the API does allow integration with CompleteFTP's file-sharing system, allowing you to manage user shares, including creating new ones. We'd be happy to advise you on how to get started on your development project.\n\n", "name": "", "is_accepted": false } ]

[ { "text": "We sent the user some test code that did a similar task to what CompleteFTP was trying to do - fetch the local user list. \n\n \n\nThey successfully used this code to diagnose the issue:\n\n\n\n> \n> I have managed to get sufficient error information to identify the cause of our problem using a modified version of the code you provided.   The Workstation Service was disabled on our Servers to meet customers security requirements, however without this service the call to DirectoryEntry fails.\n> \n> \n> Thank you for your help, this issue may now be closed.\n> \n> \n> \n\n", "name": "", "is_accepted": true } ]

[ { "text": "You need to reactivate the server from within the CompleteFTP manager using your [customer site](https://connect.enterprisedt.com) credentials. That should be all that is required.\n\n", "name": "", "is_accepted": true } ]

[ { "text": "CompleteFTP supports SSL 3.0, and TLS 1.0, TLS 1.1 and TLS 1.2.", "name": "", "is_accepted": false } ]

[ { "text": "To download from CompleteFTP using wget requires two steps (for files that require username/password). \n \nCompleteFTP uses a session id, stored as a cookie. Clients must first obtain the cookie, and then authenticate using that cookie. By default, wget sends the authorization header in the first request (before the cookie is sent). This never works, as the cookie is not sent to the server with the auth header. CompleteFTP assumes this is an expired session. \n \nSo wget must be run twice, first to get the cookie, and then again using the retrieved cookie:\n\n\n> **wget --save-cookies cookies.txt --keep-session-cookies <http://myurl> \n> wget --load-cookies cookies.txt --http-user=username --http-password=pwd <http://myurl>**\n> \n> \n\n \nThis only works in **wget version 1.12 or later** since earlier versions don't save the cookie if there's an authentication error.\n\n", "name": "", "is_accepted": true } ]

[ { "text": "You can compare features [here](http://www.enterprisedt.com/products/completeftp/editions.php).\n\n", "name": "", "is_accepted": false } ]

[ { "text": "The ciphers that are mainly used for TLS 1.2 are:\n\nTLS\\_ECDHE\\_RSA\\_WITH\\_3DES\\_EDE\\_CBC\\_SHA,  \nTLS\\_ECDHE\\_RSA\\_WITH\\_AES\\_128\\_CBC\\_SHA,  \nTLS\\_ECDHE\\_RSA\\_WITH\\_AES\\_256\\_CBC\\_SHA\n\nWe plan on adding the GCM ciphers in the next release.\n\n", "name": "", "is_accepted": false } ]

[ { "text": "I'm going to assume that you're using FTP or FTPS, since you don't really say. \n\n \n\nThere are no defaults for FTP. The problem is that the FTP protocol doesn't deal with permissions, so there are no commands for handling them nor even any rules for what the defaults are supposed to be. It's therefore up to each individual server to determine how they should be handled, which is done via SITE commands. \n\n \n\nSFTP does have permission commands and rules, so if you were to use that protocol (which our client supports) then you'd have some options. \n\n \n\nHaving said that, I don't see why upgrading edtFTPj/PRO to a more recent version should break anything, so if it worked with the old client then it should work with the new client.", "name": "", "is_accepted": false } ]

[ { "text": "At the time of writing, Okta's IDP metadata doesn't include the identifier that CompleteFTP uses to differentiate between multiple IDP's. In order to work around this problem, it's necessary to manually edit the metadata to insert this identifier, called the 'entity ID'.\n\nTo do this, you must first obtain the entity ID from Okta. This is available on the page shown when you press the 'View Setup Instructions' button in the 'Sign On' tab of the admin page for your application on the Okta website. To make things even more difficult, there's a space missing, so that the entity ID runs together with the last word preceding it, i.e. \"The Identity Provider Issuer isXYZ\", where XYZ is the entity ID. Be careful to only copy the entity ID when you copy it to the clipboard.\n\nNow download the metadata XML file and open it in a text editor. The second line begins:\n\n\n```\n<md:EntityDescriptor\n```\nInsert the following immediately after this:\n\n\n```\nentityID=\"XYZ\"\n```\nwhere entity ID that you copied to the clipboard.\n\nOnce you've done this you can add it to CompleteFTP in the usual manner and it should work. Please contact [our support team](https://enterprisedt.com/help/) if it still doesn't work.\n\n", "name": "", "is_accepted": true } ]

[ { "text": "The [User Guide](https://enterprisedt.com/products/edtftpnetpro/doc/manual/index.html) provides comprehensive examples and documentation, but it's primarily a matter of setting the protocol:\n\n\n\n```\n\n?// Create SecureFTPConnection object\nSecureFTPConnection ftpConnection = new SecureFTPConnection();\n\n// setting server address and credentials\nftpConnection.ServerAddress = serverAddress;\nftpConnection.UserName = userName;\nftpConnection.Password = password;\n\n// select explicit FTPS\nftpConnection.Protocol = FileTransferProtocol.FTPSExplicit;\n\n// switch off server validation (unsafe - only do this when testing) ftpConnection.ServerValidation = SecureFTPServerValidationType.None;\n\n// connect to server\nftpConnection.Connect();\n```\n", "name": "", "is_accepted": false } ]

[ { "text": "This turned out to be a bug in version 8.5.0.  The fix will be released with the next version of CompleteFTP (probably 8.5.1).", "name": "", "is_accepted": false } ]

[ { "text": "Please try renaming the files. You might be able to use the full path of the file to get it moved to another directory. However this will depend on the server.", "name": "", "is_accepted": false } ]

[ { "text": "How about this:\n\n\n```\nfunction transferFiles() {\n try {\n ftp.connect();\n } catch (e) {\n console.log(\"There was an error with connecting \" + e);\n return;\n }\n}\n\ntransferFiles();\n```\n", "name": "", "is_accepted": false } ]

[ { "text": "FTP commands are initiated by the client, which opens a TCP connection called the control (or command) channel to the server. This control channel is used for the entire duration of a session between the client and server. A session typically begins when the client logs in, and ends when the quit command is sent to the server. The control channel is used exclusively for sending FTP commands and reading server replies - it is never used to transfer files. In FTP and FTPS this is usually port 21. \n \nFile transfers and directory listings use a separate, transient connection for each transfer or listing. The client issues a command to open a data connection (passive, using the PASV command, or active, using the PORT command). In passive mode, the server replies with a port number that the client must connect to for the data transfer. In active mode, the client sends a port number to the server, which connects back to it. \n \nNow firewalls are usually configured by default to allow TCP connections out or in on port 21. They are **not** configured by default to allow connections on the data ports. With FTP, this usually isn't an issue - the firewall inspects the control channel, sees the data port number that is sent, and automatically opens this port so the data connections are permitted. FTP users don't even notice. Note though that some firewalls may not do this automatically for FTP. \n \nUnfortunately, with FTPS this is not possible - the control channel is encrypted and the firewall can't inspect it to obtain the data port numbers to open. So the data connection fails, even though the user can login and issue commands. \n \nThe only solution to this is to configure the firewall to open the data port numbers permanently. FTPS servers must be configured to only use a fixed range of data port numbers, and these are set up in the firewall. If active mode is used, clients must be similarly configured to use a fixed range of port numbers.\n\n", "name": "", "is_accepted": true } ]

[ { "text": "When we're asked to troubleshoot a problem, we often ask users to send us a 'clean debug log'. What we mean by 'clean debug log' is a log file that contains, as far as possible, only information related to the problem at hand. \nThe steps for producing a 'clean debug log' are as follows: \n**SHORT VERSION:**\n\n1. Set the logging level to Debug\n2. Stop the CompleteFTP service\n3. Delete the existing log file\n4. Start the CompleteFTP service again\n5. Reproduce the error\n6. Send us the (zipped) log file\n\n \n**LONG VERSION:**\n\n1. **Set the logging level to Debug:**\n\t1. Open CompleteFTP Manager and connect.\n\t2. Select Logs from the menu.\n\t3. Set the Logging level to 'Debug' and click 'Apply Changes'.\n\t4. Close CompleteFTP Manager.\n2. **Stop the CompleteFTP service:**\n\t1. Open the Services item in the Windows Control Panel.\n\t2. Select CompleteFTP and hit the stop button.\n3. **Delete the existing log file:**\n\t1. Select 'Log Files' from the CompleteFTP start menu.\n\t2. Find 'Diagnostics.log' and delete (or rename) it.\n4. **Start the CompleteFTP service again:**\n\t1. Open the Services item in the Windows Control Panel.\n\t2. Select CompleteFTP and hit the start button.\n5. **Reproduce the error:**\n\t1. Do whatever it was that caused the error. E.g. connecting with an SFTP client and getting an error.\n6. **Send us the (zipped) log file:**\n\t1. Select 'Log Files' from the CompleteFTP start menu.\n\t2. Zip up the Diagnostics.log file and e-mail it to us\n\nIf you are having difficulty getting the manager to connect, see this FAQ: \n<http://www.enterprisedt.com/forums/viewtopic.php?t=4230>\n\n", "name": "", "is_accepted": true } ]

[ { "text": "Please ensure that:\n\n1. The path of the /Public folder in CompleteFTP Manager is C:\\ProgramData\\Enterprise Distributed Technologies\\Complete FTP\\Public\n2. The directory, C:\\ProgramData\\Enterprise Distributed Technologies\\Complete FTP\\Public, contains a file called index.html, as well as some other files.\n", "name": "", "is_accepted": true }, { "text": "Does the directory, C:\\ProgramData\\Enterprise Distributed Technologies\\Complete FTP\\Public, contain a file called index.html ?", "name": "", "is_accepted": false } ]

[ { "text": "Almost all servers are supported - email support if yours is not and we'll do our best to add support for it.", "name": "", "is_accepted": true } ]

[ { "text": "Please login to your account [here](https://connect.enterprisedt.com/#/downloads/products) , where you will be able to download the version you require. Please be aware that some versions may not be available if you have not renewed support for the license.\n\n", "name": "", "is_accepted": false } ]

[ { "text": "Please enable logging at the Debug level and post a relevant log snippet. We will probably move this thread into the edtFTPnet/PRO forum.", "name": "", "is_accepted": false }, { "text": "Bruce -\n \n Did you find any particular info on this topic?", "name": "", "is_accepted": false }, { "text": "Bruce - any new light on this subject", "name": "", "is_accepted": false }, { "text": "The error in your log is an authentication failure. So you are providing an invalid private key for the user, or the user's public key is not registered on the server.", "name": "", "is_accepted": false }, { "text": "Yes, I understand the problem but, when this occurs sFTP stays connected to the server Reflections session and does not return control to the client application. This, in effect, simulates a lock up instead of recording the error and returning control to the client application thru DCOM. I built a C# component that negotiates the communication between the client foxpro application and EDT server application. I cannot figure out the property I need to use to get EDT to relase control back to my client application facilitating a failure to connect error. I was inquiring which property to use to get EDT to release its memory segment so that the foxpro client can continue its processing.", "name": "", "is_accepted": false }, { "text": "Can you please post your code? If you are handling any event from our components, please post those as well.\n \n\n \n- Hans (EnterpriseDT)", "name": "", "is_accepted": false }, { "text": "\n```\nusing System;\nusing System.Runtime.InteropServices;\n\nnamespace EnterpriseDT\n{\n    //[ClassInterface(sftp.AutoDual)]\n    //[ProgId(\"EnterpriseDT.SecureFTPConnection\")]\n    [Guid(\"75C37F9E-A0E7-4004-8E56-95C00AD29843\")]\n    //[ComVisible(true)]\n    public interface SFTPTransfer\\_Interface\n    {\n        [DispId(1)]\n        void upLoadFile(string targetAddress, string targetFilePath, string sourceFilePath, string result);\n        [DispId(2)]\n        string[] GetFiles();\n        [DispId(3)]\n        void Connect();\n        [DispId(4)]\n        void Close();\n        [DispId(5)]\n        string ServerAddress{ get; set; }\n        [DispId(6)]\n        string UserName{ get; set; }\n        [DispId(7)]\n        string Password { set; }\n        [DispId(8)]\n        bool IsConnected { get; }\n        [DispId(9)]\n        int portUsed { get; set;  }\n        [DispId(10)]\n        void InitializeComponent(string PrivateKeyLocationAndFileName, string PrivateKeyPassphrase, string sLogFileName);\n        [DispId(11)]\n        void addknownHostFile(string HostName, string publicKeyLocation);\n        [DispId(12)]\n        void deleteFileFromServer(string targetFilepath, string strfilename);\n    }\n    [Guid(\"6AC80E65-5BC9-4443-B64B-95F5FC193744\"),\n    ClassInterface(ClassInterfaceType.None)]\n    public class SecureFTPConnection : SFTPTransfer\\_Interface\n        {\n            public SecureFTPConnection()\n            {\n//                EnterpriseDT.Net.Ftp.SecureFTPConnection.LogLevel = EnterpriseDT.Util.Debug.LogLevel.All;\n//                EnterpriseDT.Net.Ftp.SecureFTPConnection.LogFile = @\"Logs\\ftplogfile.log\";\n            }\n            private EnterpriseDT.Net.Ftp.SecureFTPConnection cxn;\n//                cxn = new EnterpriseDT.Net.Ftp.SecureFTPConnection();\n           \n\n            public string ServerAddress\n            {\n                get { return cxn.ServerAddress; }\n                set { cxn.ServerAddress = value; }\n            }\n\n            public string UserName\n            {\n                get { return cxn.UserName; }\n                set { cxn.UserName = value; }\n            }\n\n            public void addknownHostFile(string HostName, string publicKeyLocation)\n            {\n                cxn.KnownHosts.AddKnownHost(HostName, publicKeyLocation);\n            }\n\n             public int portUsed\n            {\n                get { return cxn.ServerPort; }\n                set { cxn.ServerPort = value; }\n            }\n\n            public bool IsConnected\n            {\n                get { return cxn.IsConnected ; }\n            }\n\n            public string Password\n            {\n                get { return cxn.Password; }\n                set { cxn.Password = value; }\n            }\n\n            public void Connect()\n            {\n                cxn.Connect();\n            }\n\n            public string[] GetFiles()\n            {\n                return cxn.GetFiles();\n            }\n\n            public void Close()\n            {\n                cxn.Close();\n                cxn = null;\n                EnterpriseDT.Net.Ftp.SecureFTPConnection.LogLevel = EnterpriseDT.Util.Debug.LogLevel.Off;\n                EnterpriseDT.Net.Ftp.SecureFTPConnection.LogFile = null;\n            }\n\n           public void deleteFileFromServer(string targetFilepath, string strfilename)\n           {\n               if (cxn.DirectoryExists(targetFilepath))\n               {\n                   cxn.ChangeWorkingDirectory(targetFilepath);\n                   if (cxn.Exists(strfilename))\n                   {\n                      cxn.DeleteFile(strfilename);\n                   }\n               }\n           }\n\n            private void setupParms(string sLogFileName)\n            {\n                EnterpriseDT.Net.Ftp.SecureFTPConnection.LogLevel = EnterpriseDT.Util.Debug.LogLevel.All;\n                EnterpriseDT.Net.Ftp.SecureFTPConnection.LogFile = sLogFileName;\n            }\n\n            public void upLoadFile(string targetFile, string targetFilePath, string sourceFilePath, string results)\n            {\n                /*if (cxn.DirectoryExists\n```\n", "name": "", "is_accepted": false }, { "text": "Hi Alan\n \n\n \nI suggest logging messages before and after you call our connect method, i.e.\n \n\n```\npublic void Connect() \n{ \n    try\n    {\n        log.Debug(\"Connecting\");\n        cxn.Connect(); \n        log.Debug(\"Connected\");\n    }\n    catch (Exception e)\n    {\n        log.Error(\"Connection error\", e);\n        throw;\n    }\n}\n```\n \nwhere log is defined as \n\n```\nLogger log = EnterpriseDT.Util.Debug.Logger.GetLogger(\"COMSecureFTPConnection\");\n```\n\n \n\n \nThis is to confirm that it never exits the SecureFTPConnection.Connect() method.\n \n\n \n- Hans (EnterpriseDT)", "name": "", "is_accepted": false } ]

[ { "text": "Do you mean that this happens when you are FTPing files from your office, or that FTP to/from other sites fails when the VPN connection is open?\n \n\n \n\n> I use edtftpnet in my application to download files. I am using DSL at home. It works fine. However whenever I open VPN connect to my office, the edtftpnet will throw exception in methods SendCommand line \"return ReadReply();\". If I disconnect VPN. It works fine again. \n> \n> I am not sure how to fix this exception. \n> \n> Thanks.\n\n", "name": "", "is_accepted": false }, { "text": "When I ftp files from other sites when the VPN is open.\n \n\n \n\n> Do you mean that this happens when you are FTPing files from your office, or that FTP to/from other sites fails when the VPN connection is open? \n> \n> \n> > I use edtftpnet in my application to download files. I am using DSL at home. It works fine. However whenever I open VPN connect to my office, the edtftpnet will throw exception in methods SendCommand line \"return ReadReply();\". If I disconnect VPN. It works fine again. \n> > \n> > I am not sure how to fix this exception. \n> > \n> > Thanks.\n> \n> \n\n", "name": "", "is_accepted": false }, { "text": "All I can think of is that you having some kind of routing problem. Try running traceroute to the remote FTP site to see how the packets are getting there.\n \n\n \n\n> When I ftp files from other sites when the VPN is open. \n> \n> \n> > Do you mean that this happens when you are FTPing files from your office, or that FTP to/from other sites fails when the VPN connection is open? \n> > \n> > \n> \n> \n\n", "name": "", "is_accepted": false } ]

[ { "text": "We do offer a 10% discount for Non-profit Organizations and Charities, but only if the purchase is carried out direct through EnterpriseDT, and not through a third party re-seller.", "name": "", "is_accepted": false } ]

[ { "text": "Yes, that's fine - there are no runtime restrictions for using edtFTPj/PRO.", "name": "", "is_accepted": true } ]

[ { "text": "There's a method for setting the character set for the control connection.", "name": "", "is_accepted": false } ]

[ { "text": "This question was previously asked and answered [here.](https://enterprisedt.com/questions/index.php/2872/the-trial-period-has-expired-how-can-i-extend-it)\n\nPlease do not post the license URL online. Please only use email or our support portal. I have replied regarding this by email to your email address.\n\n", "name": "", "is_accepted": false } ]

[ { "text": "Set the SSHMaxPacketSize to 32,000.", "name": "", "is_accepted": false }, { "text": "\n> Set the SSHMaxPacketSize to 32,000.\n\n\n \n\n \nThanks Bruce... All that grumbling around and tinkering and you were able to solve it in 2 seconds. I knew it was probably a setting on the command object.... Just didn't know which property to use! Again, thanks.", "name": "", "is_accepted": false } ]

[ { "text": "We really need a debug log for this. Please set 'All' level logging as shown [here](https://enterprisedt.com/products/edtftpjssl/doc/manual/index.html), and then open a support issue [here](https://enterprisedt.atlassian.net/servicedesk/customer/portal/1).\n\n", "name": "", "is_accepted": false } ]

[ { "text": "Yes, TLS 1.2 has been supported since 8.4.0 (current version at time of writing is 10.0).", "name": "", "is_accepted": false } ]

[ { "text": "Most likely a firewall closing the data connection for the transfer.", "name": "", "is_accepted": false } ]

[ { "text": "It sounds like the server is failing to acknowledge the client’s request to close the connection. The Close method has an override that takes a boolean argument. If you pass true for this argument then the client doesn’t wait for the server’s response before closing the connection. This should fix your problem. Although the protocol specification does state that the client should wait for a response before closing the socket, we’ve never encountered a server that enforces this, so it should be completely safe to close it without awaiting a response.\n\n", "name": "", "is_accepted": false } ]

[ { "text": "Microsoft has publicly released a [hotfix](http://support.microsoft.com/kb/2754804). They imply that the fix will be included in a general software update in the future:\n \n\n> if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.\n\n\n \n\n \n- Hans (EnterpriseDT)", "name": "", "is_accepted": true } ]

[ { "text": "I don't know what the problem is, but some suggestions:\n \n\n \n1. Supply an email address as password for anonymous\n \n2. Try the identical commands in a command-line client\n \n3. Post the stack trace for us to look at\n \n\n \n\n> ok, I've managed to cobble together the following test program: \n> \n> ```\n> import java.io.*;\n> import com.enterprisedt.net.ftp.*;\n> \n> public class ftptst {\n>     public static void main(String[] args)\n>         throws IOException, FTPException\n>     {\n>         // FTPClient ftp = new FTPClient(\"192.168.0.2\");\n>         FTPClient ftp = new FTPClient(\"ftp.arix.com\");\n>         ftp.login(\"anonymous\", \"\");\n> \n>         String[] list = ftp.dir();\n>         print(list);\n> \n>         ftp.quit();\n>     }\n> \n>     private static void print(String[] list) {\n>         System.out.println(\"Directory listing:\");\n>         for (int i = 0; i < list.length; i++)\n>             System.out.println(list[i]);\n>         System.out.println(\"Listing complete\");\n>     }\n> }\n> \n> ```\n> \n> but when I run it I get the exception shown in the subject of this posting.. as is evident, I've tried the FTPClient() constructor with \\_both\\_ a name and an IP address. what is wrong with the code? (yes I do have an ftp server at that address) \n> \n> please e-mail me ([[email protected]](mailto:[email protected])). thx - ekkis\n\n", "name": "", "is_accepted": false } ]

[ { "text": "You need a CSR to obtain a trusted certificate from one of the many certificate providers. \nFrom 6.4.0, CompleteFTP supports generation of CSRs from within the CompleteFTP Manager. \nMore details can be found in the User Guide, [here](http://www.enterprisedt.com/products/completeftp/doc/guide/html/howtocsr.html). \nMake sure you keep your private key securely! The CSR can be sent to the certificate authority (CA) that you have chosen to use. The private key is NOT sent to the certificate authority. \nBefore you send the CSR to your chosen CA, you can validate it by pasting it into [Verisign's CSR checker](https://ssl-tools.verisign.com/checker). \nWhen you get the certificate issued, for InstantSSL choose the \"OTHER\" format.\n\n", "name": "", "is_accepted": true } ]

[ { "text": "I'm not sure why you needed to recode chdir()? CD isn't an FTP command, that's probably why it is not understood by the server.\n \n\n \n\n> Hi, \n> \n> I am using your FTPClient in my project to make an automatic ftp update. I have a problem. \n> \n> I have recoded your chdir method to use CD instead of CWD. The problem is that even though everything seems fine when I debug, I can never get the chdir command to work. The response code I get is the same as when I test on a DOS ftp client and use a quote command instead of a CD command directly ('CD ': command not understood). \n> \n> Do you have a tip to how I can overcome this problem? \n> \n> \n> Thanx, \n> \n> Morten\n\n", "name": "", "is_accepted": false }, { "text": "Thank you for you quick reply :)\n \n\n \nI tried with the CWD command that was in the code originally but that also failed. The reason seems to be that my FTP server doesn't support this. In the list of commands I get when typing help includes CD but not CWD.\n \n\n \n\n \nMorten", "name": "", "is_accepted": false }, { "text": "I have included some more info here:\n \n\n \nI am not sure of the make of the FTP server, but here is the welcome message:\n \n\n \n**220 FTP server (Version 5.311PWS/AI) ready**.\n \n\n \nHere are the available commands:\n \n\n \n**! delete literal prompt send \n? debug ls put status \nappend dir mdelete pwd trace \nascii disconnect mdir quit type \nbell get mget quote user \nbinary glob mkdir recv verbose \nbye hash mls remotehelp \ncd help mput rename \nclose lcd open rmdir**[/b]", "name": "", "is_accepted": false }, { "text": "The available commands look like the client-side commands, not the server ones.\n \n\n \nThe best way to find out the FTP server commands is to ftp to it via a command line tool (e.g. ftp in Windows).\n \n\n \nOnce logged in, type \n \n\n \ndebug\n \n\n \nto get into debug mode.\n \n\n \nThen cd to a directory, you'll see something like\n \n\n \n--> CWD directory\n \n\n \nappear as all commands sent to and from the server are shown in debug mode.\n \n\n \nThis should show you what command is actually sent when you cd\n \n\n \n\n \n\n> I have included some more info here: \n> \n> I am not sure of the make of the FTP server, but here is the welcome message: \n> \n> **220 FTP server (Version 5.311PWS/AI) ready**. \n> \n> Here are the available commands: \n> \n> [/b]\n\n", "name": "", "is_accepted": false } ]

[ { "text": "By default all data used by CompleteFTP is stored in a subdirectory of ProgramData (Vista/2008 and later) or the \"All Users\" data directory (Windows XP/2003 and earlier), so backing up this directory is all that is required. \n \nIf you have set up the virtual file-system to access any other directories then of course these must be backed up separately. \n \nOn Windows XP/2003 and earlier:\n\n\n```\nC:\\Documents and Settings\\All Users\\Application Data\\Enterprise Distributed Technologies\\Complete FTP\n```\nOn Vista/2008 and later:\n\n\n```\nC:\\ProgramData\\Enterprise Distributed Technologies\\Complete FTP\n```\nTwo other ways to locate the directory: \n \n1. Open Windows Explorer and type \"%ALLUSERSPROFILE%\\Enterprise Distributed Technologies\\Complete FTP\". \n \nOR \n \n2. From the Windows Start menu open \"CompleteFTP\" and then \"Log Files\". This opens the Logs directory in Windows Explorer. Go up one directory.\n\n", "name": "", "is_accepted": true } ]

[ { "text": "Powershell now includes an SSH client, so you can ssh to the Admin site as described [here](https://enterprisedt.com/products/completeftp/doc/guide/html/commandadmin.html) and run commands such as **useradd**. \n\n", "name": "", "is_accepted": false } ]

[ { "text": "You need to write a class that implements the FTPProgressMonitor interface, e.g. MyProgressMonitor implements FTPProgressMonitor ....\n \n\n \nThen\n \n\n \nFTPProgressMonitor monitor = new MyProgressMonitor();\n \nftp.setProgressMonitor(monitor, 2048);\n \n\n \nmonitor.bytesTransferred() will be called every 2048 bytes transferred.\n \n\n \n\n \n\n> Hi, \n> \n> how can I use the progressbar? \n> Do you have an example? In the test-files I found something like: \n> \n> ftp.setProgressMonitor(new TestProgressMonitor(), 2048); \n> \n> This does not work. Did I forget to import something or where is the problem? \n> \n> Thanx for an answer! \n> \n> S\n\n", "name": "", "is_accepted": false }, { "text": "Thanx very much.", "name": "", "is_accepted": false } ]

[ { "text": "Use a full path for the local file.", "name": "", "is_accepted": false } ]

[ { "text": "Hi, \n\n \n\nYou should really update the software. Running old versions of software can be a security risk. We are now at CompleteFTP version 13.1.0. \n\n \n\nYou can set the minimum TLS which should be used under: \n\n \n\n settings (or sites) > HTTP/HTTPS > Advanced HTTP/HTTPS settings > Security Settings (also used in FTPS) > Minimum SSL Version > set the value to TLS 1.2 \n\n \n\nPlease note that setting this value to TLS 1.2 will only allow clients to connect to the server who are also running TLS 1.2. If any of your clients use older legacy machine which only support TLS 1.0. or 1.1 then they will no longer be able to connect to CompleteFTP.", "name": "", "is_accepted": false } ]

[ { "text": "With a bit of guidance from EnterpriseDT, the user was able to solve this problems successfully and, very generously, offered to share his solution with other CompleteFTP users. This is what he wrote:\n\nThis can be done using the following procedure:\n\n1. Must install [SQL Server Compact 3.5 SP2](https://www.microsoft.com/en-us/download/details.aspx?id=5783). I then chose to copy the relevant DLL to my working folder, but you could point it to the installed location of that DLL.\n2. In [this Powershell script](https://enterprisedt.com/uploads/files/InstallCertificate.txt) below, the top section has the items that must be tailored to the environment (mostly file locations)\n3. This assumes that the ACME process (I used win-acme) had already been set up and that you chose to store the PFX file somewhere available to this script. At the end of the win-acme process, it then prompts you to run a script as an installation step. That’s where you would call this script\n\n", "name": "", "is_accepted": false } ]

[ { "text": "If you enable logging at the Debug level and post the relevant snippet around this error that should explain the problem. It is probably incompatible versions of TLS.", "name": "", "is_accepted": false }, { "text": "As I mentioned before, what we need it", "name": "", "is_accepted": false }, { "text": "Here is the problem: \n \n\n> Local min SSL version: 3.1, max SSL version: 3.2 \n> Remote SSL version: 3.0 \n> \n\n \n \nSet the SSLVersion property to SSLFTPSSLVersion.SSL3", "name": "", "is_accepted": false }, { "text": "Thanks for the support.. \n \nIm starting to use this product... where do I have to \"Set the SSLVersion property to SSLFTPSSLVersion.SSL3\" ?? \n \nIt", "name": "", "is_accepted": false }, { "text": "All the documentation is installed with the product - take a look at the User Guide. \n \n\n```\nSecureFTPConnection ftp = new SecureFTPConnection();\nftp.SSLVersion = SSLFTPSSLVersion.SSL3;\n\n```\n", "name": "", "is_accepted": false } ]

[ { "text": "Yes, you can do this.\n\nPlease follow the instructions in [How to log to syslog](https://enterprisedt.com/products/completeftp/doc/guide/html/syslog.html), except in step 2 instead of pasting in the appender definition for Syslog, use the following appender definition:\n\n\n```\n`<appender name=\"Commands\" type=\"log4net.Appender.RollingFileAppender\">\n <encoding value=\"utf-8\" />\n <filter type=\"log4net.Filter.StringMatchFilter\">\n <stringToMatch value=\"CMD\" />\n <acceptOnMatch value=\"true\" />\n </filter>\n <filter type=\"log4net.Filter.StringMatchFilter\">\n <stringToMatch value=\"SSH_FXP\" />\n <acceptOnMatch value=\"true\" />\n </filter>\n <filter type=\"log4net.Filter.DenyAllFilter\" />\n <file type=\"log4net.Util.PatternString\">\n <converter>\n <name value=\"folder\" />\n <type value=\"EnterpriseDT.Util.Debug.SpecialFolderPatternConverter\" />\n </converter>\n <conversionPattern value=\"%folder{CommonApplicationData}\\Enterprise Distributed Technologies\\Complete FTP\\logs\\Commands.log\" />\n </file>\n <param name=\"AppendToFile\" value=\"true\" />\n <param name=\"RollingStyle\" value=\"Date\" />\n <param name=\"DatePattern\" value=\".yyyyMMdd\" />\n <layout type=\"log4net.Layout.PatternLayout\">\n <param name=\"Header\" value=\"\" />\n <param name=\"Footer\" value=\"\" />\n <param name=\"ConversionPattern\" value=\"%date{dd MMM yyyy HH:mm:ss} %message %newline\" />\n </layout>\n</appender>`\n```\nand instead of referencing Syslog in definition of <root>, use the following:\n\n\n```\n`<appender-ref ref=\"Commands\" />`\n```\nI have to warn you that running CompleteFTP with debug logging slows it down because I writes so much logging. I therefore recommend that you **only set it to Debug level when you’re trying to diagnose a problem** and leave it at Information otherwise.\n\n", "name": "", "is_accepted": true } ]

[ { "text": "Hi Kevin\n \n\n \n'chmod' is not part of the FTP standard (see <http://www.freesoft.org/CIE/RFC/959/23.htm>) so it would not be supported by many (any?) servers. Which server are you using?\n \n\n \n- Hans (EDT Support)", "name": "", "is_accepted": false }, { "text": "You can use quote() to send any command to an FTP server so this is a possible option for you.", "name": "", "is_accepted": false }, { "text": "thank you for your answers :-)\n \nit works fine with quote().\n \nI'm going to make the promotion of edtftpnet.\n \nThe control is great and the support efficient.\n \nRegards.\n \nKevin.", "name": "", "is_accepted": false } ]

[ { "text": "Use **getProxySettings()** to get a reference to the ProxySettings object and set its properties.\n\n", "name": "", "is_accepted": false } ]

[ { "text": "We've confirmed that this is a bug.  It will be fixed in the next release, which is due mid-April.  If you need a fix before that then we can send you a test build.  Please contact [support](https://enterprisedt.com/help) if you'd like a build.\n\n\nThank you for reporting this problem.\n\n", "name": "", "is_accepted": false } ]

[ { "text": "Could you email your config.sdf file to support at enterprisedt dot com?", "name": "", "is_accepted": false }, { "text": "\n> Could you email your config.sdf file to support at enterprisedt dot com?\n\n\n \n\n \nActually I resolved the issue myself in the end.\n \n\n \nThe windows user type was created when the file manager plugged in was not enabled so it seems that for that reason after I enabled the file manager plug in the user had no permission to access it.\n \n\n \nDeleting and re-adding the windows type user from complete ftp while the plug in was enabled seems to have fixed this. The plug in now works under the user.\n \n\n \nNirv80", "name": "", "is_accepted": false }, { "text": "have issues using the FileManager plug in for \"Windows\" type users. \n \nWhen I login I'm redirected to my home virtual folder via the standard listing templates, and all my subfolders work correctly, however I'm not redirected automatically to the /FileManager/ plugin. \n \nIf I manually try to enter the the the /FileManager/ plugin path I get the following error: :roll: :D :(", "name": "", "is_accepted": false } ]

[ { "text": "What protocol are you using? SFTP? Can you post more of the connection log leading up to the exception?", "name": "", "is_accepted": false } ]

[ { "text": "You can't. FIPS mode is not supported. More information is [here](https://enterprisedt.com/questions/index.php/2233/is-completeftp-fips-140-certified). \n\n", "name": "", "is_accepted": false } ]

[ { "text": "CompleteFTP's configuration file contains sensitive information such as password hashes and certificates. Accordingly, some filesystem security restrictions are applied to this file (typically C:\\ProgramData\\Enterprise Distributed Technologies\\Complete FTP\\config.sdf), and the associated backup directory (C:\\ProgramData\\Enterprise Distributed Technologies\\Complete FTP\\backup). Access is configured for Administrators, the default account for the CompleteFTP service (the local SYSTEM user) and the installer.\n\nUsers who have changed the 'log on' user of the CompleteFTP service from the default (i.e. local SYSTEM user) may need to manually configure Windows file permissions after installation by giving full control of the configuration file and backup directory to the new log on user.\n\n", "name": "", "is_accepted": true } ]

[ { "text": "So you only want 10 files from the listing? How do you know what files you want?", "name": "", "is_accepted": false } ]

[ { "text": "There shouldn't be any issues using edtFTPj/PRO with SysaxSSH.", "name": "", "is_accepted": false } ]

[ { "text": "There's a class called SSHFTPValidator that you can extend as described [here](https://enterprisedt.com/products/edtftpjssl/doc/manual/html/howtousesftpwithservervalidationauto.html). You override the validate method. In here you could check the keysize and return false if it isn't large enough. You are supplied with the SSHFTPPublicKey which has a method getBitLength().\n\n", "name": "", "is_accepted": true } ]

[ { "text": "People often ask us if CompleteFTP is FIPS-140 certified. \n \nThe answer is no, but from from version 6.3.0, CompleteFTP will run correctly when *Use FIPS compliant algoritms for encryption, hashing, and signing*, is enabled on the Windows machine it is installed on. Applications are permitted to disable FIPS compliance, and CompleteFTP does this so that it can still be run. \n \nKarl Levinson at SecLists.Org [outlines](http://old.nabble.com/Re%3A-How-important-is-FIPS-140-2-Level-1-cert--td8129113.html) the reasons why we have chosen not to pursue FIPS-140 compliance. \n \nThis quote explains the main reason why our products are not FIPS-140 certified:\n\n\n> FIPS certification is probably expensive and time consuming for the vendor, so that the products that get it would tend to be older products from larger, more monolithic companies, which may not necessarily guarantee you're getting superlative security.\n> \n> \n\nAnd here's an illustration of how FIPS-140 certification can actually result in a lower level of security:\n\n\n> With MS Windows, for example, you probably don't want to enable \"FIPS-compliant encryption mode,\" because an older, weaker encryption algorithm will be used for EFS disk encryption, rather than newer, stronger but uncertified protocols.\n> \n> \n\n- Hans Andersen (EnterpriseDT)\n\n", "name": "", "is_accepted": true } ]

[ { "text": "There are no immediate plans to do this. CompleteFTP uses the Linux model of permissions, which can handle most use-cases. If you describe your needs we may be able to suggest an alternative solution that doesn't rely on multiple groups.", "name": "", "is_accepted": false } ]

[ { "text": "Currently up to 20 log files are retained, 5 MB in size each. To keep log files longer, there are a few options. They are controlled via the service configuration file, which (depending on your installation) can be found at: \n \nC:\\Program Files (x86)\\Complete FTP\\Server\\CompleteFTPService.exe.config \n \nLook for the <log4net> section, and then the RollingFileAppenders. \n \nYou can do a number of things here: \n \n1. Increase MaxSizeRollBackups to a number higher than 20 \n \n2. Increase the MaximumFileSize \n \nAlternatively, you can \n \n3. Change the RollingStyle from Size to Date, and add a DatePattern, e.g. \n \n<param name=\"RollingStyle\" value=\"Date\" /> \n<param name=\"DatePattern\" value=\".yyyyMMdd\" /> \n \nIf you are more adventurous, you can investigate other [log4net](http://logging.apache.org/log4net/release/config-examples.html) configuration options. \n \nPlease note that the CompleteFTP service will need to be restarted after making any configuration file changes. \n \nNote also that all files in the *C:\\Program Files (x86)\\Complete FTP* directory are overwritten each time you install an update, so you'll need to reapply your modifications after installation.\n\n", "name": "", "is_accepted": true } ]

[ { "text": "All configuration data will be retained during the upgrade, but it is of course always a good idea to keep backups (see [here](http://enterprisedt.com/questions/index.php/2423/how-do-i-back-up-my-completeftp-data)). You can also test the upgrade on a different machine as explained [here](http://enterprisedt.com/questions/index.php/11604/how-can-i-test-that-a-new-release-works-for-my-server). \n\n\n \n\n**Instructions:**\n\n\n1. Download the latest version of CompleteFTP from our [customer site](https://connect.enterprisedt.com), using the link and login details you received after you purchased your license. If you don't have access to this then please [contact support](http://enterprisedt.com/support/contact/).\n2. Exit the CompleteFTP manager if it is running (no need to stop the CompleteFTP service).\n3. Install the new version.\n\n\nPlease note that **the trial distribution cannot be used to upgrade a licensed installation**.\n\n\nIf for some reason the upgrade fails, you can easily [roll back](http://enterprisedt.com/questions/index.php/11644/how-can-i-roll-back-to-an-earlier-version-of-completeftp) to the previous installation. \n\n", "name": "", "is_accepted": true } ]

[ { "text": "The only one which is supported from your list in version 9.1.2. is: \n\n \n\ndiffie-hellman-group-exchange-sha256", "name": "", "is_accepted": true } ]

[ { "text": "Details on how to use the license details that are emailed to customers can be found [here](http://enterprisedt.com/products/edtftpjssl/doc/manual/html/howtousethelicensefile.html).\n\n", "name": "", "is_accepted": true } ]

[ { "text": "Please see the User Guide [here](https://enterprisedt.com/products/edtftpjssl/doc/manual/html/howtosetuplogging.html) for details on how to enable logging in edtFTPj/PRO.\n\n", "name": "", "is_accepted": false } ]

[ { "text": "The [PCI DSS](https://www.pcisecuritystandards.org/documents/pci_dss_v2.pdf) (Payment Card Industry Data Security Standard) is the data security standard for the payment process industry. Developed and maintained by the major credit card companies via the PCI Security Standards Council, it is relevant for merchants, processors, acquirers, issuers and service providers. \nEssentially, PCI DSS is a set of minimum requirements designed to protect cardholder data. It has 12 major requirements, not all directly relevant to secure file transfer. FTP servers can't be PCI DSS compliant as such - they instead can help organizations to achieve PCI DSS compliance in conjunction with network security measures and policies and other technologies. \nWhen used correctly, CompleteFTP can help you achieve PCI DSS compliance in your organization. The PCD DSS requirements addressed by CompleteFTP are listed below: \n \n**Requirement 1: Install and maintain a firewall configuration to protect cardholder data** \n \nKeep your CompleteFTP installation behind a firewall. Use the IP filtering capabilities of CompleteFTP to only permit the IP addresses you want to access the server. \n \n**Requirement 2: Do not use vendor-supplied defaults for system passwords and other security parameters** \n \nDisable anonymous access. Configure the CompleteFTP manager to use a secure protocol such as SFTP or FTPS for administrative tasks. Disable HTTP and FTP protocols. For HTTPS, ensure public HTTP access flag is disabled. Hide the server product details (messages setting) to hide the version and name of the product from clients. \n \n**Requirement 3: Protect stored cardholder data.** \n \nDisable SSH terminal access. Periodically change keys. Where cardholder data is stored, encrypt it using PGP or a similar tool. \n \n**Requirement 4: Encrypt transmission of cardholder data across open, public networks.** \n \nDisable HTTP and FTP protocols, and only permit secure protocols: FTPS, SFTP and SCP. \n \n**Requirement 8: Assign a unique ID to each person with computer access.** \n \nDisable anonymous access. Disable automatic Windows users. \n \n**Requirement 10: Track and monitor all access to network resources and cardholder data.** \n \nCompleteFTP supports auto-banning of accounts or IP addresses that connect unsuccessfully. CompleteFTP has an audit log that should be regularly inspected.\n\n", "name": "", "is_accepted": true } ]

[ { "text": "No, there's no chance that edtFTPnet/PRO is creating a folder as a side-effect of uploading a file.  It's likely that there's some special functionality on the server that causes this behaviour.", "name": "", "is_accepted": true } ]

[ { "text": "Have you tried using a process trigger that triggers on the Uploaded event?", "name": "", "is_accepted": false } ]

[ { "text": "Hello \n\n \n\nI'd like to mention that my company has been using edtFTPnet/PRO as part of a product for downloading via SFTP, and we have also seen the same discrepancies in download speed.", "name": "", "is_accepted": false } ]

[ { "text": "TLS 1.2 has been supported since 5.0, for over 2 years.", "name": "", "is_accepted": false } ]

[ { "text": "The user signed certificate must be installed on the server to be of any use. The server sends the certificate to the client which verifies it using the PEM file supplied, which can either contain 1) the CA certificate the server cert was signed with, or 2) the actual server certificate. More information in the User Guide [here](https://enterprisedt.com/products/edtftpjssl/doc/manual/html/howtouseftpswithservervalidationparta.html). \n\n", "name": "", "is_accepted": false } ]

[ { "text": "On a machine without Internet access, you can either \n\n \n\n1) In the CompleteFTP manager's licensing panel's activation link you can copy the activation URL and use it on a machine with Internet access, and then copy the activation key back to the server machine. \n\n \n\nor \n\n \n\n2) Install the CompleteFTP manager on a machine that does have internet access and can also reach the server machine. Connect to the server machine with the manager and activate as normal.", "name": "", "is_accepted": false } ]

[ { "text": "I've never heard of that before, so, no, unfortunately that's not an option we've implemented.  However, SecureFileTransferClient is a high level, more user-friendly class that uses the lower level SSLFTPClient for all of the actual FTP operations (and SSHFTPClient for SFTP).  I suggest that you port your code from using SecureFileTransferClient to SSLFTPClient.  This gives you near-total control over which commands are sent to the server.", "name": "", "is_accepted": true } ]

[ { "text": "An SSL certificate must have an associated private key file, which is the PVK file if you generated the certificate request from CompleteFTP. It's possible you have a different type of private key file, or if your certificate is in PEM format it may even be in the certificate PEM file (open it and check). \n\n \n\nFrom version 12.1, CompleteFTP can directly import certificates in PEM format. If the certificate's private key is not included in the PEM file, you will be prompted for it. PEM private key files are also supported from 12.1.", "name": "", "is_accepted": false } ]

[ { "text": "I've fixed this code by calling ftpClient.dirDetails(directory) before ftpClient.cd(directory). Probably better anyway.", "name": "", "is_accepted": false } ]

[ { "text": "The key difference is that SecureFTPConnection also offers FTP/FTPS support, so you can switch between FTPS and SFTP by setting a property.  Along with that SecureFTPConnection offers more features like connection-pooling and asynchronous methods.  Behind the scenes, SecureFTPConnection actually uses SSHFTPClient for SFTP.", "name": "", "is_accepted": true } ]

[ { "text": "I think 0D0D0A isn't a standard character sequence for a text-file regardless of which platform you're on.  On Windows it could be interpreted as either one or two newlines and I think 0A isn't generally used in text-files on *NIX at all.  Since this character-sequence isn't defined you should expect various behaviours depending on the inclinations of the developers.  So I wouldn't really call it a bug in either platform.  It's more of a feature.  :-) \n\n \n\nTo avoid this discrepancy I'd probably either use binary transfer-mode or process the file prior to transfer.", "name": "", "is_accepted": false } ]

[ { "text": "Those events will only be triggered when Close is actually called. Is Close being called? They won't trigger if the connection just drops out.\n \n\n \n- Hans (EnterpriseDT)", "name": "", "is_accepted": false } ]

[ { "text": "Please open up a support ticket [here](https://enterprisedt.atlassian.net/servicedesk/customer/portal/1/group/1/create/1). \n\n", "name": "", "is_accepted": false } ]

[ { "text": "You can only use a gateway connection if you're authenticating your FTP users using accounts on the internal CompleteFTP server, so if the accounts of your users are defined only on the CompleteFTP server in your DMZ then you can't use a gateway connection.  So it boils down to where your accounts are stored - on the DMZ server or on the internal server. \n\n? \n\nA more in-depth explanation: \n\n? \n\n?If you're authenticating users using a gateway authenticator from accounts on your internal server then the DMZ server connects to the internal server as soon as a user tries to authenticate.  If authentication is successful then that initial connection between the DMZ server and the internal server is kept open for the duration of the session and is used when the user accesses a gateway folder.   \n\n? \n\n?If, on the other hand, the DMZ server is authenticating users itself (using accounts set up on that server), then no connection between the DMZ server and the internal server is opened initially.  When the user tries to access a gateway folder it has no existing 'gateway connection' available, so it must use a specified connection.  This specified connection must have the user-name and password of an account on the internal server set.", "name": "", "is_accepted": true } ]

[ { "text": "**The CompleteFTP manager won’t connect! How can I resolve this?**\n\n**Symptoms**\n\nWhen the CompleteFTP manager is launched, the 'Connect to CompleteFTP' dialog box should appear. After filling in the details and selecting OK, error messages appear such as :\n\n“*The CompleteFTP service is not currently running on this machine.Would you like to start it?*”\n\n“*Cannot connect to server: Authentication failed*”; \n\nThe manager application fails to progress any further.\n\n**How to resolve this:**\n\n1) If you are told that the service is not running, make sure the CompleteFTP service is started - it must be running in order to connect.  If the service is not running, start the service from the Services panel and make sure it shows as running. \n\n2) If you are not prompted but suspect the service is not running, then please access services using  Win+R  and type in  ‘services.msc’, or you can access it through the control panel>administrative tools>services. Search for Complete FTP Server, right click over it and choose ‘start’. \n\n3) The manager must be running with the correct permissions for the windows services, in order for it to connect to the server. If the manager is not running with the correct permissions for the Complete FTP Server (Service), then you will have to start it using one of the methods shown above (i.e. connect first to control panel>Administrative Tools>Services>Complete FTP Server>start).\n\n4) If the service is running but you still receive a message telling you it is not, you are probably connecting on the wrong server administrator port. By default, the admin port should be 14983. In very early versions, the default port was 14982. Please check that the correct port number has been entered (see image below).\n\n5) Check that the *correct* username and password have been entered in the connect dialogue box as shown below:\n\n\n\n6) If you have forgotten your password, then please go [here](https://enterprisedt.com/questions/index.php/2355/how-can-i-reset-the-administrator-password?show=2355#q2355) to see the steps on how to reset it.\n\n7) For this kind of problem we need to know what ports the server is listening on. Earlier versions of Complete FTP server used the FTP/FTPS protocol for manager connections on port 14982. Later and current versions use SFTP port 14983. Protocols used for connection may have been amended by your administrator and these can be seen by clicking on ‘*other settings*’>connection protocol>click on the drop down menu, and ensure the correct protocol has been entered. (See below image)\n\n8) Before contacting support it is useful to have a diagnostic ‘Manager’ log. To get this please go to ‘other settings’ on the ‘connect to Complete FTP’ window and choose ‘Full diagnostic (slow) - see below image. Then close it down again and attempt to reconnect. After these steps please go to  C:\\Users\\MyUserName\\AppData\\Local\\EnterpriseDT\\Complete FTP\\Logs\\Diagnostic.log You can check the log and search for ‘listener’ which should tell you which port number is set for connections from the CompleteFTP Manager.\n\n\n\nIf you are still unable to resolve this issue please send the latest 'Diagnostic.log' which covers your most recent connection attempt to support (You will need a current support agreement in place).\n\n", "name": "", "is_accepted": false } ]

[ { "text": "So you've loaded your SSL certificate obtained from your CA and are testing HTTPS. You start IE, and go to <https://localhost>. \n \nIE gives the message \"This organization's certificate has been revoked\", and you can't view the page at all. What's going on? \n \nWell, IE has very strict checking for HTTPS. If the SSL certificate's common name does not match the hostname of the server, IE will block access to the page on CompleteFTP. On a test machine, this will usually be the case. \n \nTo view the page (and the error message), you need to disable revocation in the Advanced Settings of IE's Internet Options. You need to disable two settings, \"Check for publisher's certificate revocation\" and \"Check for server certificate revocation\". \n \nOnce revocation is disabled, you will be given the option of continuing to the page - and the actual error message will be shown: \"The security certificate presented by this website was issued for a different website's address.\" \n \nYou won't get this problem when you deploy CompleteFTP on a machine where the hostname matches the certificate's common name. \n \nYou don't see this error in Chrome.\n\n", "name": "", "is_accepted": true } ]

[ { "text": "Please enable debug logging and take a look in the server log file: \n\n \n\nC:\\ProgramData\\Enterprise Distributed Technologies\\Complete FTP\\Logs\\diagnostics.log", "name": "", "is_accepted": false } ]

[ { "text": "Use the RollingFileAppender:\n\n\n```\nusing EnterpriseDT.Util.Debug;\n\nLogger.ClearAppenders();\nLogger.AddAppender(new RollingFileAppender(\"myfile.log\", 5000000, 10));\n\n```\nThat gives a max size of 5 MB with 10 log files.\n\n", "name": "", "is_accepted": true } ]

[ { "text": "If you follow the instructions [here](https://enterprisedt.com/products/edtftpjssl/doc/manual/html/howtosetuplogging.html) and record a debug level log of your connection then you should see the algorithms that your client is offering the server during the negotiation of the SSH connection.\n\n", "name": "", "is_accepted": true } ]

[ { "text": "What it means is that the authentication partially succeeded, but the server requires another authentication as well - it is suggesting via password. This is being done automatically.\n \n\n \nFor partial success, it probably should be a debug level message. It has been changed to that in the source, so in future this error message won't appear.", "name": "", "is_accepted": false }, { "text": "Thanks, that will be fine.\n \nDo you have a date for the next release?", "name": "", "is_accepted": false }, { "text": "It won't be for a couple of months. Let us know if you'd like a build to use in the interim.", "name": "", "is_accepted": false } ]

[ { "text": "This question requires contacting support.", "name": "", "is_accepted": false } ]

[ { "text": "Hi,\n\nFor some reason the rename operation is failing. Check the exact path of the file on the server. 550 errors are often given because of a non-existent file or because the file path is wrong. You also need to check that the user has the correct privileges for this path. A typing error in the file name can also lead to this error.\n\nAs you currently have a support agreement please open up a ticket on our support page which can be found [here](https://enterprisedt.atlassian.net/servicedesk/customer/portal/1). Please upload the full debug log file (you can zip it up). \n\n", "name": "", "is_accepted": false } ]

[ { "text": "Only folders of which a given account is the owner is included in its quota. Any subfolders that are owned by other users are not included in the data usage quota of the owner of the parent folder.\n\n", "name": "", "is_accepted": false } ]

[ { "text": "Please let us know which product you are using and please give us more details of the error including the debug log entry showing the error.", "name": "", "is_accepted": false } ]

[ { "text": "It may be that it's trying first with regular password authentication and then again using the same password with KBI (KeyBoard Interactive).  What do the logs say?", "name": "", "is_accepted": false } ]

[ { "text": "The solution was to set UseClientHelloExtension = false. The end user has confirmed this was successful.", "name": "", "is_accepted": false } ]

[ { "text": "The ServerAddress property must be set to the IP address or the hostname, so something like \"123.123.123.123\" or \"my.hostname.com\".  You can set the ServerDirectory property to the folder-name.", "name": "", "is_accepted": false } ]

[ { "text": "Hi, \n\n \n\nThere's no limit on the number of files. Can you post a snippet of your code?", "name": "", "is_accepted": false } ]

[ { "text": "It's likely that they are using a new server that does not have diffie-hellman-group1-sha1 enabled. You may need to upgrade to a later version that supports other key exchange algorithms  if you are using an older version.", "name": "", "is_accepted": false } ]

[ { "text": "Please see [here.](https://enterprisedt.com/products/edtftpjssl/doc/api/com/enterprisedt/net/ftp/ssl/SSLFTPCertificateStore.html)\n\n", "name": "", "is_accepted": false } ]

[ { "text": "Your article states \"SFTP uses keys rather than certificates\" - What kind of keys, the SSH RFCs refer to host keys and seem to imply asymetric technology but I'm having difficulty understanding them.\n \n\n \nThe article also states \"SFTP clients must install keys on the server\", please explain why this is so. The SSH RFCs seem to indicate that the major issue is the client verifying the server key and server identy association rather than the server having to evaluate a client key.\n \n\n \nThank you for your help, I'm trying to understand the technology and any assistance would be appreciated.", "name": "", "is_accepted": false }, { "text": "SSH uses asymmetric keys - public/private key pairs. \n \n\n \nServers must be able to identify the client (as it is essentially logging into the server), hence the client public key must be installed on the server.", "name": "", "is_accepted": false } ]

[ { "text": "Unfortunately we haven't yet added the ability to add event handlers via the command-line. \n\n \n\nIf you tell me what you want the trigger to do then I might be able to suggest a solution.", "name": "", "is_accepted": false } ]

[ { "text": "You can test run a new release of CompleteFTP against your production configuration on a test machine by following these steps. \n\n\n1. Install production's version of CompleteFTP on the test machine.\n2. Locate the configuration file (config.sdf) on the prod machine. Typically, its location is C:\\ProgramData\\Enterprise Distributed Technologies\\Complete FTP\\config.sdf\n3. Copy config.sdf to the same location on the test machine, creating directories as necessary. Make sure the SYSTEM user has full control of any directories you create.\n4. Copy all data directories from the prod machine to the test. By default, these are subdirectories of the directory where config.sdf is stored, but directories in other locations may be referenced as well.\n5. Restart the CompleteFTP service on the test machine. You now have a replica of prod - check it works with local connections (it will have the wrong activation key so you won't be able to connect from external machines).\n6. Download the version of CompleteFTP you want to upgrade to from our [customer site](https://connect.enterprisedt.com/). You'll need to know your registered email address for your account if you've lost your account details. If you can't log in, please [contact support](http://enterprisedt.com/support/contact/). You'll need a current support agreement to get the latest version - the trial won't work.\n7. Install the upgrade version of CompleteFTP on the test machine, choosing to keep the existing configuration, and confirm everything works locally (as noted, it will have the wrong activation key so you won't be able to connect from external machines).\n8. If everything works fine on the test machine, you are ready to run the upgrade installer on your production machine.\n", "name": "", "is_accepted": false } ]

[ { "text": "SFTP doesn't use passive mode - that's for FTP or FTPS (you might be talking about FTPS). \n\n \n\nHundreds of connections from a client may not work as there is usually a limit to the number of network connections you can open on a client machine. The server may also ban you for having too many connections - this will look like a DOS attempt.", "name": "", "is_accepted": false } ]