dougpapenthien

That is correct.

Have you checked the domain log after attempting to send a file share invitation? There should be an error message in there that will contain the failure response from the mail server (if one was received). It should start with something like "Unable to send message to". You'll need to have logging for "System Messages"…

It sounds to me like your only options are to accept that Serv-U will have a port value in the URL or acquire another IP address so the domains can point to separate services on the same machine. The file sharing feature doesn't support downloading a file directly like you're trying to do.

Serv-U's ODBC support wasn't designed for external programs to be able to administer the database and for those changes to effect immediately within Serv-U. As you've discovered, it is technically possible but there's no guarantee from Serv-U on when it will start using those updated settings. In fact, if an external…

This is probably something that's going to require some back-and-forth to work out all of the details. Can you open a support ticket for this? An agent will be able to work with you directly to get this resolved faster.

This indicates that the path being used to create the file share location is still incorrect. See how it's trying to receive the file to the path "filesharing\1\...." instead of something like "C:\filesharing\1\..."? If you've already fixed this, ensure that you've configured it at the proper level (server or domain) and…

If you double-click on the folder you want to use (so the dialog actually browses to it) and then hit "Select" in the dialog, it should use the full path. Otherwise, just manually type in the path in the field and save it.

Unfortunately, that is the only way this can be done currently. I see that you've opened a feature request in the forum as well, which is good (I voted for it, too ).

The default value for "Treat Windows shortcuts as targets in listings" is "No", so you would need to modify this to "Yes" in order to test out my settings. Serv-U reports the shortcut as a Unix style link because, for FTP, Serv-U uses "Unix style listings" for the LIST command and "Interpret Windows shortcuts as links" is…

If you're on Linux, then you probably have the OpenSSL command-line tools already available to you. Otherwise, you'll need to install a Windows package: http://www.openssl.org/related/binaries.html Once that's done, this page explains how you can extract the public key: openSSL: how to extract public key? - Stack Overflow

From the top part of the System Variables help documentation page: Furthermore, you can also use the %USER%, %HOME%, %USER_FULL_NAME%, and %DOMAIN_HOME% variables. For more information about these variables, see "Directory Access Rules" In general, it's best to use the $ macros for events and within system messages (like…

Serv-U will continue to authenticate against other sources when the DB is down. The order in which Serv-U check for users is 1) local users, 2) ODBC users, 3) Windows Authentication, 4) LDAP users, 5) Integration DLL users. You would need a mechanism for replicating your users within one of these other sources. I'm not…

Are you using Security Groups in your LDAP setup? In your example above, are FTP-Admin and FTP-User OUs or Security Groups? Currently, there is a bug in Serv-U where the OU isn't parsed as a group membership for LDAP users unless the user also belongs to at least one security group (which is identified in your LDAP server…

An additional option is enabling FIPS. If FIPS is already turned on, then SSLv3 is disabled since it isn't FIPS compliant. However, if it's not already enabled, you may end up needing a new certificate or private key if either are using ciphers or MACs which aren't FIPS compliant.

Thanks for following up with us on your deployment. I'm very happy to hear that the new version made this possible for you!

This is most likely due to the limited LDAP support in the current version of Serv-U. There are LDAP improvements coming up in the next version of Serv-U that includes the ability to specify a "connection account" (or a "bind account") that is used to make queries against the LDAP server. I'm guessing that is your issue as…

In addition, make sure "Triggered Events" are enabled in your logging options. Then examine the domain and server logs to see if the event is showing up as having fired twice. Part of the logging information is the Event Name: [06] Tue 24Jun14 15:33:00 - Event: USER_LOGIN (Event 03); Type: BALLOON TIP; "User has logged in"…

This is a known issue that's being corrected. It occurs because your Management Console is password protected. The current workaround is to right-click the tray and select "Use System Browser".

The sysop chat feature was a rarely used feature in older versions of FTP Voyager. Unfortunately, it was removed as of v16.

I believe each of the vulnerabilities you've listed is addressed in this KB article: http://www.serv-u.com/kb/2167/Common-Vulnerabilities-and-Exposures-(CVEs)-Pertaining-to-Serv-U Having said that, yes, the OpenSSL library is getting updated soon.

The documentation for setting up LDAP is a bit misleading. We're getting it corrected. The documentation instructs you to drop the base DN when setting up your LDAP User Groups. This is incorrect. You must include the base DN in your hierarchy. To use the help documentation example, if your user is "CN=John…

Pulling the email address from Windows Auth is a common feature request. If the effort to migrate isn't too great for you, you could use LDAP instead as that authentication method will pull in the information and prepopulate it for you. Since AD runs on LDAP, the effort shouldn't be too much unless you're making extensive…

If you've followed the advice in the articles you linked, then here's a couple things you'll want to try: * What format are you using for your login ID? Are you using the full UPN? Do you have a suffix defined in your Windows Authentication settings within Serv-U? The suffix is appended to the login ID provided when…

This isn't currently possible with this feature. We do have a logged feature request to allow shares to remain open indefinitely while the files themselves expire, which I believe would meet the biggest requirement of what you're looking to do.

Unfortunately, Serv-U doesn't support single sign-on as described here. It can reuse credentials from an external system like LDAP or AD, but users must still provide those credentials for Serv-U to log them in.

Serv-U doesn't necessarily need to be installed on the same file server where the files reside, although you'll get better performance out of it if file transfers aren't going to / coming from a network path. You can use UNC paths in the home directories of the Serv-U groups & users to access storage located elsewhere. If…

This isn't currently supported. I know I've seen a feature request to allow certain groups to view/manage each other's shares, but I'm not sure I've seen one for an admin to have the ability to view/manage all of them within their administrative reach.

If the user accounts are stored locally, then they're stored in individual files in C:\ProgramData\RhinoSoft\Serv-U\Users\<loginID>.Archive. Direct modification of these files isn't officially supported and can be risky. However, for bulk actions like this, it could work if done carefully. The home directory for each login…

I don't think there is a way for a program to know whether or not a folder is a mount point without providing it with knowledge of your file system (and intentions) that most programs shouldn't need to worry about. I think there are better ways to achieve what you're looking to do: * Use an automounter to ensure the mount…

There will be a noticeable slowdown when the initial load of Web Client takes place through Gateway. This is to be expected with any proxy server as all connections must occur twice (at the proxy level and the server level) while all data must be forwarded through both points as well. This is most noticeable with HTTP and…