We have an Serv-U file server running and have only the port 22 opened for SFTP access from clients.
We have some questions below.
First thing first, we always have to make sure that all file transfer is SFTP SSH level secured.
1) by opening port 433 to enable the HTTPS access to the Serv-U server for clients using IE, are the file transfers between the client and server SSH secure level guaranteed the way as sftp with port 22?
2) is there any web link that we can provide our clients so they can access our SFTP server directly without using any FTP client tool? again, not simple FTP, we would need SFTP.
3) We have a Serv U Gold edition, is there any limit on maximun number of domain can be created?
Is there any maximum number client accounts/users create be created for that Gold license?
4) is it possible that we can receive an email alert when a client has push a file to our SFTP server by Serv-U?
Thanks a lot,
#1) You should be opening port 443 (not 433) for HTTPS. That channel is secured by SSL/TLS, the same as any other https://... connection. (That's slightly different than SFTP secured by SSH, but is basically the same level of security.)
#2) No, there is no standard "sftp://..." URL system. ("ftp://..." is widely supported but not secure but "https://(yourhostname)" would be appropriate to shared with people using your HTTPS web interface.
#3) No, there are no domain or user restrictions. See Serv-U FTP Server Editions Information - "Gold" is basically an early version of "MFT Server"
#4) Yes, you should set up a "File Uploaded" event to send email upon a successful transfer. If you set this up at the domain level, it will send email when any file arrives. If you set this up at the user or group level it will send email only when certain users upload files. If you set up additional event filters, you can make sure email is sent only for specific files or only uploads into certain folders.
Thank you Jonathan. I have a few more questions below.
1) SFTP supports file transfer resume, it depends on the client ftp software for that, right? Serv-U would have nothing to do with the file trasfer resume if any breakage or network connection problem has encountered?
2) By using the HTTPS web interface of Serv-U, I have done some tests with it.
Is there any maximum file size restriction for the Web Client (it does say >2GB may not work for some browser)?
3) By using the HTTPS web interface of Serv-U, does it support any resume on file transfer?
4) Regarding the "File Uploaded" event to send email upon a successful transfer, is it possible to have the filename in the email body? Seems it wont work that way.
Thanks a lot for you help again.
My pleasure. BTW, if you like what I'm saying, please click the "like" key on the responses - it will help other people see this thread and learn from it as well.
Now, on to the second group of questions:
#1) Exactly right. Serv-U is a server, which means that it will support client attempts to resume, but that the client is still responsible for deciding when or if or try resuming.
#2) The built-in web client is built so just about any web browser can use it. It uses a Browse button and a standard web-based upload form to upload files, and that mechanism does have a 2GB upload limit on many browsers. However, Serv-U does support larger-than-2GB uploads in two instances: first, you can use the Serv-U Web Client Pro, a Java-based plug-in (look for the "Web Client Pro" button in your regular Web Client interface), or second, you can use FTP Voyager JV, a Java executable that launches from Web Client (look for the "FTP Voyager JV" button in your regular Web Client interface.) Both options remove the 2GB limit, allow multiple transfers at once, add progress bars and do a number of other things that are difficult to do with just a plain web upload form.
#3) No, the built-in web client does not support resume. You would need to use one of the plug-ins to get this functionality.
#4) Yes, it's possible. I think you want to use the "$FileName" variable in your message body. ($FileName - Retrieves just the filename from $PathName)
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process.