dougpapenthien

Comments

  • Serv-U 15.1.0 contains some improvements in this area. * LDAP users should still auto-populate the full name and email address according to the values coming from the LDAP server. If they're not, then the attribute mappings may not be correctly configured. * AD users should now see their full name and email address get…
  • When you refer to the "Password Request Page", are you talking about the page guest users receive when attempting to access a password protected share that's been sent to them? If so, then this issue has been corrected in the v15.1.0 release.
  • Setup an HTTP listener on the regular port 80, then setup a limit for the Domain | Limits & Settings | Connection | Require secure connection before login --> true. When a user connects via regular HTTP, they will be redirected to the corresponding HTTPS listener by default.
  • It may be a problem with the format of the certificate. I would need more details to say for sure. I'm assuming you've already worked with someone in support regarding this. Can you request that they reopen the case so we can take a look?
  • The recent release of Serv-U v15.1.0 adds support for pulling a user's full name and email address from AD so it should be auto-populated in the file share wizards.
  • Serv-U v15.1.0.480 has a separate field that lets you customize the default subject of a file share. Domain | Limits & Settings | File Sharing | Invitation Subject Template.
  • Are you talking about the title on the login page or the Web Client itself after you login? If it's the former, then this is already supported. Domain | Limits & Settings | Settings | HTTP Login Title Text. The field does not support HTML. It inserts the provided text into the <title> tag for the login page.
  • You can setup a limit to require secure connections (Domain Limits & Settings | Limits | Connection | Require secure connection before login). Once this done, Serv-U expects FTP clients to negotiate a secure connection before it will process a login attempt. Doing so will also cause connections to a regular HTTP listener…
  • This has been corrected in Serv-U v15.1.0.
  • Serv-U should work just fine with a wildcard certificate. As far as the server is concerned, it just presents the certificate when required by the protocol/negotiation. It's up to the client whether or not to accept a wildcard certificate. Re: Want to use my company certificate on the FTPS. Can I do that ?
  • Serv-U v15.1.0 supports this. Admins can now define a limit on guest expiration of less than 90 days. Admins can also remove an individual user's ability to configure this value. So you can either say "expires at any length less than 'x' days" or "all links expire after 'x' days".
  • Did you make sure to create a directory access rule in the default LDAP user group for the home directory? The easiest way to define one is to use the %HOME% macro for the path as this will always translate to whatever value is entered for the home directory. At a minimum, you should have read access defined for this rule.
  • Excellent. I'm glad we got it working!
  • You don't need to setup the directory access rules for the user. The file sharing feature does not use these settings since guest user access is restricted to a specific file share rather than a physical path. You also shouldn't need to share anything from within Windows itself. The Serv-U process will obviously need to be…
  • The temporary workaround is to disable everything BUT RC4. RC4 has known attack vectors but depending on who you ask/trust, they're not currently practical. If you disable SSLv2 and everything but RC4, you should see this with a Qualy scans: Lack of FIPS support in client software is, unfortunately, not something we can…
  • Direct modification of the settings file isn't something we support or encourage. It's not intended to be a user-friendly format for editing. However, it can be useful in locating the origin of a setting that you can't otherwise location through the UI. In this particular case, because the event is USER_ADDED and you're…
  • In order for Gateway to listen on an IP address it thinks isn't a private IP, you'll need to add an entry to the Accept-Public-IP-CIDRs.txt file in the Gateway install directory. The entry should be for the IP address owned by Serv-U that's responsible for the Gateway. Once Gateway knows what "external" IP address to…
  • I'm glad you got it working. Let the support rep know and they'll close out the case. Thanks!
  • Yes, clustered environments are affected by this situation. We usually recommend for clustered environments that a single instance is defined as the "master" and recommend the majority of administration takes place from this instance to minimize impact. However, the caching only affects changes made to existing user…
  • These look like the file sharing settings configured globally (at the server level). My guess is that the value is being overridden at the domain level. Can you take a look at your settings for the domain you're using to access file sharing?
  • Are you trying to upload as a guest to a share that was already created when the bad path value was being used? I believe the path for a share is set at the time the share is created, so it can differ from the current file sharing repository value. If that's the case and you now have a full path for this configuration…
  • The suggestion to disable the MLSD command is a good one, if only to see if it starts working as expected. I had assumed that SyncBack was using the older LIST command, which apparently it's not. After disabling MLSD, I don't recommend changing the list style to IIS or DOS. By default, it'll use the UNIX style listings I…
  • You need the entire hierarchy defined in the LDAP groups in order for Serv-U to map them properly. Using your example, if I have a user where the memberOf attribute contains this entry: CN=FTP-Admin,OU=users,DC=test,DC=local Then my groups need to be setup as follows: -local -test -users -FTP-Admin At least one of these…
  • POODLE is MITM attack exploited when the client & server use a CBC cipher during an SSLv3 session. What makes this more dangerous is that the MITM can force the client & server to use SSLv3 even if they both support TLS (and would normally negotiate a TLS session) through another "attack". For applications that don't…
  • Did you just leave the management console open to the groups page all weekend? If so, you'll never see the change due to some performance optimizations in the engine/browser communication protocol that makes the assumption that only valid admin sessions will be changing the data. I believe ODBC group data may be cached in…
  • If you open a support ticket with SolarWinds regarding this issue and mention this Thwack thread stating that you want to know when the new version is available, you can be put on a list that will receive notification when an RC is available for testing.
  • The JavaScript error is an indication that your browser security settings are probably interfering with the user interface by preventing it from making an AJAX request to the server (I believe IE uses an ActiveX object to implement their AJAX object used by JavaScript): Error: Automation Server can't create object
  • A USER_ADDED event named "User Welcome Message" is created if you used the "Create Common Events" button. As has been mentioned, this can be done in any of 4 places (server, domain, group, or user). Since you're not using ODBC authentication, this means the event is stored in the Serv-U settings somewhere. A support agent…
  • The only reason this should be happening is if your IE11 is reporting itself to the page as IE7 or older. If you've ever opened the developer tools for the browser (using F12) and modified the browser mode or document mode values, this could happen. Is it possible this has been done?
  • Ok, let me make sure I understand correctly. You want to limit it so that only certain groups in AD can login to Serv-U? If so, the easiest way to do this is to only define home directories for the groups that you want to access Serv-U. Be sure not to have a home directory defined for the Default Windows Group as every AD…