Datasets:

---

clips

/

mqa

like 52

Follow

CLiPS 10

[ { "text": "These classes were deprecated some years ago and have not been replaced.", "name": "", "is_accepted": false } ]

[ { "text": "Yes, if you go to the User's panel and select *General User Settings*, you'll see where you can enter a default domain. Users belonging to the default domain will no longer have to prefix their userid with the domain name. \n \n\n", "name": "", "is_accepted": true } ]

[ { "text": "Pretty soon - we're working on this now. I expect within a couple of months.", "name": "", "is_accepted": true } ]

[ { "text": "This problem is almost always due to the max connections per user being set to a low figure. The File Manager uses multiple HTTPS connections, and so if users are limited to just a few connections, it won't display properly. Set the max connections per user to at least 50. \n\n", "name": "", "is_accepted": false } ]

[ { "text": "version SSH 2.0", "name": "", "is_accepted": false } ]

[ { "text": "I cannot find it anywhere on the website. Like the previous user mentioned it's under GPL and since you redistributed it already, you need to make the source accessible.", "name": "", "is_accepted": false }, { "text": "edtFTPD has been discontinued - development ceased a year or more ago - and the tweaks to the proFTPD source have been lost. Sorry.\n \n\n \nYou can download the original source from <http://www.proftpd.org/>.\n \n\n \nWe have left the binary there for download as there has still been a lot of demand for it.", "name": "", "is_accepted": false } ]

[ { "text": "Please have a look at [this help article](https://enterprisedt.com/products/completeftp/doc/guide/html/howtoupgradecluster.html).\n\n", "name": "", "is_accepted": true } ]

[ { "text": "CompleteFTP supports FTP, FTPS, SFTP, SCP and SSH (from version 4.0). \n\n \n\nFTPS is often described as FTP over an SSL connection, while SFTP is file transfer secured by SSH. SCP is an earlier form of secure copy which is also over SSH. CompleteFTP also supports SSH terminals. \n\n \n\nThe Standard Edition supports FTP, FTPS and SFTP. \n\n \n\nBoth SCP and SSH are additionally supported in the Professional Edition.", "name": "", "is_accepted": true } ]

[ { "text": "We occasionally get emails that say something like: \n\n \n\n\"I have installed and registered our CompleteFTP server. Upon startup, I receive the message \"Mismatch in machine identifier, CompleteFTP is running in restricted mode.\"\" \n\n \n\nAlmost always, this is because the URL to activate (containing the machine id) has been manually copied from the CompleteFTP manager, and a mistake has been made (usually between I and l, and 0 and O). Please, don't manually copy the URL if at all possible - it is very easy to make a mistake.", "name": "", "is_accepted": true } ]

[ { "text": "Assuming that users access the different companies via different domain-names then, yes, you can make the login page look different for different companies.\n\nYou can do this by changing the script that generates the login page.  You can find this script at\n\n\n```\nC:\\ProgramData\\Enterprise Distributed Technologies\\Complete FTP\\Login\\index.jss\n\n```\nIf you change the line:\n\n\n```\nresponse.writeUsingTemplateFile(\"template.html\", templateData);\n```\nto\n\n\n```\nresponse.writeUsingTemplateFile(\"template-\" + request.uriParts.host + \".html\", templateData);\n```\nthen the script will build the login page using files called:\n\n* template-company1.com.html\n* template-company2.com.html\n\nwhere company1.com and company2.com are the domain-names of two of the companies.  Obviously you need to substitute the actual domain names. \n\nAll you need to do is copy the existing template.html file to those file-names and then customize each of them as required.\n\nDoes that make sense?\n\n", "name": "", "is_accepted": false } ]

[ { "text": "Yes, you'll need to tell the client to use the default Java keystore. \n\nUse SSLFTPClient.getRootCertificateStore() to get the SSLFTPCertificateStore. This class has [various methods](https://enterprisedt.com/products/edtftpjssl/doc/api/com/enterprisedt/net/ftp/ssl/SSLFTPCertificateStore.html) to load keystores, including the Java keystore. \n\n", "name": "", "is_accepted": false } ]

[ { "text": "The solution was to assign %FileName% to another variable first:\n\n\n> SET checkname=%FileName% \n> SET checkname=%checkname:~0,5% \n> IF /I NOT \"%checkname%\"==\"KEEP-\" DEL /F /Q \"%WindowsPath%\"\n> \n> \n\n", "name": "", "is_accepted": true } ]

[ { "text": "Given that you know it is an SFTP server, the best explanation seems that the IP address resolved from the hostname is wrong. Is the IP address correct?\n \n\n \nThe other possibility is that a firewall on this machine is interfering somehow.\n \n\n \nWhat happens when you use a different SFTP client like Filezilla to connect?", "name": "", "is_accepted": false }, { "text": "The IP address is correct. Its not a server I can access but I'll ask them to get another SFTP client on there and see if it works.\n \n\n \nThanks for the quick response! \n \nMatt", "name": "", "is_accepted": false }, { "text": "Hi, \n \nI'm having exactly the same error. \nI've tried to connect with a sFTP client (Filezilla) and it works. \nWhen I try to connect with enterprisedt library I get an exception \"NotSSHServer\". \n \nI'm using edtFTPnetPRO version 8.3.0.20 \n \nAny idea what could be the issue?", "name": "", "is_accepted": false }, { "text": "Forget this... I was trying to connect to a ftps server, not a sftp server. \nThe message \"NotSSHServer\" could be more specific anyway... \n \nKind regards, \n \nJoao", "name": "", "is_accepted": false } ]

[ { "text": "This is generally because the FTP server has not correctly responded to the standard SSL/TLS closure exchange sequence. In this case, the server abruptly closes the connection without sending an acknowledgement to the client. The client can be prevented from waiting by setting DISABLE\\_SSL\\_CLOSURE:\n\n\n```\nSSLFTPClient ftp = new SSLFTPClient();\nftp.setConfigFlags(SSLFTPClient.ConfigFlags.DISABLE\\_SSL\\_CLOSURE) :\n\n```\n", "name": "", "is_accepted": true } ]

[ { "text": "UPDATE: Support for .NET CORE 3.1 was added in 9.8.0, which was released in January 2021.\n\n", "name": "", "is_accepted": true } ]

[ { "text": "After trying a lot of stuff (and learning about encoding conversion :-) ), i come to the conclusion that there is a bug in the IBM Virtual Machine on the USS. The transformation of encodings is probably not implementet. Once you got EBCDIC encoding you can not conevrt it bach to ASCII on the IBM VM on USS. \n \nSo the only workaround is to modify the InputStreamReader and give it a fixed encoding. Off Course yau have to modify the ASCII get/put Methods analog to this if you wish to use them:\n \n\n \nClass: FTPClient\n \nMethod: public String[] dir(String dirname, boolean full)\n \n\n \nCode:\n \n...\n \nLineNumberReader in =new LineNumberReader(\n \n new InputStreamReader(data.getInputStream(),\"Cp850\"));\n \n...\n \n\n \nI know its a ugly workaround, but thats the only way to get it run under a USS.\n \n\n \nGreetings Codon", "name": "", "is_accepted": false }, { "text": "Thanks for the info. \n \n\n \n\n> I know its a ugly workaround, but thats the only way to get it run under a USS. \n> \n> Greetings Codon\n\n", "name": "", "is_accepted": false } ]

[ { "text": "It's not supported right now but if and when it gets more popular we'll end up supporting it.", "name": "", "is_accepted": false } ]

[ { "text": "Go to the HTTP/HTTPS advanced setting and open the custom headers dialog box. You can add a new header. \n\nIn this case, add a header called \"X-Content-Type-Options\" and set its value to \"nosniff\".\n\n\n\n", "name": "", "is_accepted": false } ]

[ { "text": "Yes, but you may need a DLL that doesn't reference any Windows GUI libraries - please email us for a build.", "name": "", "is_accepted": false } ]

[ { "text": "For the information of readers, this issue was because the \"Apply changes\" button in the CompleteFTP manager had not been selected after adding the user. This meant the user had not yet been added to the configuration.", "name": "", "is_accepted": true } ]

[ { "text": "Hi,\n\nIn order to resolve this issue, please lodge a support ticket with our support team [here](https://enterprisedt.atlassian.net/servicedesk/customer/portal/1).\n\nThank you!\n\n", "name": "", "is_accepted": false } ]

[ { "text": "If you run one of the sample programs included with edtFTPj/PRO, it will fail unless there's a valid license.", "name": "", "is_accepted": false } ]

[ { "text": "We've located the leak and can provide you with a patch to try.  To get it, please open a ticket [here](https://enterprisedt.com/help).\n\n", "name": "", "is_accepted": false } ]

[ { "text": "Depends what you mean by ping your router :)\n \n\n \nIf you mean telnet to the router and run a command to verify its status (all in Java), it isn't particularly difficult - but not related to FTP.\n \n\n \n\n> Hello, \n> Can the code be easily modified to ping my router? \n> Better yet, how difficult would it be to write code JUST to ping my router?\n\n", "name": "", "is_accepted": false }, { "text": "@ the house, want to have my wireless clients ping the router so the connection stays active.\n \n\n \nOtherwise, the connections terminate from lack of use.\n \nEasy enough to reconnect when you're in front of the remote client but a pain when you upstairs and want to remotely connect to the wireless client but can't since the connection was dropped!", "name": "", "is_accepted": false } ]

[ { "text": "Many firewalls will accept the following for (host,user,password) supplied to edtFTPj's FTPClient: \n \n\n \n(firewallmachine, [[email protected]](mailto:[email protected]), remotepassword). \n \n\n \ni.e. the remote machine is the firewall, the user is the login for the remote machine followed by '@' and then the remote host, and the password is the remote host's password for the user. \n \n\n \n\n \n\n> Hi, \n> \n> I have a question, maybe someone can help me with this... \n> \n> If i want to ftp file through a proxy server / firewall (not SOCKS ones), how do i do that with this library? Where do i set up the firewall IP address? \n> \n> And what if the proxy server / firewall requires username and passwod? where do i setup firewall username & password? \n> \n> Any snippet would be really helpful... \n> \n> Many thanks \n> J\n\n", "name": "", "is_accepted": false }, { "text": "Thanks for the quick response\n \n\n \nJust to confirm, say if:\n \n\n \nFirewall IP Address: 111.111.111.111\n \nremote host IP address: 222.222.222.222\n \nremote username: aaa\n \nremote password: bbb\n \n\n \nthen i can ftp thru the firewall like this:\n \n\n \nFTPClient newClient = new FTPClient(\"111.111.111.111\");\n \nnewClient.setConnectMode(FTPConnectMode.PASV);\n \nnewClient.user(\"[email protected]\");\n \nnewClient.password(\"bbb\");\n \n\n \nam i right?", "name": "", "is_accepted": false }, { "text": "If your firewall supports this, yes.\n \n\n \n\n> Thanks for the quick response \n> \n> Just to confirm, say if: \n> \n> Firewall IP Address: 111.111.111.111 \n> remote host IP address: 222.222.222.222 \n> remote username: aaa \n> remote password: bbb \n> \n> then i can ftp thru the firewall like this: \n> \n> FTPClient newClient = new FTPClient(\"111.111.111.111\"); \n> newClient.setConnectMode(FTPConnectMode.PASV); \n> newClient.user(\"[email protected]\"); \n> newClient.password(\"bbb\"); \n> \n> am i right?\n\n", "name": "", "is_accepted": false }, { "text": "im using edtftp to do ftp for my java program and i just installed WinProxy to test if i could use it through a proxy server. \n \n\n \nI did your instruction above using the Proxy IP and Host, Host Username / Password. Somehow i got this error message.\n \n\n \n\n \njava.net.ConnectException: Connection refused: connect\n \n at java.net.PlainSocketImpl.socketConnect(Native Method)\n \n at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)\n \n at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)\n \n at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)\n \n at java.net.Socket.connect(Socket.java:426)\n \n at java.net.Socket.connect(Socket.java:376)\n \n at java.net.Socket.<init>(Socket.java:291)\n \n at java.net.Socket.<init>(Socket.java:147)\n \n at com.enterprisedt.net.ftp.FTPControlSocket.<init>(FTPControlSocket.ja\n \na:143)\n \n at com.enterprisedt.net.ftp.FTPClient.<init>(FTPClient.java:268)\n \n at com.enterprisedt.net.ftp.FTPClient.<init>(FTPClient.java:236)\n \n\n \ni tried my browser to connect to internet through the WinProxy (using the same Proxy IP address and port number), they went through alright. So i assume the WinProxy setting is okay? Unless im missing something here...\n \n\n \nAny idea?", "name": "", "is_accepted": false }, { "text": "We haven't tried WinProxy. You need to ensure that the FTP protocol is configured on it correcly. Also, it may not be listening on port 21, the FTP default. If WinProxy is listening on a different port (probable), you will need to supply this one to the appropriate FTPClient constructor as well.\n \n\n \n\n> im using edtftp to do ftp for my java program and i just installed WinProxy to test if i could use it through a proxy server. \n> \n> I did your instruction above using the Proxy IP and Host, Host Username / Password. Somehow i got this error message. \n> \n> java.net.ConnectException: Connection refused: connect \n> i tried my browser to connect to internet through the WinProxy (using the same Proxy IP address and port number), they went through alright. So i assume the WinProxy setting is okay? Unless im missing something here... \n> \n> Any idea?\n\n", "name": "", "is_accepted": false }, { "text": "thanks for the tips\n \n\n \nthe FTP wasnt activated by default, apparently.\n \n\n \njust restarted WinProxy with FTP enabled, now it works fine.\n \n\n \nis it possible to know the list of proxy/firewall that have been tested? So we could test the one you guys havent tested and post the result here", "name": "", "is_accepted": false }, { "text": "The only firewalls I'm aware of for certain that it works for are\n \n\n \n- Check Point Firewall-1\n \n- WinProxy (thanks to you)\n \n\n \nI *think* it works with most firewalls but if people can post here if they know it works for sure that would be great. Thanks for the idea.\n \n\n \n\n> thanks for the tips \n> \n> the FTP wasnt activated by default, apparently. \n> \n> just restarted WinProxy with FTP enabled, now it works fine. \n> \n> is it possible to know the list of proxy/firewall that have been tested? So we could test the one you guys havent tested and post the result here\n\n", "name": "", "is_accepted": false }, { "text": "what if the proxy requires username and password?\n \n\n \nhow do we do this?", "name": "", "is_accepted": false }, { "text": "We've never used one configured to require username/password. Anyone else tried this?\n \n\n \n\n> what if the proxy requires username and password? \n> \n> how do we do this?\n\n", "name": "", "is_accepted": false } ]

[ { "text": "The trial installation converts to a Developer licensed version after 30 days which can be used indefinitely for local testing purposes (but doesn't permit connections external to the machine). \n\n \n\nIf you need a fully functional development or test server(s) that allows external connections, currently we offer a 50% discount provided you already have a fully licensed production server.", "name": "", "is_accepted": true } ]

[ { "text": "Wow, that's a strange problem! In FTP (and in all our libraries) you can get a list of file-names without getting all the details. In .NET you can do this using FTPConnection.GetFiles() or FTPClient.Dir(). In Java you can do it using FileTransferClient.directoryNameList() or FTPClient.dir().\n \n\n \n- Hans (EnterpriseDT)", "name": "", "is_accepted": false }, { "text": "We do still need to get the file sizes to determine if the file needs to be updated-- is there any way to avoid getting the list of files, then going file by file to get the file sizes?\n \n\n \nSince this error causes the entire command to fail, it might be good to return a bogus date like 01/01/0001, rather than failing entirely. At least then we'd have some data back...", "name": "", "is_accepted": false }, { "text": "Which product are you using?\n \n\n \n- Hans (EnterpriseDT)", "name": "", "is_accepted": false }, { "text": "edtFTPnet/PRO", "name": "", "is_accepted": false }, { "text": "OK, here are three options:\n \n1. Call GetSize() on each file\n2. Call GetFiles(\"mydir\", true), which returns all the file information as strings (one for each file), and then parse it yourself.\n3. Write your own directory parser and set it using FileInfoParser.FileParser\n\n\n \n- Hans (EnterpriseDT)", "name": "", "is_accepted": false }, { "text": "By the way, if you're using the GUI controls then you'll need to write an FTPFileParser.\n \n\n \n- Hans (EnterpriseDT)", "name": "", "is_accepted": false } ]

[ { "text": "'Short read' means that the client has lost the connection with the server.  These can be very hard to diagnose, particularly when they're intermittent and the transfers are huge. \n\n \n\nHave you implemented a robust retry strategy?  In particular, I'd recommend reconnecting and resuming the transfer from where you left off.  This is more tricky than usual for you since you're processing a stream in real-time, but it shouldn't be too hard.  FTPInputStream has a constructor that takes an offset, so you just need to set that to the size of the remote file when you resume.  Since you're (presumably) parsing lines of text, you'll need to buffer any uncompleted lines of text between retries so that you can prefix them to the first line of the resumed stream. \n\n \n\nI realise this does directly answer the question that you asked, but for file-transfers as large as that, having a robust retry strategy is really essential since you can't stop interruptions occurring entirely.", "name": "", "is_accepted": false } ]

[ { "text": "Best to post the log file snippet that shows the problem. \n \n\n \nYou could try changing to passive mode, or using setActiveIPAddress() to force a valid IP address (the client's) to be supplied to the server.", "name": "", "is_accepted": false }, { "text": "\n> Best to post the log file snippet that shows the problem. \n> \n> You could try changing to passive mode, or using setActiveIPAddress() to force a valid IP address (the client's) to be supplied to the server.\n\n\n \n\n \nThank you, I will try to get the log file. The problem is that it happen at a remote location and I don't have access to the station there. The user just sent a capture of the pop message for the exception. Will try to get more information on it. \n \n\n \nFYI, it is already using passive transfer mode. Also, I realized that I posted in the wrong forum. Please move the post to the edtFTP instead of the edtFTPj. Thank you very much.\n \n\n \nftpclient = New Ftp.FTPClient\n \nftpclient.RemoteHost = tsite\n \nftpclient.ControlPort = tport\n \nftpclient.Timeout = 9600000\n \nftpclient.ConnectMode = Ftp.FTPConnectMode.PASV", "name": "", "is_accepted": false }, { "text": "To get an illegal PORT command error from the server it must be in active mode, not passive.", "name": "", "is_accepted": false } ]

[ { "text": "Take a look at the test package in the source distribution. It has loads of JUnit tests and also a simple test.\n \n\n \nPS there is a box to tick called \"Notify me when a reply is posted\" if you have registered with an email address.\n \n\n \n\n> hi, I'm new to Java and need to write a small utility to retrieve a file via ftp. I'm working in Linux and after downloading the tarball and unpacking it, don't know how to run the tests. \n> \n> also, I cannot seem to find a simple piece of code that shows how I can use these classes. can anyone please help? \n> \n> an e-mail would be greately appreciated (as I can't be checking this forum all the time for replies and I don't see a notification service for it) at [[email protected]](mailto:[email protected])\n\n", "name": "", "is_accepted": false } ]

[ { "text": "A CompleteFTP manager log is very useful for diagnosing connection problems between the manager and the server. \n\nIn the connect dialog box, choose \"Other settings ...\" and set the logging level to \"Full diagnostic\". \n\nThen try connecting to the server. \n\nThe log file should appear here: \n\nC:\\Users\\<username>\\AppData\\Local\\EnterpriseDT\\Complete FTP\\Logs\\Diagnostic.log", "name": "", "is_accepted": false } ]

[ { "text": "Set setMaxQueuedReadRequests(1) prior to connection.", "name": "", "is_accepted": false } ]

[ { "text": "Sorry, currently STOU is not supported in edtFTPnet/PRO (which I think is the command you need).", "name": "", "is_accepted": false } ]

[ { "text": "By default, CompleteFTP runs as the Local System user. Some users prefer to run CompleteFTP as a less privileged user. Can this be done? \n\nThe answer is yes, but some configuration is required: \n\n \n\n   - The CompleteFTP user must have the \"Logon User\" privilege.- The CompleteFTP user must have permission to write to the CompleteFTP data directory. \n\n \n\n   - The CompleteFTP user must have permission to access any other directories it is required to access \n\n \n\nTo actually change the user, you need to locate the Complete FTP Server in the list of services, and open its Properties dialog. Select the Log On tab, and enter the user account you wish to run the service as.", "name": "", "is_accepted": false } ]

[ { "text": "This should work fine.  CompleteFTP uses [impersonation](https://docs.microsoft.com/en-us/windows/desktop/com/impersonation), which has proven to be pretty bullet-proof over the years, so unexpected errors like this are usually because of configuration problems.  For example, one error someone had recently was that when she was testing it, she was inadvertently logging into local Windows accounts rather than equivalently named AD accounts.  In any case, a good place to start diagnosing the problem is a diagnostic log file (DEBUG level), but this shouldn't be uploaded to this public forum.  Can you instead please open a ticket at our [helpdesk](https://enterprisedt.com/help) and attach the log file there?\n\n", "name": "", "is_accepted": true } ]

[ { "text": "We identified a scenario where locking could occur, and released a fix in version 13.0.1. If anyone is experiencing this issue, please upgrade to 13.0.1.", "name": "", "is_accepted": true } ]

[ { "text": "The Complete FTP Manager is intended to be used for remote administration, and so often you'll want to install it on a machine other than the one that the server is installed on. \n\n \n\nThis is easy to do - you just need the production installer which you are supplied with on purchase. \n\n \n\nThe trial installer installs both the server components and the Complete FTP Manager for simplicity. The production installer permits just the Complete FTP Manager to be installed if required.", "name": "", "is_accepted": false } ]

[ { "text": "If browser-based authentication is used, you'll find that even if you use the default logout link, when you return to the site you are not prompted for your credentials again. This even happens if \"remember this password\" is not checked in the browser popup which collects the username and password. \n \nUnfortunately, browsers cache the credentials for the page, and simply resend the username and password automatically. Probably the best solution to this is disable browser authentication and use the supplied login page. There's an option in the [HTTP/HTTPS settings](http://www.enterprisedt.com/products/completeftp/doc/guide/html/httpsettings.html) to do that.\n\n", "name": "", "is_accepted": true } ]

[ { "text": "A loop that attempts the transfer and sleeps if an FTPException is thrown, then retries?", "name": "", "is_accepted": false } ]

[ { "text": "I've found the issue and it is a bug in our code. I've now fixed the bug and it is released as 5.3.1. Please download the release from our [customer site](https://connect.enterprisedt.com/) and that should resolve it for you.\n\n", "name": "", "is_accepted": true } ]

[ { "text": "Yes you can. \n\n \n\nWhen a browser accesses the server without authenticating it accesses it via the 'anonymous' account.  /Public is the default home folder of the anonymous account, so that is what will be presented to it. \n\n \n\nThe home folder can be changed and it can be different for different sites, so you can configure the home folder of anonymous to be, say, /Public for the Public site and /Internal for the Internal site.  The owner of both these directories should be 'anonymous'.  You can configure /Public to point to one Windows directory (e.g. C:\\Webroot\\Public) and /Internal to point to another (e.g. C:\\Webroot\\Internal).", "name": "", "is_accepted": true } ]

[ { "text": "Try setting the logging level - I can't see it set in your code.", "name": "", "is_accepted": false }, { "text": "That did it. Thank you so much! This will help troubleshooting our application SO much!", "name": "", "is_accepted": false } ]

[ { "text": "OpenSSH has fairly recently created a new private key format called RFC4716 (it isn’t a standard but is derived from this public key standard). That’s their default format now, and you can recognise it by the file header:\n\n—–BEGIN OPENSSH PRIVATE KEY—–\n\nWe don’t yet support it in our products, although we will soon. You can convert from the new format to the old format PEM keys using ssh-keygen. The command below will do the conversion (overwriting the original file!):\n\nssh-keygen -e -f openSshKeyNew -m PEM -p\n\nYou can also convert to the old PEM format using PuTTYgen.\n\n", "name": "", "is_accepted": false } ]

[ { "text": "It looks to me like the user is not permitted to use the CWD command. \n \nSet AutoLogin property to false, and then use the Login() method to login.", "name": "", "is_accepted": false }, { "text": "I tried that now but then the log file does not give anything, its created but empty. \nThe .Login method does not log, only the .Connect \n \nIt also looks like I come as far as before, logged out :(", "name": "", "is_accepted": false }, { "text": "Set AutoLogin to false, call Connect() and then Login(user,pwd).", "name": "", "is_accepted": false }, { "text": "\n> Set AutoLogin to false, call Connect() and then Login(user,pwd).\n\n \n \nThe .Login method does not take parameters but I got it to work with latest version 8.6.5.20 :D", "name": "", "is_accepted": false }, { "text": "Oops yes - but you just set the UserName and Password properties prior to calling Login().", "name": "", "is_accepted": false }, { "text": "\n> Oops yes - but you just set the UserName and Password properties prior to calling Login().\n\n \n \nWorks fine with latest version. I forgot to upload it to the server ;)", "name": "", "is_accepted": false } ]

[ { "text": "Please see our user guide [here](https://enterprisedt.com/products/completeftp/doc/guide/html/syslog.html)\n\nTo remove a logging appender please go to: \n\nC:\\Program Files (x86)\\Complete FTP\\Server\\CompleteFTPService.exe.config\n\nThen please open this up in a text editor. Scroll down to: \n\n*'Setup the root category, add the appenders and set the default level'*\n\nThe default shows as below:\n\n\n```\n<root>\n\t<level value=\"ALL\" />\n\t<appender-ref ref=\"Recent Logging Messages\" />\n\t<appender-ref ref=\"Recent Error Messages\" />\n\t<appender-ref ref=\"Syslog\" />\n\t<appender-ref ref=\"Audit\" />\n\t<appender-ref ref=\"Config\" />\n</root>\n```\nRemove the logging methods which you no longer require, e.g. if you only require Audit logging, but no other then please change to the below:\n\n<root>\n\n<level value=**\"ALL\"** />\n\n<appender-ref ref=**\"Audit\"** />\n\n</root>\n\n", "name": "", "is_accepted": false } ]

[ { "text": "Please see [here](https://connect.enterprisedt.com/#/downloads/products) for the edtFTPnet/PRO download page.\n\nTo download the licensed version you will require your login credentials.\n\nFor the trial version download page, please see [here](https://enterprisedt.com/products/edtftpnetpro/download/).\n\nI hope this helps.\n\n", "name": "", "is_accepted": false } ]

[ { "text": "The easiest thing would be for us to have a look at your configuration, but we can only do that via the helpdesk.  Can you please open a ticket at [enterprisedt.com/help](http://enterprisedt.com/help)?\n\n", "name": "", "is_accepted": false } ]

[ { "text": "If you are using the Windows move command, you need to use Windows paths. So you'll need access to the Azure folder from Windows. \n \nIf you want to use an Azure folder from within CompleteFTP, use Javascript Server-Side (JSS). See [here](https://enterprisedt.com/products/completeftp/doc/guide/jssapi/index.html) for the API guide. Try File.CopyTo\n\n", "name": "", "is_accepted": false } ]

[ { "text": "A server that accepts password authentication really shouldn’t be on the Internet if it’s not protected by auto-banning. This is because it’s constantly being attacked. The attacks generally start within seconds of the server being placed online. If you check your logs you’ll probably see these attacks. The most common attacks are brute force and dictionary attacks, in which attackers try random or common passwords. The more times that they’re permitted to try, the higher the chance that they’ll be successful. Auto-banning stops this by kicking them off after a few failures. If you disable it then they’ll be able to try an unlimited number of times - maybe millions of times.\n\nSo the solution to problems with auto-banning isn’t to disable it, but to work out why it’s happening. The most common cases are:\n\n1. The server is behind a NAT router that replaces the remote client’s IP address with its own such that, from the point of view of CompleteFTP, it looks like all clients are on the same IP address. Thus legitimate clients look like they’re on the same remote machine as attackers, so when an attacker is auto-banned, legitimate clients are also banned. Users of F5 have often reported this problem.\n2. The legitimate client is coming from the same IP address as a badly configured automated process that’s repeatedly attempting to log in and failing.\n\nSo you should not disable autobanning at all, as this gives an attacker unlimited scope to continue to carry out their attacks without hindrance.\n\nChanging the Auto-Banning paramters in our Professional and Enteprise edition is relatively straight forward, and configuration options are provided. In our Standard edition the options are very limited, but if you really need to, it is possible to change the auto-banning parameters in Standard Edition by executing an SQL query via the cftpconfig utility, but it’s a bit fiddly and we don’t advise it. The best way forward if you really need to tackle this is to upgrade to either our Professional edition or our Enterprise edition.\n\n", "name": "", "is_accepted": true } ]

[ { "text": "Not much. \n\n \n\nSSL is short for Secure Sockets Layer, and is a protocol designed and implemented by Netscape. Version 3.0 of SSL was used as the basis for the Transport Layer Security (TLS) standard, version 1.0 (defined in RFC 2246, The TLS Protocol Version 1.0). The differences between SSL 3.0 and TLS 1.0 are not substantial, but the two protocols do not interoperate. TLS does, however, support a mechanism to back down to SSL 3.0. edtFTPnet/PRO supports TLS 1.0. We generally use the term \"SSL\" interchangeably with \"TLS\", as SSL is more commonly known.", "name": "", "is_accepted": true } ]

[ { "text": "I can't tell exactly what's going on without a log file, but yes, it sounds safe to ignore this error.", "name": "", "is_accepted": false } ]

[ { "text": "The Professional Edition of CompleteFTP allows for 50 CompleteBox users, and the Enterprise Edition has unlimited users. See [here](https://enterprisedt.com/products/completeftp/doc/guide/html/filesharing.html). \n\n", "name": "", "is_accepted": false } ]

[ { "text": "Answer:\n\n\n> I suggest this structure: \n>  \n> ```\n> +- Files\n> +- Home\n> |  +- UserA\n> |  +- UserB\n> |  +- UserC\n> +- Shared\n> ```\n> \n> \n> To do this:1. Add a root folder called something like 'Files'. To do this, go to the Folders panel, click 'Add folder' and select 'Root folder' and then 'Virtual folder'. This will add a folder called 'Virtual folder 1'. To rename this, right-click on the folder and select Properties. This will show the Properties panel where you can select the Name field and add the new name. Note that a virtual folder is a folder that exists only in CompleteFTP's virtual file system. It can't contain any files. You may choose to make this a Windows folder if you'd like to put files in there.\n> 2. Drag the existing 'Home' folder into the Files folder that you just created.\n> 3. Right-click on the Files folder, select 'Add folder' and then 'Windows folder'. Now find the shared folder in your Windows file-system and add that. If you've already created it in CompleteFTP you can just drag it into the Files folder.\n> \n> \n> So now you have the basic structure. Next thing is to set the permissions. \n> \n> You need your users to have 'list folder contents' and 'change into folder' permission for Files so that they can navigate to that folder in FileZilla. For the Shared folder you want users to have those permissions as well as 'download files' permission. All users are members of the inbuilt 'users' group. If you know you want all users to have the same permissions for Files, Home and Shared then you can just go ahead and user the users group for these three folders. So set this to be the group for Files, Home and Shared, and set the permissions for the group as described above. You shouldn't need to set the permissions of the Home folder and users' individual home folders as the default setting should suffice for those. \n> \n> When UserA first logs in they'll see only the folders, Files, Home and UserA. The question-mark on the icon for Files implies that FileZilla hasn't yet retrieved a listing for that directory and therefore doesn't know if that directory has subdirectories other than Home. When the user selects Files FileZilla will get a listing of Files and thus find the Shared folder.\n\n", "name": "", "is_accepted": true } ]

[ { "text": "Yes, CompleteFTP supports events called [process triggers](http://enterprisedt.com/products/completeftp/doc/guide/html/processtriggers.html) that get launched after a file transfer or some other actions. You can use our FTP script to send the file elsewhere, or your own tool. It also has [scheduled events](http://enterprisedt.com/products/completeftp/doc/guide/html/scheduledevents.html). \n\n", "name": "", "is_accepted": false } ]

[ { "text": "There's a release of edtFTPnet/PRO that works on .NET 1.1 (7.4.0), and later versions all work on 2.0 and above.", "name": "", "is_accepted": false } ]

[ { "text": "edtFTPnet and edtFTPj(/SSL) are client APIs only.\n \n\n \n\n> Hi everybody, \n> I am developing an app with jms api, and i would like to add a service to transfer files over users. I would like to use this api, but i have a question: \n> \n> This api offers, services to Client, however if i need to transfer a file or upload a file to a server, i had to implement the server with sockets or this api has capability to receive files from other client? \n> \n> Thanks and sorry for my English.\n\n", "name": "", "is_accepted": false } ]

[ { "text": "A start might be to increase the timeout setting of the proxy server. \n \n\n \n\n> Hi, \n> \n> I have been using edtFTP in an application i built for a company a while back. Up until now all has been well, but recently the company has grown in size and has changed the sourcing for their company network. \n> \n> The network now goes through a proxy server and all of a sudden they cant download any of the larger files in the application because they get a timeout error. \n> \n> Is there any way to get around this problem, as they dont seem to be able to make changes to the config of the proxy server. \n> \n> \n\n", "name": "", "is_accepted": false } ]

[ { "text": "You'll need to open a support ticket [here](https://enterprisedt.atlassian.net/servicedesk/customer/portal/1) for us to look into this in detail, but if you enable debug logging on the server and examine the server log file (C:\\ProgramData\\Enterprise Distributed Technologies\\Complete FTP\\Logs\\diagnostics.log) there's a good chance you'll see why this is happening. \n\n", "name": "", "is_accepted": true } ]

[ { "text": "Yes, it is easy to upgrade and will cost you only the price difference. Please open a support ticket [here](http://enterprisedt.com/support/open.php) and give us your purchase reference and details, and we'll send you a quote with a purchase link.\n\n", "name": "", "is_accepted": false } ]

[ { "text": "You should find it in the registry.  Please run regedit.exe and look for the following key:\n\n\n```\nHKEY\\_CURRENT\\_USER\\Software\\Enterprise Distributed Technologies\\edtFTPnet PRO\n```\n", "name": "", "is_accepted": false } ]

[ { "text": "This is a problem with Filezilla server, and it is because Filezilla server does not support the [extended master secret](https://tools.ietf.org/html/rfc7627) feature in TLS. This feature makes connections more secure. \n\nIf a server does not support the extended master secret and the client does, the RFC says the client should not resume connections. But Fiezilla server has a setting that says if a data connection (used to list directories or transfer files) does not resume, then terminate the connection. \n\nThe Filezilla log shows it happening:\n\n450 TLS session of data connection has not resumed or the session does not match the control connection\n\nTo fix the problem,go to FTP over TLS settings in the Filezilla server options, and uncheck \"Require TLS session resumption on data connection when using PROT P\".\n\n", "name": "", "is_accepted": true } ]

[ { "text": "Some people have been reporting the following exception when using FTPS on Windows 8 or 2012: \n\n \n\nSystem.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt. \n\n \n\nIf this is happening from within Visual Studio, it seems that it is a bug with the Visual Studio hosting process. \n\n \n\nGo to the project Debug settings, and uncheck \"Enable the Visual Studio hosting process\".", "name": "", "is_accepted": false } ]

[ { "text": "I'm sorry for your trouble. \n\n \n\nI've checked the logs.  I can see lots of login attempts by gibksa01, but they all failed.  Did you actually manage to log in successfully with this user-name?  It seems unlikely as there are no accounts with a user-name that looks similar to this.  Please note that our ordering system doesn't share account with our Q&A and helpdesk systems, so you'll need to create a new account when you order.  I've verified that no credit card transaction has been created in association with your attempts to order, so it's safe to try again.  When you do, please just create a new account with a new username.", "name": "", "is_accepted": false } ]

[ { "text": "You have control over the algorithms so you can disable the ones you don't want such as MD5 and DES - there's an API for doing so. \n\n \n\nIn SFTP we currently support SFTPv3 (as it is the most broadly supported protocol).", "name": "", "is_accepted": false } ]

[ { "text": "The home folder can be different for each site, so there's a table called SiteUser that maps users to sites. This table has a NodeID, which is the foreign key of the user's home folder, which is stored in the Node table.\n\n\n```\nSELECT UserName AS UserName, Configuration AS Path FROM [User]\nINNER JOIN SiteUser ON SiteUser.UserID=[User].UserID\nINNER JOIN Node ON SiteUser.NodeID=Node.NodeID\nINNER JOIN Site ON SiteUser.SiteID=Site.SiteID\nWHERE Site.System=0\n```\n", "name": "", "is_accepted": false } ]

[ { "text": "Make sure he is using 1.1.5 - this uses the InvariantCulture which might help. Also, 1.1.5 allows you to set the ParsingCulture which he could try to set specifically to his regional culture.\n \n\n \n\n> Hi, \n> \n> I'm developing a utility for a friend in Taiwan. He has Windows 2000, and his regional settings are set to Chinese Traditional, Chinese (Taiwan). When he calls the DirDetails(string dirName) function, he gets the following exception message: \n> \n> \"String was not recognized as a valid DateTime.\" \n> \n> \n\n", "name": "", "is_accepted": false } ]

[ { "text": "Please [enable logging](http://www.enterprisedt.com/products/edtftpnet/doc/manual/html/howtosetuplogging.html) and post the log file (suitably edited to remove the hostname etc)", "name": "", "is_accepted": false }, { "text": "\n> Please [enable logging](http://www.enterprisedt.com/products/edtftpnet/doc/manual/html/howtosetuplogging.html) and post the log file (suitably edited to remove the hostname etc)\n\n\n \n\n \n\n \nINFO [BaseSocket] 24 Mar 2014 09:07:35.608 : Connecting to 12.169.193.146:21 with timeout 120000 ms\n \nINFO [FTPControlSocket] 24 Mar 2014 09:07:35.810 : Command encoding=System.Text.SBCSCodePageEncoding\n \nINFO [FTPControlSocket] 24 Mar 2014 09:07:35.857 : Expected reply codes = [230,202,332] (strict=False)\n \nDEBUG [FTPConnection] 24 Mar 2014 09:08:53.040 : Set LocalDirectory='C:\\Users\\bwhite\\AppData\\Local\\Temporary Projects\\BBTTransmit\\bin\\Debug'\n \nDEBUG [FTPClient] 24 Mar 2014 09:08:53.040 : Connecting to 12.169.193.146:21\n \nDEBUG [HostNameResolver] 24 Mar 2014 09:08:53.040 : Resolving 12.169.193.146\n \nDEBUG [HostNameResolver] 24 Mar 2014 09:08:53.040 : 12.169.193.146 resolved to 12.169.193.146\n \nINFO [BaseSocket] 24 Mar 2014 09:08:53.040 : Connecting to 12.169.193.146:21 with timeout 120000 ms\n \nDEBUG [BaseSocket] 24 Mar 2014 09:08:53.071 : Successfully connected to 12.169.193.146:21\n \nDEBUG [FTPControlSocket] 24 Mar 2014 09:08:53.087 : Setting socket timeout=120000\n \nINFO [FTPControlSocket] 24 Mar 2014 09:08:53.087 : Command encoding=System.Text.SBCSCodePageEncoding\n \nDEBUG [FTPControlSocket] 24 Mar 2014 09:08:53.087 : StrictReturnCodes=False\n \nDEBUG [FTPControlSocket] 24 Mar 2014 09:08:53.103 : 220 (vsFTPd 2.0.1)\n \nDEBUG [FTPConnection] 24 Mar 2014 09:08:53.103 : Connected to 12.169.193.146 (instance=0)\n \nDEBUG [FTPControlSocket] 24 Mar 2014 09:08:53.103 : ---> USER ******\n \nDEBUG [FTPControlSocket] 24 Mar 2014 09:08:53.134 : 331 Non-anonymous sessions must use encryption.\n \nDEBUG [FTPControlSocket] 24 Mar 2014 09:08:53.134 : ---> PASS ********\n \nDEBUG [FTPControlSocket] 24 Mar 2014 09:08:53.165 : 503 Login with USER first.\n \nINFO [FTPControlSocket] 24 Mar 2014 09:08:53.165 : Expected reply codes = [230,202,332] (strict=False)\n \n\n \n\n \n(I also *'ed out the user name)", "name": "", "is_accepted": false }, { "text": "Interesting. It is telling you to use \"USER\" first, and yet the log shows that you are.\n \n\n \nThe clue may be in this message: \"Non-anonymous sessions must use encryption\".\n \n\n \nThat may mean you need to be using FTPS (FTP over SSL) rather than FTP.\n \n\n \nYou can confirm that by using FIlezilla to connect - first try FTP then FTPS (explicit).", "name": "", "is_accepted": false }, { "text": "It certainly appears that you have to use FTPS in order to log into a user account. Our commercial version of the library, [edtFTPnet/PRO](http://www.enterprisedt.com/products/edtftpnetpro/overview.html) contains a component, [SecureFTPConnection](http://www.enterprisedt.com/products/edtftpnetpro/doc/manual/api/html/T_EnterpriseDT_Net_Ftp_SecureFTPConnection.htm), that allows you to set the protocol to FTPSExplicit, which should allow you to log in.\n \n\n \n- Hans (EnterpriseDT)", "name": "", "is_accepted": false } ]

[ { "text": "CompleteFTP is its own webserver - it doesn't use IIS or an external webserver. \n\n \n\nThe issuer probably wants to know because they need to know what format they should send you the certificate in. CompleteFTP accepts most format, but since you need to choose one, we suggest telling them Apache. \n\n \n\nBy the way, I see that you're still using the old file-manager (FileManager1). I recommend using the new one, which is much more modern and works on mobiles. You can change it by setting the home web-app for the whole site or for individual users to FileManager2.", "name": "", "is_accepted": false } ]

[ { "text": "Without a log it is difficult to say. Is this FTPS or SFTP? You could enable logging at the INFO or ERROR level - that will give minimal logging but will provide some clues. Also, the server log may provide details on the issue if you have access to it.", "name": "", "is_accepted": false } ]

[ { "text": "Rolling back CompleteFTP is quite easy. The most crucial step is restoring the old version's configuration file.\n\n\nCompleteFTP uses a configuration file called config.sdf, and it is stored here:  \n\n\nC:\\ProgramData\\Enterprise Distributed Technologies\\Complete FTP\n\n\nWhen an upgrade is performed, a backup of the old configuration file is stored here:\n\n\nC:\\ProgramData\\Enterprise Distributed Technologies\\Complete FTP\\Backup\n\n\nBackups are named by their version number, and are called either daily\\_[version]\\_[date].sdf or update\\_[version]\\_[date].sdf.\n\n\nTo roll back to a specific version, you need the most recent configuration file for this version,. e.g. to roll back to 9.1.3 from 10.0.0, you need to locate the most recent version of the 9.1.3 config file. For the installation on the author's machine, that file is update\\_913\\_20161222.sdf.  \n\n \n\nOnce this file is located, follow these steps:\n\n\n1. Uninstall CompleteFTP (it won't remove backups).\n\n\n2. Copy the previous version's configuration file (e.g. update\\_913\\_20161222.sdf) to the configuration directory (C:\\ProgramData\\Enterprise Distributed Technologies\\Complete FTP), renaming it to config.sdf.\n\n\n3. Install CompleteFTP using the rollback version's installer (obtainable from our [customer site](https://connect.enterprisedt.com)). \n\n\n  \n\n \n\n", "name": "", "is_accepted": true } ]

[ { "text": "If you are using the Enterprise Edition and have written your own extension, it is possible you have received this error: \"Error in authentication: Could not load file or assembly 'CompleteFTPServer, Version=x.x.x\". \n\n \n\nThis error occurs if you have upgraded CompleteFTP and not recompiled your extension assembly against the new CompleteFTPServer.dll. Currently this is required.", "name": "", "is_accepted": true } ]

[ { "text": "Yes, it does it by simple order, and by default ssh-dss is listed first. You can change the order in SSHFTPClient like this:\n\n\n```\nsshFTP.disableAllAlgorithms(SSHFTPAlgorithm.KEY\\_PAIR);\nsshFTP.setAlgorithmEnabled(SSHFTPAlgorithm.KEY\\_RSA, true);\nsshFTP.setAlgorithmEnabled(SSHFTPAlgorithm.KEY\\_DSA, true);\n```\nThis puts them in the order ssh-rsa,ssh-dss.\n\n", "name": "", "is_accepted": true } ]

[ { "text": "4.1.1 is an extremely old version, and we don't have a comparison sheet. You will, however, get a good idea of the differences by browsing the revision history, [here](http://enterprisedt.com/products/edtftpnetpro/doc/manual/html/history.html).\n\n", "name": "", "is_accepted": false } ]

[ { "text": "Please go to the monitoring tab in the CompleteFTP Manager (administration) application , where you can find the TCP port usage, connection details, real time logging and more.", "name": "", "is_accepted": false } ]

[ { "text": "Assuming you are referring to CompleteFTP, yes, the trial version has the same functionality as the production version.", "name": "", "is_accepted": false } ]

[ { "text": "The lrename command (which is an operation on the local system, i.e. on the CompleteFTP server on which it is running) only renames a file or a directory.  It cannot move files from one directory to another.", "name": "", "is_accepted": false } ]

[ { "text": "Yes, [turn on auditing](https://enterprisedt.com/products/completeftp/doc/guide/html/auditing.html) and examine the auditing log. \n\n", "name": "", "is_accepted": false } ]

[ { "text": "You can directly query the configuration database using [this tool](http://technet.microsoft.com/en-us/library/ms174147.aspx).  \n\n \n\nMake a copy of C:\\ProgramData\\Enterprise Distributed Technologies\\Complete FTP\\config.sdf, install the viewer and then open the copy using the viewer. \n\n \n\nThen run this query (or similar) in the query editor: \n\n \n\nSELECT UserName,FullName,Description from [User] \n\n \n\nYou can copy and paste the result.\n\n", "name": "", "is_accepted": true } ]

[ { "text": "Yes, edtFTPnet/PRO works in non-GUI apps including console applications and Windows services. Of course it will also work in Windows Forms apps, where the FTP GUI controls can save the developer a lot of time and effort.", "name": "", "is_accepted": true } ]

[ { "text": "This has been observed when the Linux command-line sftp client tries to connect to CompleteFTP. \n\n \n\nThe problem was non-English characters in the welcome banner set up in CompleteFTP. Most SFTP clients such as Filezilla deal with non-English characters correctly, but the Linux sftp client does not. Removing the non-English characters from the welcome message in CompleteFTP solved this issue.", "name": "", "is_accepted": false } ]

[ { "text": "Can you please enabled logging at the DEBUG level and post the relevant portion of the log.\n \n\n \n- Hans (EnterpriseDT)", "name": "", "is_accepted": false }, { "text": "Switch to the latest Pro version and the error gone away. I still try to run some more test with logging turn on. As soon as I see the same error, I will post the log.", "name": "", "is_accepted": false }, { "text": "Got the error again with the Pro version. Turned on log file and emailed the log to support. Please check.\n \nThank you,\n \n\n \nHugh", "name": "", "is_accepted": false }, { "text": "It wasn't detecting that the file wasn't found from the msg returned from SIZE. Solution is to do this:\n \n\n \nmyftp.FileNotFoundMessages.Add(\"CANNOT FIND\")", "name": "", "is_accepted": false } ]

[ { "text": "CompleteFTP's Javascript environment (JSS) includes both an FTP client and an Email client, so you can write a script that downloads files and then sends an email when it's done.\n\nHere's sample script that downloads a file (adapted from [this](https://enterprisedt.com/products/completeftp/doc/guide/jssapi/Ftp.html)):\n\n\n```\nvar ftp = new Ftp();\nftp.hostName = \"myftpserver\";\nftp.protocol = \"SFTP\";\nftp.userName = \"myusername\";\nftp.password = \"mypassword\";\ntry {\n ftp.connect();\n} catch (e) {\n throw \"Could not connect to server.\";\n}\ntry {\n ftp.download(\"myfile.dat\", \"/home/myusername/myfile.dat\");\n console.log(\"Download complete\");\n} catch (e) {\n throw \"Error while downloading file.\";\n}\nftp.close();\n\n```\nand here's a sample script that sends an email (from [here](https://enterprisedt.com/products/completeftp/doc/guide/jssapi/mail.html))\n\n\n```\nmail.smtp.server = \"smtp.gmail.com\";\nmail.smtp.port = 587;\nmail.smtp.userName = \"[email protected]\";\nmail.smtp.password = \"my.password\";\nmail.smtp.enableSSL = true;\n\nmail.send(\"[email protected]\", \"[email protected]\", \"Test message\", \"This is a test\");\n\n```\nYou should be able to put these two together to get the desired result.\n\n", "name": "", "is_accepted": false } ]

[ { "text": "It allows the SFTP client to send batch upload requests so that instead of sending one request and waiting for the response before sending another one, it sends a set of requests all at once and processes them as they arrive, sending another request for each response.", "name": "", "is_accepted": false } ]

[ { "text": "I've never heard of a firewall blocking an SSH message. A debug log file might tell us more.", "name": "", "is_accepted": false } ]

[ { "text": "Yes, the timestamp is returned in local time. Why's that a problem?", "name": "", "is_accepted": false }, { "text": "\n> Yes, the timestamp is returned in local time. Why's that a problem?\n\n\n \nOn the remote site, in timezone A, certain files are created throughout the day and placed in a daily folder. When retrieved and placed in the same daily folder, it appears to certain users, that the files are going into the wrong folder due the the \"corrected\" time stamp.\n \n\n \nMy customers simply asked if it was possible to set the modified time on the local file to the same value as the modified time on the remote system. LastWriteTime seemed like a straightforward solution until the time showed up in local time.\n \n\n \nAs explained initially, a file last modified on Nov 8 at 23:59PM on the remote system shows up on the local system with a time of Nov 9 02:00AM. My customers would like both to read Nov 8 23:59PM.", "name": "", "is_accepted": false }, { "text": "The server actually supplies the timestamp in UTC, and we convert it to local time. So we don't actually get the local time on the server sent to us when a file is downloaded.\n \n\n \nWhat you can do is work out the time difference and set the TimeDifference property. You should be able to do this by doing using GetFileInfos() which does return the server time, and comparing a file's timestamp to that returned by GetLastWriteTime.", "name": "", "is_accepted": false }, { "text": "\n> The server actually supplies the timestamp in UTC, and we convert it to local time. So we don't actually get the local time on the server sent to us when a file is downloaded. \n> \n> What you can do is work out the time difference and set the TimeDifference property. You should be able to do this by doing using GetFileInfos() which does return the server time, and comparing a file's timestamp to that returned by GetLastWriteTime.\n\n\n \n\n \nTurns out my code uses GetFileInfos() to build the list of files to download. And the ModifiedTime inside the FTPFile class has the remote time in it exactly as I needed it. Wasn't necessary to calculate the TimeDifference at all. The \"Kind\" of the ModifiedTime datetime is Unspecified. See [http://msdn.microsoft.com/en-us/library ... .kind.aspx](http://msdn.microsoft.com/en-us/library/system.datetime.kind.aspx)\n \n\n \nSo right when myClient.DownloadFile() returns, I just create a FileInfo for the local file, check it exists and set the LastWriteTime to the ModifiedTime from FTPFile.\n \n\n \nWorks great. Hope I haven't overlooked something.\n \n\n \nThanks for pointing that out to me.", "name": "", "is_accepted": false }, { "text": "That sounds fine.", "name": "", "is_accepted": false }, { "text": "Well, after upgrading to the newest edtFTP Pro library, the \"Kind\" of the LastModifiedTime in the FileInfo is UTC as I was warned it should be. Or perhaps it was one of the Microsoft updates.\n \n\n \nBack to the drawing board. :(\n \n\n \nI think the answer is no but can I get the \"date\" of the remote system using an FTP command? Is there anything in transferring a file out or getting a directory listing? Maybe creating a new file on the remote system knowing my localtime and then looking at the FileInfo for the newly created file? Have to think my way through some of this. Again.", "name": "", "is_accepted": false }, { "text": "You can work out the time offset by exploiting an idiosyncrasy of the protocol. The GetLastWriteTime, which uses the MDTM command, returns the time in UTC, whereas the GetFileInfos() method returns timestamps in the local time. What you can therefore do is retrieve a directory listing using GetFileInfos() and then call GetLastWriteTime() for one of the files or directories in the listing. Then timezone offset is the difference between the two.\n \n\n \nPlease let me know how that goes.\n \n\n \n- Hans (EnterpriseDT)", "name": "", "is_accepted": false }, { "text": "\n> You can work out the time offset by exploiting an idiosyncrasy of the protocol. The GetLastWriteTime, which uses the MDTM command, returns the time in UTC, whereas the GetFileInfos() method returns timestamps in the local time. What you can therefore do is retrieve a directory listing using GetFileInfos() and then call GetLastWriteTime() for one of the files or directories in the listing. Then timezone offset is the difference between the two. \n> \n> Please let me know how that goes. \n> \n> - Hans (EnterpriseDT)\n\n\n \n\n \n :? Ok...\n \n\n \nWhat I want is the timestamp on the client file to be the same as the timestamp on the server file ignoring any timezone differences. As mentioned above, although maybe not clearly, it WAS working! I was using the timestamp from the FTPFile class returned by the GetFileInfos command and assigning it the client file timestamp.\n \n\n \nThis was working when I was testing in December. However, when I went to check with one of our user's, the timestamps of the files on the client machine weren't the timestamps from the server anymore, they were the timestamps with the difference between the server timezone and the client timezone applied.\n \n\n \nWhen I looked at the FTPFile timestamp, it now showed the \"Kind\" as UTC where previously it showed as \"Unspecified\".\n \n\n \nI'll look but I don't think I changed any code that would cause this. So I was thinking it was something in the latest edtFTPnetPRO.dll, 8.3.20 that I updated to in my project about the same time...", "name": "", "is_accepted": false } ]

[ { "text": "Unfortunately version 12.X doesn't support formats other than JSON when custom commands are invoked in this way, but there is a way to do it.\n\nWhat you can do is create a JSS web app that calls your custom command and returns a value in any format you like.  To try this do the following:\n\n1. Add a Windows folder called 'Test' underneath the /Public folder in the virtual file-system.\n2. Set the owner to 'web' (since the web user has JSS enabled).\n3. Use a text editor to create a file called test.jss and save it in the Windows folder to which /Public/Test is mapped (probably C:\\ProgramData\\Enterprise Distributed Technologies\\Complete FTP\\Public\\Test).\n4. Copy the code below into the JSS file and replace 'myFunction' with the name of your function.\n5. Save the file.\n6. Open the following URL in your browser: https://localhost/Test/test.jss.  You should see the XML that your function returned.\n\nCode:\n\n\n```\nresponse.write(system.executeCustomCommand(\"myFunction\"));\nresponse.contentType = \"application/xml\";\n```\nNote that, since the /Public/Test folder doesn't give permissions to 'All users', you'll need to be logged in to be able to call the function.  If you'd like provide public access then just grant 'Download' permission for 'All users' for that folder in the Folders panel.\n\n", "name": "", "is_accepted": false } ]

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

[ { "text": "Encryption at rest is implemented by CompleteFTP (in the Enterprise Edition). You don't need to purchase any third party software.", "name": "", "is_accepted": false } ]

[ { "text": "Yes, edtFTPnet/PRO certainly can be used on .NET 4.7.1.", "name": "", "is_accepted": false } ]

[ { "text": "We recommend you have a [current support agreement](http://enterprisedt.com/products/completeftp/support/) prior to migrating your installation. This gives you access to assistance with the migration and the latest version of CompleteFTP. \n\nIf you do not have a current support agreement, you can still freely move your license if you are on version 9.1 or higher (via the *release license option)*. If you are on 9.0 or below, or you need technical assistance, you will need to renew support to move your license.\n\nFollow the steps below in order to move CompleteFTP server from one machine (source) to another machine (target):\n\n1. a) If you are on version 9.0 or below, [contact support](http://enterprisedt.com/support/contact/) to get another license allocated so you can reactivate. If you do not have a current support agreement you will need to renew it. \nOR \nb) If you are on version 9.1 or above, you can use the *release license option* in the Licensing panel of the CompleteFTP manager. This puts the server into migration mode, and it is fully operational for a further 30 days. We advise doing this only when the new machine is ready to activate (Step 7). Note that if you have current technical support, you can upgrade to the latest version on the original machine so this option can be used.\n2. Download the latest version of CompleteFTP that you are entitled 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.\n3. Install CompleteFTP on the target machine. This creates all the default directories.\n4. Locate the configuration file (config.sdf) on the source machine. Typically, its location is C:\\ProgramData\\Enterprise Distributed Technologies\\Complete FTP\\config.sdf\n5. Copy the config.sdf to the same location on the target machine.\n6. Copy all data directories from the source to the target. By default, these are subdirectories of the directory where config.sdf is stored, but directories in other locations may be referenced as well.\n7. Install CompleteFTP on the target machine (again), choose the option to keep the configuration file, and confirm everything works locally (it will have the wrong activation key so you won't be able to connect from external machines). Note: if you have specific IP addresses configured for certain protocols, you will need to alter these if your new machine has a different IP address.\n8. [Activate CompleteFTP](http://www.enterprisedt.com/products/completeftp/activation.html) on the target machine. If you are running 9.1 or above, this is the time to release the license from the original machine (Step 1b)). If you have trouble activating your new installation then please [contact support](http://enterprisedt.com/support/contact/).\n9. Check external connections succeed. If your server IP address has changed, ensure your firewall is directing external connections to your new server. You may also need to modify the server's Windows firewall to give CompleteFTP access to the outside world.\n\n", "name": "", "is_accepted": true } ]

[ { "text": "Warning. This will completely remove your CompleteFTP installation!\n\n1. Delete C:\\Program Files (x86)\\Complete FTP (and subdirectories)\n\n2. Delete C:\\ProgramData\\Enterprise Distributed Technologies\\Complete FTP (and subdirectories)\n\n3. Delete the service by doing the following:\n\na) Click *Start* | **Run** and type regedit in the Open: line. Click OK.\n\nb) Navigate to HKEY\\_LOCAL\\_MACHINE\\SYSTEM\\CurrentControlSet\\Services\n\nc) Scroll down the left pane, locate the service name, right click it and **select Delete**.\n\n4, Similarly delete the following registry entries using regedit, and any subkeys:\n\nHKEY\\_LOCAL\\_MACHINE\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Uninstall\\Complete FTP\n\nHKEY\\_LOCAL\\_MACHINE\\SOFTWARE\\Complete FTP\n\n", "name": "", "is_accepted": false } ]

[ { "text": "This looks like an oversight.  Given the apparent simplicity of this change, we may be able to get you a patch with the setter included very quickly.  This will require you to have a current support agreement, however.  Do you have a current support agreement?", "name": "", "is_accepted": false } ]

[ { "text": "How often do you need to send files? Typically, SFTP servers will disconnect a connection if it is idle for more than a few minutes, so if it is more than say two minutes between sends, you should disconnect and reconnect each time.", "name": "", "is_accepted": true } ]

[ { "text": "No, a file lock is not put on the file (unless the FTP server that actually doing the file write puts a lock on the file). There is no mechanism for the FTP client to do this. Typically, FTP servers don't lock this file as often another process may be reading it.  They may put a write lock but you can't count on it. \n\n \n\nThe usual approach is to upload to a temporary file name and then rename it to the target filename once the upload is complete. This should avoid the problem you are describing.", "name": "", "is_accepted": false } ]

[ { "text": "This is because some SFTP clients send a \"fake\" login with no username when they login. The SSH protocol means that the reply message (failed login) lists all the authentication methods that are possible, and the client uses that list to decide what authentication method to try next. \n\n \n\nI'm not sure if this should be ignored or logged as a login attempt. We'll consider ignoring it the first time, as it's annoying having the login event triggered when it is not really trying to login.", "name": "", "is_accepted": false } ]

[ { "text": "Yes, we plan to do this and hope to have it ready in late 2019.", "name": "", "is_accepted": false } ]

[ { "text": "Events are only triggered at the completion of an event. Process triggers can be written in Javascript so they are quite flexiible. You could write a script to tell you the size of the file, but you can't tell the number of bytes transferred or the error message (it would be useful if the error message could be supplied - I will check to see if that is on the planned features list.", "name": "", "is_accepted": true } ]

[ { "text": "Someone else requested this mid last year and we added support for it.  I'm not sure which version it was added, but it's definitely in the current version 8.5.1.  There's no visible change in the user-interface, but a new configuration of rules is supported.\n\n\nHere's how I described it to our tester:\n\n\n\n> \n> The way that this requirement can be realized by the admin is that they set precedence to 'allow before deny' and then add two rules for each restricted user: one to deny all access from all addresses for that user, and the other to allow access from one specific address for that user.  This can be done in the IP filtering dialog box.\n> \n> \n> \n\n\nIt looks like your support agreement has expired.  You can extend it [here](https://connect.enterprisedt.com/#/shop/support/extend).  If you just want to test the latest version then you can download the trial from [here](http://enterprisedt.com/products/completeftp/download).\n\n", "name": "", "is_accepted": false } ]

[ { "text": "Most servers will allow you to use the rename function to do that.\n \n\n \n- Hans (EnterpriseDT)", "name": "", "is_accepted": false } ]

[ { "text": "Currently, there is no way to set a validator for SSL in SecureFileTransferClient. This is an oversight and is not by design, so we will add this to a future version (hopefully the next release). \n\n \n\nIf you post the relevant snippet of the debug log file we can offer an opinion on what is happening.", "name": "", "is_accepted": true } ]