Ftp客户端

开发平台：

Visual C++

Help-Admin-Strings.strings：源码内容

$LINK_PRODUCT_HOME$=<a href="http://www.Serv-U.com/" target="_blank">http://www.Serv-U.com/</a>
$LINK_PRODUCT_SALES$=<a href="http://www.Serv-U.com/sales/" target="_blank">http://www.Serv-U.com/sales/</a>
$LINK_PRODUCT_SUPPORT$=<a href="http://www.Serv-U.com/support/" target="_blank">http://www.Serv-U.com/support/</a>
$LINK_PRODUCT_HELP_DESK$=<a href="http://www.Serv-U.com/prodsupport" target="_blank">Serv-U Help Desk</a>
$LINK_PRODUCT_KB$=<a href="http://www.Serv-U.com/kb/" target="_blank">http://www.Serv-U.com/kb/</a>
$LINK_PRODUCT_PURCHASE$=<a href="http://www.Serv-U.com/purchase/" target="_blank">http://www.Serv-U.com/purchase/</a>
$LINK_PRODUCT_PRICING$=<a href="http://www.Serv-U.com/pricing/" target="_blank">http://www.Serv-U.com/pricing/</a>
$LINK_CUSTOMER_SERVICE$=<a href="http://www.RhinoSoft.com/customer/" target="_blank">RhinoSoft.com Online Customer Service Center</a>
$LINK_DNS4ME$=<a href="http://www.DNS4Me.com/" target="_blank">DNS4Me</a>
$RHINOSOFT_CONTACT_INFO$::
RhinoSoft.com
P.O. Box 53
Helenville, WI 53137
U.S.A.
Sales: +1 (262) 560-9627
Phone: +1 (262) 560-9627
FAX: +1 (262) 560-9628
$LINK_PRODUCT_HOME$
$LINK_PRODUCT_SALES$
$LINK_PRODUCT_SUPPORT$
::END
$LINK_HELP_EDITIONS$=<a href="/?InternalDir=Admin&InternalFile=Help/Help-ServU-Editions.htm">Serv-U Editions</a>
$LINK_HELP_UIC$=<a href="/?InternalDir=Admin&InternalFile=Help/Help-UIC-Info.htm">User Interface Conventions</a>
$LINK_HELP_RATIOS$=<a href="/?InternalDir=Admin&InternalFile=Help/Help-User-Quotas-Ratios.htm">Transfer Ratios</a>
$LINK_HELP_SYSTEM_VARS$=<a href="/?InternalDir=Admin&InternalFile=Help/Help-System-Variables.htm">System Variables</a>
$LINK_HELP_LOG_SETTINGS$=<a href="/?InternalDir=Admin&InternalFile=Help/Help-Configure-Logs.htm">Domain Log Settings</a>
$LINK_HELP_GUIDE$=<a href="/?InternalDir=Admin&InternalFile=Help/Help-Quick-Start.htm">Quick Start Guide</a>
$LINK_HELP_VIRTUAL$=<a href="/?InternalDir=Admin&InternalFile=Help/Help-Virtual-Hosts.htm">Virtual Host</a>
$LINK_HELP_DIRACCESS$=<a href="/?InternalDir=Admin&InternalFile=Help/Help-Directory-Access.htm">Directory Access Rules</a>
$LINK_HELP_USER_LIMITS$=<a href="/?InternalDir=Admin&InternalFile=Help/Help-Limits-Settings-User.htm">Password Limits</a>
$LINK_HELP_GROUPS$=<a href="/?InternalDir=Admin&InternalFile=Help/Help-About-Groups.htm">Groups</a>
$OVERVIEW_HEADER$=Serv-U File Server Overview
$OVERVIEW1$::
Welcome to the Serv-U File Server!
The Serv-U File Server is a multi-protocol file server capable of sending and receiving files from other networked computers through various
means. Administrators create accounts for users that allow access to specific files and folders on the server's hard drive or any other
available network resource. These access permissions define where and how the users can access the available resources. Serv-U's
multi-protocol support means that users can employ whatever access method is available to them when connecting to your server. The Serv-U
File Server supports the following protocols:
::END
$OVERVIEW_PROTOCOLS$::
FTP (File Transfer Protocol)
HTTP (Hyper Text Transfer Protocol)
FTPS (FTP over SSL)*
HTTPS (HTTP over SSL)**
SFTP using SSH2 (File Transfer over Secure Shell)**
::END
$OVERVIEW_EDITION_NOTE$::
* - Requires Serv-U Gold or Silver Edition
** - Requires Serv-U Gold Edition
::END
$OVERVIEW2$::
In addition to Serv-U's excellent support for a large collection of the most popular FTP clients, you can now use your favorite web browser or SSH client to
connect and transfer files to and from Serv-U. Server administrators looking to provide a full-featured FTP client to users that may not have an FTP client
license of their own can even license FTP Voyager JV - a Java enabled FTP client delivered to the user after logging in to their Serv-U account. For more
information on licensing <a href="http://www.Serv-U.com/Web-FTP-Client.asp" target="_blank">FTP Voyager JV, click here</a>.
The Serv-U File Server maintains the Serv-U brand's legendary feature set and continues to raise the bar for file servers by enabling you to:
::END
$OVERVIEW_LIST$::
Access files from anywhere
Share files with friends, family, and clientèle
Provide employees in the field with a central location to send and receive data files
Full group support that streamlines user creation and maintenance
View images in thumbnails and slide shows, generated on-the-fly to minimize bandwidth usage
Administer the server through a custom-built web interface
Chat with FTP clients and view session logs in real time
Customize FTP command responses
Create custom limits and rules at an extremely granular level to control resource usage on the server
Connect securely using SSL/TLS or SSH2
Use 3rd party digital certificates to guarantee the server's identity to clients
Host multiple domains on the same IP address and port
Utilize multiple sources of authentication on the same domain (local user database, NT/SAM, ODBC)
Automatically build the tables necessary for ODBC authentication
...and much more!
::END
$OVERVIEW3$::
Serv-U is trialware that functions as the unlimited "Gold Edition" for 30 days. Registration entitles you to 1 year of free software updates (upgrade protection) and free email technical support. Licenses
are also available at a discounted price that extends the upgrade protection coverage to 2 years.
::END
$SERVU_EDITIONS_HEADER$=Serv-U Editions
$SERVU_EDITION_INTRO$::
The Serv-U File Server is available in three different versions designed to meet the various needs of today's server administrators. RhinoSoft.com
offers a Bronze Edition with the core tools and features, a Silver Edition which adds support for FTPS(SSL) and Virtual Hosts, and a Gold Edition that offers an enterprise feature-set
designed for use by medium to large corporations with high volume file server traffic.
::END
$SERVU_BRONZE_HEADER$=Serv-U Bronze Edition
$SERVU_BRONZE_BODY1$::
Serv-U Bronze Edition offers a robust feature set with all the tools for managing and transferring files:
::END
$SERVU_BRONZE_LIST$::
One domain with twenty-five concurrent connections
Fifty user accounts
Support for HTTP Web Client
Support for virtual path mapping
Support for transfer ratios and quotas
::END
$SERVU_SILVER_HEADER$=Serv-U Silver Edition
$SERVU_SILVER_BODY$::
Serv-U Silver Edition extends the capabilities of the Bronze Edition by adding:
::END
$SERVU_SILVER_LIST$::
Three domains with 100 concurrent connections
250 user accounts
Support for encrypted FTPS connections
Support for Virtual Hosts
User Password Recovery via HTTP login page
::END
$SERVU_SILVER_LIST_OLD$::
Three domains with 100 concurrent connections
250 user accounts
Support for encrypted FTPS connections
Support for Virtual Hosts
::END
$SERVU_GOLD_HEADER$=Serv-U Gold Edition
$SERVU_GOLD_BODY$::
Serv-U Gold Edition addresses the need for an enterprise file server with no limitations and the ability to continue growing with your business.
In addition to the encrypted FTPS support in the Silver Edition, Serv-U Gold Edition adds SSH and HTTPS support. With this in mind, Serv-U
Gold Edition has the following additional capabilities:
::END
$SERVU_GOLD_LIST$::
Unlimited domains with an unlimited number of concurrent connections
Unlimited number of user accounts
FIPS 140-2 support, certified through OpenSSL (Certificate #1051)
Support for Custom HTTP Logo
Support for User and Group Statistics
Support for encrypted HTTPS connections
SFTP using SSH2 (File Transfer over Secure Shell)
Support for remote administration of multiple servers from a single location
Support for ODBC database storage of user and group accounts
Support for NT-SAM / Active Directory based user accounts
Support for email, external program, and balloon tip events
::END
$SERVU_GOLD_LIST_OLD$::
Unlimited domains with an unlimited number of concurrent connections
Unlimited number of user accounts
Support for Custom HTTP Logo
Support for User and Group Statistics
Support for encrypted HTTPS connections
SFTP using SSH2 (File Transfer over Secure Shell)
Support for remote administration of multiple servers from a single location
Support for ODBC database storage of user and group accounts
Support for NT-SAM / Active Directory based user accounts
Support for email, external program, and balloon tip events
::END
$SERVU_EDITIONS_LINK_INFO$=<a href="http://www.Serv-U.com/" target="_blank">Click here</a> for more information about the three editions of the Serv-U File Server.
$HOW_TO_PURCHASE_HEADER$=How To Purchase Serv-U
$HOWTOPURCHASE$::
Serv-U is available as a fully functional Gold Edition trial for 30 days after the date of initial installation. In order to continue using Serv-U with
its full set of features, a Serv-U license must be purchased.
A license can be purchased online at $LINK_PRODUCT_PURCHASE$. Simply choose which Edition of the Serv-U File Server is required and the quantity to purchase
(discount pricing applies for bulk purchasing). A Serv-U File Server license must be purchased before adding an FTP Voyager JV license to your shopping cart.
Licenses of FTP Voyager (our premier FTP client software) may also be bundled at the time of purchase at a substantial discount.
Pricing information can be found at: $LINK_PRODUCT_PRICING$.
If you have lost your registration ID, it can be retrieved at: $LINK_CUSTOMER_SERVICE$.
Once the purchase has been completed, an email containing the registration details is immediately sent. If it is not received within an hour, check your
Spam filter to make sure that the email has not been filtered. Occasionally, the .reg installation file attached to our messages is blocked. If this should
happen, simply register using the "Register Manually" directions in the email.
::END
$PO_ORDER_HEADER$=Ordering By PO
$ORDERING_BY_PO1$::
Purchase orders can be sent to RhinoSoft.com in one of three ways:
::END
$POORDERLIST1$::
E-Mail PO (PDF/JPG/GIF Format Preferred) to a Sales Representative at $LINK_PRODUCT_SALES$.
Fax PO to +1 (262) 560-9628
Mail directly to RhinoSoft.com
::END
$RHINO_MAILING_ADDRESS$::
RhinoSoft.com
P.O. Box 53
Helenville, WI 53137
U.S.A.
::END
$TECHNICAL_SUPPORT_HEADER$=Technical Support
$TS_INTRO$::
Have a question and need more help? RhinoSoft.com offers a variety of technical support options. For current product support policies, please refer to the
$LINK_PRODUCT_HELP_DESK$.
Users who purchased their copy of Serv-U from an Official RhinoSoft.com reseller are referred back to their reseller for support. Telephone technical
support is available. Information on pricing for telephone technical support, including the minimum phone support charge, can be found at the
$LINK_PRODUCT_HELP_DESK$. Premium Support Contracts are also available, which includes priority
email technical support and covers 5 telephone technical support incidents.
If you have lost your registration ID, please visit the $LINK_CUSTOMER_SERVICE$.
::END
$TS_FREE_EMAIL$=Free Email Support
$TS_FREE_EMAIL_INFO$::
Free technical support is available via email to all users. RhinoSoft.com asks that all users submit their inquiries to $LINK_PRODUCT_SUPPORT$ for technical
support requests.
::END
$TS_KNOWLEDGE_BASE$=Knowledge Base
$TS_KNOWLEDGE_BASE_INFO$::
Our Knowledge Base is a dynamic support tool that you can use to research solutions to your questions and problems. Nearly every technical question posed to
our technical support team is answered here. The Knowledge Base can provide immediate, informative, step-by-step answers with screenshots to your questions.
Visit $LINK_PRODUCT_KB$ to get answers now.
::END
$TS_SALES_SUPPORT$=Sales Support
$TS_SALES_SUPPORT_INFO$::
Sales questions (of a non-technical nature) relative to the Serv-U File Server software should be directed to: $LINK_PRODUCT_SALES$. Sales representatives
can also be reached by calling RhinoSoft.com at +1 (262) 560-9627.
Technical Support options are subject to change without notice at the discretion of RhinoSoft.com
::END
$CONTACT_HEADER$=Contacting RhinoSoft.com
$CONTACT_INTRO$::
If you have lost your registration ID, please visit the $LINK_CUSTOMER_SERVICE$.
You may contact RhinoSoft.com by snail-mail at:
::END
$CONTACT_SALES$::
For sales inquiries, visit: $LINK_PRODUCT_SALES$.
::END
$CONTACT_PRODUCT_INFO$::
For more information on the Serv-U File Server, visit: $LINK_PRODUCT_HOME$.
::END
$QUICK_START_HEADER$=Quick Start Guide
$QS_INTRODUCTION$::
Serv-U has been designed to be simple to configure with the flexibility and control you require to easily share files with others under the best security
possible. This Quick Start Guide helps you install the server, create your first domain, and add a user account to the new domain. Once you have
completed these simple steps, you will be able to connect to your new file server and start transferring files!
::END
$QS_INSTALLATION$=Installation
$QS_INSTALLATION_INFO$::
If you are installing Serv-U for the first time, simply follow the instructions on the installation screens to choose the install directory and configure any
desktop shortcuts for quickly accessing the server. You may also choose to install Serv-U as a system service, meaning that Serv-U is automatically started
when Windows is started - before any user logs on to the machine. This is useful if Serv-U is run on a dedicated server machine that doesn't regularly have
an interactive user session logged on to it. If Serv-U is not installed as a system service, it needs to be manually started after logging in to Windows.
If Serv-U is being installed over an existing Serv-U installation, we recommend creating a back-up of your original installation folder first. While Serv-U
can be safely installed over any existing installations and performs any necessary upgrades to data files and binaries, it is considered good data
management practice to backup critical components before upgrading them. If the installation being upgraded is older than version 7.0, you are also
prompted with a dialog pointing out some of the critical changes made after version 6 and how these changes affect your administration of the Serv-U File
Server.
Once installation is complete, the Serv-U Management Console is started. If you chose not to have the Serv-U Management Console started after installation,
you can always launch it by double-clicking on the Serv-U icon in your system tray, or right-clicking it and selecting the "Start Management Console" option.
::END
$QS_FIRST_DOMAIN$=Creating Your First Domain
$QS_FIRST_DOMAIN_INFO$::
Once the Management Console has finished loading, you are prompted if you would like to create a new domain if no domains are currently present. Clicking
Yes starts the domain creation wizard. This wizard can be run at any time by clicking on the New Domain button found
at the top of the Management Console and in the Change Domain dialog, which is accessible from any page within the Management Console.
There are 3 simple steps to creating a new domain on your Serv-U File Server.
The first step is to provide a unique name for the domain. The domain's name is not visible to any of its users nor does it affect how the domain is accessed
by others. It is simply an identifier for the domain to make identification and management of the domain easier for its administrators. The name must also be
unique so that Serv-U can distinguish it from other domains on the server. You can also provide any other descriptive comments for the domain in the space
provided for the description. By default, the domain is enabled and accessible to users. If you would like this domain to be temporarily unavailable
to users while you are configuring it, uncheck the Enable Domain box. Click Next to continue creating your domain.
The second step in creating a new domain is identifying the protocols this domain should use to provide access to its users. The standard file sharing
protocol is FTP (File Transfer Protocol) which operates on the default port of 21. However, any of these ports can be changed to a value of your choosing.
It's a good idea to use a port above 1024 if you're going to run the server on a non-default port. Please refer to the documentation on Serv-U Editions for
more information on which protocols are supported by each Serv-U Edition. Check the boxes next to the protocols you want the domain to support before clicking
Next to continue.
The third step is to specify the physical address used to connect to this domain. Normally, this is an IP address that users specify in order to
find your server on the Internet. Most home users can leave this option blank, which tells Serv-U to use any available IP address on the computer.
::END
$QS_FIRST_DOMAIN_ENCRYPT$::
The fourth and final step is to determine which encryption mode will be used when storing passwords on this domain. By default, all passwords are stored
securely using one-way encryption, which locks away the password once it is saved. However, when users are expected to take advantage of the "Password Recovery"
utility in the Web Client, it may be desirable to use two-way encryption so that Serv-U does not need to reset their passwords when password recovery is requested.
Finally, if the passwords should be stored in clear text Serv-U also allows passwords to be stored in clear text. This is not recommended, but may be necessary for
integration with legacy systems (especially when using database support).
::END
$QS_FIRST_DOMAIN_DONE$::
Now, click Finish to have Serv-U create your first domain. Congratulations! You now have your first domain online. There are
additional properties that can be configured for the domain at another time. For more information on these options, see the documentation on
Domain Settings. Now, you need to create a user account to start sharing files through this domain.
::END
$QS_FIRST_USER$=Creating Your First User Account
$QS_FIRST_USER_INFO$::
After your first domain is created, you are taken to the user's page of the Management Console and asked if you want to create a new user account with the new
user wizard. Clicking Yes starts the new user account wizard. This wizard can be run at any time by clicking on the "Wizard" button found on
the user account page. There are 4 easy steps to creating a new user account.
::END
$QS_FIRST_USER_LOGIN_OLD$::
The first step is to provide a unique login ID for the account. This login ID is used to begin the authentication process when connecting to the domain.
The login ID must be unique for this domain, however other domains on your server may have an account with the same login ID. To create an anonymous
account, specify "anonymous" or "ftp" for the login ID. Click Next to continue creating the user account.
::END
$QS_FIRST_USER_LOGIN$::
The first step is to provide a unique login ID for the account. This login ID is used to begin the authentication process when connecting to the domain.
The login ID must be unique for this domain, however other domains on your server may have an account with the same login ID. To create an anonymous
account, specify "anonymous" or "ftp" for the login ID.
At this time, a Full Name and an email address may also be specified for the user account. The Full Name provides a canonical name with which to refer to
the user account, and the email address allows Serv-U email notifications and recovered passwords to be sent to the user account. Click
Next to continue creating the user account.
::END
$QS_FIRST_USER_PASSWORD$::
After specifying a unique login ID, you must also specify a password for the account. The password is the second piece of information required to
authenticate a user when they connect to the domain. In order for another person to connect to this domain, they must know the login ID specified in step 1,
and this password. It is possible to leave this password blank, however that allows anyone who knows the login ID to access your domain. Click
Next to continue.
The third step is specifying a home directory for the account. The home directory is the location on the server's hard drive (or accessible network resource)
that the user account is placed in upon successful login. Essentially, it's the location you want the user account to use when sending and receiving files
on the server. Clicking the Browse button allows you to browse to a location on your hard drive, or it can be typed in manually. If the user
is locked in their home directory, they are not able to access files or folders above the directory structure of their home directory. Additionally, the
actual location of their home directory is masked and displayed as "/". Click the Next button to proceed to the final step.
The final step is granting access rights to the user account. Access rights are granted on a per directory basis. However, they can be inherited by all
subdirectories contained in an accessible directory. The default access is "Read Only", which means that the user can list files and folders in their home
directory and download them. However, they cannot upload files, create new directories, delete files/folders, or rename files/folders. If "Full Access" is
selected, the user is able to do all of these things. After the user is created, these access rights can be configured on a more granular basis by
editing the user, and selecting the "Directory Access" tab. After selecting the directory access rights, click the Finish button to create
the user account.
Congratulations! Your Serv-U File Server is now accessible and ready for sharing. You can create more accounts just like this one to share it with other
friends, family, or colleagues. Each user can have a different home directory allowing you to share different files with different people. There are many
more user configurable options that let you fine-tune an account's access to the server. For more information on these options, refer to the documentation
on User Accounts.
::END
$SERVER_CONCEPTS_HEADER$=Server Concepts
$SERVER_CONCEPTS_INTRO$::
The Serv-U File Server makes use of several concepts that aid in the understanding of how to configure and administer your File Server as a single, hierarchical
unit. There are four related levels of configuration to the Serv-U File Server: the Server, the Domain, the
Group, and the User. Of all of these, only the Group is optional - all the other levels are mandatory
parts of the File Server. An explanation of each level is provided below.
::END
$SERVER_CONCEPTS_SERVER_HEADER$=Server
$SERVER_CONCEPTS_SERVER_BODY$::
The Server is the basic unit of the Serv-U File Server and the highest level of configuration available. It represents the File Server as a whole and governs
the behavior of all Domains, Groups, and Users. The Serv-U File Server ships with a set of default options that can be overridden on a per setting basis. Thus,
the Server is at the top-level of the hierarchy of configuring Serv-U. Domains, Groups, and Users inherit their default settings from the Server. Inherited
settings can be overridden at each of these lower levels. However, some settings are exclusive to the Server, such as the PASV port range.
::END
$SERVER_CONCEPTS_DOMAIN_HEADER$=Domain
$SERVER_CONCEPTS_DOMAIN_BODY$::
A Server can contain one or more Domains. Domains are the interface through which Users connect to your File Server and access a specific User account. A
Domain's settings are inherited from the Server. It also defines the collection of settings that all of its Groups and User accounts inherit. If a Server setting
is overridden at the Domain level, then all of its Groups and User accounts inherit that value as their default value.
::END
$SERVER_CONCEPTS_GROUP_HEADER$=Group
$SERVER_CONCEPTS_GROUP_BODY$::
The Group is an optional level of extra configuration provided to make it easier to manage related User accounts that share many of the same settings. By using
a Group, administrators can quickly make changes that propagate to more than one User account instead of having to manually configure each one separately. A
Group inherits all of its default settings from the Domain it belongs to. It defines the collection of settings inherited by all Users who are a member of the
Group. Virtually every User level setting can be configured at the Group level, or overridden at the User level.
::END
$SERVER_CONCEPTS_USER_HEADER$=User
$SERVER_CONCEPTS_USER_BODY$::
The User is at the bottom of the hierarchy. It can inherit its default settings from multiple Groups (if it's a member of more than one Group) or from its
parent Domain (if it's not a member of a Group or the Group doesn't define a default setting). A User account identifies a physical connection to the
File Server and defines the access rights and limitations of that connection. Settings overridden at the User level cannot be overridden elsewhere and are
always applied to connections authenticated with that User account.
::END
$SERVER_CONCEPTS_COLLECTION_HEADER$=User Collections
$SERVER_CONCEPTS_COLLECTION_BODY$::
Unlike Groups, User Collections do not offer any level of configuration to the User accounts they contain. Instead, they simply offer a way to organize users
into containers for ease of viewing and administration. For example, Collections can be created to organize User accounts based upon Group membership, however
they must be manually maintained when User accounts change Group membership.
::END
$NAV_SERVU_HEADER1$=The Serv-U Management Console
$NAV_SERVU_INFO$::
The Serv-U Management Console is designed to provide quick and easy access to the File Server's configuration options in a familiar way. When viewing a
configuration page, you can return to the main Management Console page at any time by clicking on the Serv-U File Server logo in the top-left corner.
::END
$NAV_LAYOUT$=Management Console Layout
$NAV_LAYOUT_INFO$::
The Management Console is presented in the familiar control panel style layout and arranged in to categories of related options. Clicking a category header,
such as "Users", displays the user account management screen. From this screen, each of the sub-category configuration options is available. A sub-category
can also be selected to go directly to that sub-category's configuration page.
For Server Administrators, the Management Console is displayed in two columns. The right column displays categories related to configuring server-wide options
and settings. The left column displays categories related to configuring the active domain. To change the active domain, click the Manage Domain
button in the top-left corner of the Management Console and select a different domain to administer. Alternatively, the Change Domain button is
available in bottom-right corner of the footer. This method of changing the active domain can be employed from any Management Console page.
Domain Administrators only have access to configuring settings and options for their applicable domain and do not have access to the server-level categories
displayed to System Administrators.
::END
$NAV_MENU$=Navigation Menu
$NAV_MENU_INFO$::
The Navigation menu is located in the lower-left corner of the screen and provides direct links to all of the Serv-U configuration categories. It is context
sensitive and displays the relevant categories for the selection being configurated (Domain or Server) as well as an expandable list of configuration options
for the currently selected category.
::END
$NAV_TABS$=Tabbed Configuration Pages
$NAV_TABS_INFO$::
When opening a category from the Management Console, all related sub-category pages are displayed in tabs on the same screen. This allows for quick navigation
between related configuration options.
::END
$NAV_SERVU_WEB_CLIENT$=Launching A Web Client
$NAV_SERVU_WEB_CLIENT_INFO$::
While configuring the Serv-U File Server, an HTTP session can be launched by clicking the appropriate launch button in the toolbar at the bottom
of the page. If licensed for use, the Web Client is available and runs from within the browser. If licensed for use, FTP Voyager JV can also be
launched using the Java Runtime Environment, by clicking on the FTP Voyager JV button.
::END
$NAV_SERVU_THEMES$=Changing themes in Serv-U
$NAV_SERVU_THEMES_INFO$::
The "Theme" button, used to launch the theme menu, is located in the lower-right corner of the screen. The menu lists the available themes available
to change the look and feel of Serv-U. Simply select a theme from the drop down combo box then click the "OK" button. The theme will be loaded without
needing to refresh the page.
::END
$UIC_HEADER$=User Interface Conventions
$UIC_INTRO$::
The Serv-U File Server uses a consistent method of representing configuration options in a manner that not only conveys the current value of the option, but
also whether or not that value is the default (or inherited) value. Traditionally, this has been done with something called a tri-state checkbox. The tri-state
checkbox has two major drawbacks:
::END
$UIC_TRI_STATE_LIST$::
The default state does not clearly convey the current value of the option. In some versions of Windows, the box is checked with a grey background - even if the option isn't currently enabled!
They can only be used to represent binary values, which is to say they can only represent two values - on or off.
::END
$UIC_INTRO2$::
The Serv-U File Server uses a different, easy to understand convention that overcomes these drawbacks. When an option is inheriting its value from a parent,
the text of the option is displayed in regular, unbolded text. The value that is displayed (whether it's a text value or a checkbox) can change to
reflect changes made to the parent where the item is currently inheriting its value.
However, if the value is overriding the default, the text of the value is displayed in bold. The value that is currently displayed is
always the value of that option, regardless of changes to its parent.
::END
$UIC_CASEFILE1_HEADER$=Understanding User Interface Conventions
$UIC_CASEFILE1_BODY$::
To better illustrate the user interface conventions, consider the following case file.
Acme Technology Co. is a computer repair company that maintains a Serv-U File Server providing global access to shared corporate resources to their traveling
technicians. Each technician has their own account on the File Server. To facilitate easy administration of the user accounts, the File Server administrator
has made each user account a member of the "Technician" group. This group's Administration Privilege is set to No Privilege since none of the
technicians have any File Server administration duties.
::END
$UIC_CASEFILE1_BODY2$::
A technician receives a promotion. In addition to his current technician duties, he is also given administration privileges on the File Server so he can
assist other technicians with their accounts. The File Server administrator can simply edit the technician's user account and change the Administration
Privilege to Domain Administrator. The text of this option turns bold to reflect that it is overriding the default value (No Privilege) that
the user account inherits from its membership to the "Technician" group.
::END
$UIC_CASEFILE1_BODY3$::
At a later date, the Administration Privilege can be reverted back to the default value inherited from the "Technician" group by selecting the Inherit
default value option in the "Administration Privilege" drop-down box.
::END
$SERVER_OVERVIEW_HEADER$=Server Overview
$SERVER_OVERVIEW$::
The Serv-U File Server allows for certain settings to be configured at the Server level. When configured at the Server level, the settings apply to all Users,
Groups, and Domains on the Server unless those settings are overridden at a lower level. Settings that can be configured at the Server level include:
Directory Access rules, IP Access rules, bandwidth limitations, global user accounts (user accounts which can log into any Serv-U Domain), and more. Detailed
information on each setting and how it can be configured is listed in the help pages below.
::END
$IP_ACL_HEADER$=IP Access Rules
$IP_ACCESS_TXT$::
IP Access rules are an additional form of user authentication that can restrict login access to specific IP addresses, ranges of IP addresses, or even a domain
name. IP Access rules can be configured at the Server, Domain, Group, and User levels. The level at which an IP access rule is specified also defines how far
a connection is allowed before being rejected. Server and Domain level IP access rules are applied before the Welcome message is sent. Domain level IP access
rules are also applied when responding to the HOST command to connect to a virtual domain. Group and User level IP access rules are applied in response to a
USER command when the client identifies itself to the server.
Specifying these rules ensures that only clients in certain networks can login. To configure IP Access rules, first specify what clients are allowed to login
or not allowed to login. Add rules by clicking the Add button and specifying what IP addresses or range of addresses are to be applied to the
rule. If a dynamic DNS service, such as $LINK_DNS4ME$ is used, then a domain name can be specified in place of an IP address to allow access to clients that
travel and don't have a static IP address. Reverse DNS names are also acceptable. If a domain name or reverse DNS rule is created, Serv-U must perform either
a reverse DNS look-up or DNS resolution in order to apply these rules. This can cause a slight delay during login depending upon the speed of the system's
DNS server.
Special formatting allows ranges and wildcards to be used, as below:
::END
$IP_ACCESS_RULE_EXACT$=xxx
$IP_ACCESS_RULE_EXACT_TXT$=An exact match such as 192.168.1.1.
$IP_ACCESS_RULE_RANGE$=xxx-xxx
$IP_ACCESS_RULE_RANGE_TXT$=A specified range of IP addresses such as 192.168.1.10-19.
$IP_ACCESS_RULE_STAR$=*
$IP_ACCESS_RULE_STAR_TXT$=Any valid IP address value such as 192.168.1.*, which is analogous to 192.168.1.0-255.
$IP_ACCESS_RULE_QUESTION$=?
$IP_ACCESS_RULE_QUESTION_TXT$=Any valid character when specifying a reverse DNS name such as server?.mydomain.com.
$IP_ACCESS_RULE_SLASH$=/
$IP_ACCESS_RULE_SLASH_TXT$=The slash separator allows the use of CIDR notation to specify which IP addresses should be allowed or blocked. Common CIDR blocks are /8 (for 1.*.*.*), /16 (for 1.2.*.*) and /24 (for 1.2.3.*). The block /32 can be used to specify a single IP address.
$IP_ACCESS_ABOUT$::
IP access rules are applied in the order they are displayed. In this way, specific rules can be placed at the top to allow (or deny) access before a more
general rule is applied later on in the list. The arrows on the right side of the list can be used to change the position of an individual rule in the list.
::END
$IP_ACCESS_APPROVED$::
Approved addresses already appearing in the list do not become automatically blocked by the anti-hammering rule. For example, a local IP address 192.168.0.17
causes Serv-U to initiate its anit-hammer rule to ban the IP addres, but 192.168.0.17 is explicity approved in the list, 192.168.0.17
is not automatically blocked by the anti-hammer rule.
Here's how it works. Assuming the following IP access rules:
+ 192.168.0.17
+ *
When there's activity coming from 192.168.0.17, but the user gets the password wrong auto IP blocking (via timeout, anti-hammer, or by system admin from Sessions Activity) doesn't
occur because that IP address is specifically enabled. The bottom item * means everyone is approved, without this value only 192.168.0.17 would be approved.
If anti-hammer kicks in for a different IP address the blocked IP address gets added to the top of the list, so it looks like:
- 10.10.10.1
+ 192.168.0.17
+ *
If an entire block of IP addresses is desired, this also works as described:
+ 192.168.0.1-255
+ *
If anti-hammer kicks in on any of these IPs, the IP is not blocked. The key here is the wild card *. Serv-U also checks for *.*, *.*.*, *.*.*.* as being "any" IP address.
::END
$IP_ACCESS_SORT_HEADER$=Enable Sort Mode
$IP_ACCESS_SORT_INFO$::
This option allows the IP Access list to be sorted numerically rather than in the processing order. Displaying the IP Access list in sort mode will not
change the order in which rules are processed - to view rule precedence disable this option. Viewing the IP Access list in numerical order can be a valuable
tool when reviewing long lists of access rules to determine if an entry already exists.
::END
$IP_ACL_CASEFILE1_HEADER$=Case File - Contractor
$IP_ACL_CASEFILE1_BODY$::
A contractor has been hired on a temporary basis, and access to the Serv-U File Server is required for the contract work to be completed effectively. He is
granted access but should not be able to access the Server from locations outside of the field office as it would pose a risk to confidentiality. All of the
in-office workstations are assigned IP addresses from 192.168.10.2-192.168.10.254. Therefore, create a Allow Access rule as shown:
::END
$IP_ACL_CASEFILE1_BODY2$::
The rule shown above permits the contractor to access the file server from inside the office, but because of the creation of the "Allow Access" rule there is
an implicit "Deny All" rule added that prevents the account from being used anywhere else. He is granted the access necessary for the position, but the
administrator has greater control over where the data is accessed from.
::END
$IP_ACL_CASEFILE2_HEADER$=Case File - Open Kiosks
$IP_ACL_CASEFILE2_BODY$::
A user needs to be able to access the Server from within the office, but should not be able to log on from a set of open PC kiosks in the building for security
reasons. The kiosks are assigned IP addresses from 192.168.15.100-192.168.15.110. Therefore, create a Deny Access rule which denies access to
192.168.15.100-192.168.15.110. Keep in mind that because of the implicit "Deny All" rule added when using IP Access rules, an "Allow All" rule must be added
at the end of the list to allow the user to log on from all other address ranges by entering an Allow Access rule which allows access to "*.*.*.*". This rule
at the end ensures that connections are allowed from all other IP addresses.
::END
$IP_ACL_CASEFILE3_HEADER$=Case File - Access By Name
$IP_ACL_CASEFILE3_BODY$::
Users connecting from the examplesite.com Domain should be the only ones able to access the Domain. To restrict the users able to connect to the Domain,
implement an IP Access rule based on reverse DNS and host name. First, create a new access rule allowing access to *.examplesite.com.
NOTE: For such an access rule to work, the PTR records for the IP addresses in question must match the rule that has been created. Generally,
the connecting clients must be connecting from a large company with an IP range assigned to it for the connecting IP addresses to have such PTR records -
typically, dynamic IP addresses do not meet the requirement.
::END
$DATABASE_HEADER$=Database Access
$DATABASE_ACCESS_BODY1$::
Serv-U enables the use of an ODBC database to store and maintain group and user accounts at both the Domain and Server levels. The ODBC
connections are configured from two locations: Domain | Domain Details | Database and Server | Server Details | Database.
Serv-U can automatically create all of the tables and columns necessary to begin storing Users and Groups in your database. Because Serv-U uses one set of
table names to store its information, individual ODBC connections must be configured for each item which stores details in the database. In other words,
the Server as well as each Domain must have a unique ODBC connection to ensure they are stored separately. To configure a database, follow these steps:
::END
$DATABASE_PREP_LIST1$::
Create an ODBC connection for Serv-U to use. RhinoSoft.com recommends MySQL, but any database that has a Windows ODBC driver available can be utilized. Use a System DSN if Serv-U is operating as a system service, or a User DSN if Serv-U is operating as a regular application.
Open the Serv-U Management Console and browse to the appropriate Domain or Server database settings. Enter the Data Source Name (DSN), the login ID, and Password and click Save.
::END
$DATABASE_ACCESS_BODY2$::
If the database connection is being configured for the first time, leave the Automatically create options checked. With these options
checked, the Serv-U File Server builds the database tables and columns automatically.
::END
$DB_SQL_TEMPLATES$=SQL Templates
$DB_SQL_TEMPLATES_TXT$::
Serv-U uses multiple queries to maintain the databases containing User and Group information. These queries conform to the SQL language standards. However,
if the database you're using is having problems working with Serv-U, you may need to alter these queries. From the SQL Templates dialog, each query used by
Serv-U can be specially tailored to conform to the standards supported by your database.
NOTE: Incorrectly editing these SQL queries could cause ODBC support to stop working in Serv-U. Do not edit these queries unless you are
comfortable constructing SQL statements and are positive that it is necessary to enable ODBC support with your database software.
::END
$DB_TABLE_MAPPINGS$=User and Group Table Mappings
$DB_TABLE_MAPPINGS_TXT$::
By default, Serv-U automatically creates and maintains the tables and columns necessary to store User and Group information in a database. However, if you're
attempting to connect Serv-U to an existing database containing this information, you need to customize the table and column names to conform to the existing
database structure. Click the User Table Mappings or Group Table Mappings to get started.
Serv-U stores information for a User or Group in 10 separate tables. Only the User/Group Info Table and User/Group Dir Access Table are required. The current
table can be changed from the Object Table drop-down box. The Attribute column lists the attributes that are stored in the
current table. The Mapped Database Value displays the name of the column that attribute is mapped to in the database. The first row always
displays the "TableName" and can be used to change the name of the table.
Certain tables where the order of the entries bears significance have a SortColumn attribute listed. This column is used to store the order
in which rules are applied.
Click the Edit button or double-click the column name to edit a value.
::END
$DB_TABLE_MAPPINGS_TXT2$::
When enabled, the table is accessed as needed. In special situations a table that isn't being used may be disabled to reduce the number of ODBC (database)
calls. For example, if not using Ratios and Quotas "User Ratio-Free Files", "Per User Files Ratio", "Per User Bytes Ratio", "Per Session Files Ratio", and
"Per Session Bytes Ratio" tables may be disabled preventing unneeded ODBC calls. Exercise caution when disabling tables as the fields will appear in dialogs,
but they will not be saved or loaded. The "User Info" and "Group Info" tables cannot be disabled.
::END
$DATABASE_ACCESS_CASEFILE1_HEADER1$=Case File - ODBC Authentication
$DATABASE_ACCESS_CASEFILE1_BODY1$::
Authentication in the Serv-U File Server can be handled through an ODBC database, allowing for scripted account management and maintenance. In order to make use
of ODBC functionality, migrate to ODBC authentication through a database. By storing credentials in settings in a database, accounts can be managed from outside
the Serv-U Management Console via scripted database operations which can be built into many existing account provisioning systems. A DSN must first be created in
Control Panel | Administrative Tools | Data Sources (ODBC) - use a System DSN if Serv-U is running as a service or a User DSN if Serv-U is running as an
application. Once the proper DSN has been created, specify the Data Source Name, login ID and password and select Save. Serv-U creates the
tables and columns transparently. Database Users and Groups can be managed from the Database Users and Database Groups sections of Serv-U (located near the normal
Users and Groups tabs).
::END
$EVENTS_HEADER$=Serv-U Events
$EVENTS_BODY1$::
Serv-U enables the use of event handling which can perform various actions triggered by a list of selected events. Below is a list of actions
available to administrators:
::END
$EVENTS_SERVER$=Server Events
$EVENTS_LIST1$::
$SUEVENT_ID_SERVER_START_TEXT$
$SUEVENT_ID_SERVER_STOP_TEXT$
::END
$EVENTS_SERVER_DOMAIN$=Server and Domain Events
$EVENTS_LIST2$::
$SUEVENT_ID_DOMAIN_START_TEXT$
$SUEVENT_ID_DOMAIN_STOP_TEXT$
$SUEVENT_ID_SESSION_CONNECT_TEXT$
$SUEVENT_ID_SESSION_DISCONNECT_TEXT$
$SUEVENT_ID_SESSION_CONNECT_FAILURE_TEXT$
::END
$EVENTS_LIST2_FUTURE_FEATURE$::
$SUEVENT_ID_LOG_DELETED_TEXT$
::END
$EVENTS_ALL$=Server, Domain, User and Group Events
$EVENTS_LIST3$::
$SUEVENT_ID_USER_LOGIN_TEXT$
$SUEVENT_ID_USER_LOGOUT_TEXT$
$SUEVENT_ID_USER_LOGIN_FAILURE_TEXT$
$SUEVENT_ID_USER_PASSWORD_CHANGE_TEXT$
$SUEVENT_ID_USER_PASSWORD_CHANGE_FAILURE_TEXT$
$SUEVENT_ID_USER_ENABLED_TEXT$
$SUEVENT_ID_USER_DISABLED_TEXT$
$SUEVENT_ID_USER_DELETED_TEXT$
$SUEVENT_ID_IP_BLOCKED_TEXT$
$SUEVENT_ID_IP_BLOCKED_TIME_TEXT$
$SUEVENT_ID_TOO_MANY_SESSIONS_TEXT$
$SUEVENT_ID_TOO_MANY_SESSIONS_ON_IP_TEXT$
::END
$EVENTS_LIST3_FUTURE_FEATURE$::
$SUEVENT_ID_IP_ADDR_AUTO_BLOCKED_TIME_TEXT$
$SUEVENT_ID_USER_ADDED_TEXT$
$SUEVENT_ID_USER_PASSWORD_RECOVERY_SENT_TEXT$
$SUEVENT_ID_USER_PASSWORD_RECOVERY_FAILED_TEXT$
::END
$EVENTS_LIST3_2$::
$SUEVENT_ID_FILE_UPLOAD_TEXT$
$SUEVENT_ID_FILE_UPLOAD_FAIL_TEXT$
$SUEVENT_ID_FILE_DOWNLOAD_TEXT$
$SUEVENT_ID_FILE_DOWNLOAD_FAIL_TEXT$
$SUEVENT_ID_FILE_DELETE_TEXT$
$SUEVENT_ID_FILE_MOVE_TEXT$
$SUEVENT_ID_DIR_CREATE_TEXT$
$SUEVENT_ID_DIR_DELETE_TEXT$
$SUEVENT_ID_DIR_CHANGE_TEXT$
$SUEVENT_ID_DIR_MOVE_TEXT$
$SUEVENT_ID_QUOTA_OVERAGE_TEXT$
$SUEVENT_ID_DISK_SPACE_OVERAGE_TEXT$
::END
$EVENTS_ACTIONS$=Event Actions
$EVENTS_BODY2$::
Administrators can select from three different actions that will be executed when an event is triggered. Below is a list of these actions:
::END
$EVENTS_LIST4$::
$SUEVENT_ACTION_EMAIL_TEXT$
$SUEVENT_ACTION_BALLOON_TIP_TEXT$ (Server administrator only)
$SUEVENT_ACTION_EXEC_TEXT$ (Server administrator only)
::END
$EVENTS_EMAIL_ACTION$=Email Actions
$EVENTS_BODY3$::
Email actions can be configured to send an email when an event is triggered. Email actions contain an "To", "Subject" and "Message"
parameter. Special variables may be used to send specific data pertaining to the event. Please refer to the list of these variables located under "<a href="Help-System-Variables.htm">System Variables</a>".
::END
$FUTURE_FEATURE_EVENTS_BODY3$::
Email actions can be configured to send emails to multiple recipients and to Serv-U Groups when an event is triggered. To add an email address, enter it in the "To" or "Bcc" fields. To send mail to a Serv-U
Group, use the "Group" icon to add or remove Serv-U Groups from the distribution list. Email addresses must be seperated with commas or semicolons. Email actions contain an "To", "Subject" and "Message"
parameter. Special variables may be used to send specific data pertaining to the event. Please refer to the list of these variables located under "<a href="Help-System-Variables.htm">System Variables</a>".
::END
$EVENTS_BALLOON_ACTION$=Balloon Tip Actions
$EVENTS_BODY4$::
Balloon tip actions can be configured to show a balloon tip in the system tray when an event is triggered. Balloon tip actions contain a "Balloon Title" and "Balloon Message"
parameter. Special variables may be used to send specific data pertaining to the event. Please refer to the list of these variables located under "<a href="Help-System-Variables.htm">System Variables</a>".
::END
$EVENTS_EXEC_ACTION$=Execute Command Actions
$EVENTS_BODY5$::
Execute command actions can be configured to execute a command on a file when an event is triggered. Execute command actions contain an "Executable Path" and "Command Line Parameters"
parameter. Special variables may be used to send specific data pertaining to the event. Please refer to the list of these variables located under "<a href="Help-System-Variables.htm">System Variables</a>".
::END
$FUTURE_FEATURE_EVENTS_BODY5$::
Execute command actions can be configured to execute a command on a file when an event is triggered. Execute command actions contain an "Executable Path", "Command Line Parameters", and "Completion Wait Time"
parameter. For the "Completion Wait Time" parameter, you may enter the number of seconds to wait after starting the executable path. Enter a value of 0 for no waiting.
NOTE: any amount of time Serv-U spends waiting delays any processing that Serv-U can perform.
A wait value should only be used to give an external program enough time to perform some operation, such as move a log file before it is deleted (i.e., $LogFilePath for the "Log File Deleted" event).
Special variables may be used to send specific data pertaining to the event. Please refer to the list of these variables located under "<a href="Help-System-Variables.htm">System Variables</a>".
::END
$EVENTS_COMMON$=Creating Common Events
$EVENTS_COMMON_BODY$::
Serv-U allows administrators to automatically create a list of the most common events. You may choose to create these common events using email and/or balloon tip actions. Simply click the "Create Common Events"
button located in the "Events" tab. Select either the "Send Email" or "Show balloon tip" radio button for the action you want to be performed on the common events. If you choose to "Send Email" you must also enter an
"To:" address where the events are to be sent.
::END
$SMTP_CONFIG_HEADER$=Serv-U SMTP Configuration
$SMTP_CONFIG_BODY$::
Serv-U allows administrators to configure an SMTP connection to send email for events configured to use email actions. SMTP can be configured on the server and/or the domain level.
SMTP configuration at the domain level may be inherited from the server level. The SMTP configuration dialog is located in the "Events" tab in the "Domain Details" and "Server Details" pages.
Simply click on the "Configure SMTP" button to launch the dialog.
::END
$SMTP_CONFIG_SERVER_INFO$=SMTP Server Information
$SMTP_CONFIG_SERVER_INPUT$::
SMTP Server - the name or IP address of the SMTP server.
SMTP Server Port - the port the smtp server is using.
From Email Address - the email address to use for the outgoing email.
::END
$SMTP_CONFIG_FROM_NAME$::
From Name (optional) - the name to use for the outgoing email.
::END
$SMTP_CONFIG_SERVER_AUTH$::
My server requires authentication - to enable authentication check this box.
::END
$SMTP_CONFIG_SSL_CONN$::
This server requires a secure connection (SSL) - Some SMTP servers require that all incoming connections be encrypted to protect against possible attacks. If your server requires incoming SMTP connections to be encrypted, enable this option. The default port for encrypted SMTP connections is 465. Serv-U supports Implicit SSL only, and does not support Explicit SSL (port 587).
::END
$SMTP_CONFIG_AUTH_INFO$=Authentication Information
$SMTP_CONFIG_AUTH_BODY$::
If your SMTP server requires authentication you must enter the following information:
::END
$SMTP_CONFIG_AUTH_INPUT$::
Account Name - the account name associated with authentication for the SMTP server.
Password - the password for the account.
::END
$LICENSE_DETAILS_HEADER$=License Information
$LICENSE_DETAILS_BODY1$::
The License Details tab displays the information contained in the current registration ID in use by the Serv-U File Server. If the installation is running in
trial mode, then information on the number of trial days remaining is also included. Information contained on this tab includes:
::END
$LICENSE_DETAILS_NAME$=Name
$LICENSE_DETAILS_NAME_TXT$=The name associated with the current license.
$LICENSE_DETAILS_EMAIL$=Email Address
$LICENSE_DETAILS_EMAIL_TXT$=The email address associated with the current license.
$LICENSE_DETAILS_EDITION$=Serv-U Edition
$LICENSE_DETAILS_EDITION_TXT$=The Serv-U Edition that is enabled by the current license. See $LINK_HELP_EDITIONS$ for more information.
$LICENSE_DETAILS_COPIES$=Copies
$LICENSE_DETAILS_COPIES_TXT$=The number of concurrent installations allowed by the current license.
$LICENSE_DETAILS_DATE$=Purchase Date
$LICENSE_DETAILS_DATE_TXT$=The date the current license was purchased.
$LICENSE_DETAILS_UPDATES$=Updates
$LICENSE_DETAILS_UPDATES_TXT$=The date through which the current license allows free updates to the latest version. If running as a trial, the number of trial days remaining is displayed.
$LICENSE_DETAILS_INFO$=Edition Information
$LICENSE_DETAILS_INFO_TXT$=Displays enabled functionality and limitations of the licensed Serv-U Edition.
$LICENSE_DETAILS_PRODUCTS$=Additional Products
$LICENSE_DETAILS_PRODUCTS_TXT$=Additional add-ons for Serv-U and whether or not they are enabled.
$LICENSE_DETAILS_REGISTER_HEADER1$=Registering Serv-U
$LICENSE_DETAILS_REGISTER_BODY1$::
To Register the Serv-U File Server, click the Register button on the bottom toolbar and enter your alphanumeric registration ID. If you have
lost your ID, click on the Lost ID button for assistance in retrieving it. If you need to purchase an ID, click on the Purchase
button to visit our web site to purchase an ID.
::END
$PROG_INFO_HEADER$=Program Information
$PROG_INFO_BODY$::
The Program Information tab displays information about the current version of Serv-U installed on the server including:
::END
$PROG_INFO_BUILD$=Build Date
$PROG_INFO_BUILD_TXT$::
The date of the software build for the current installation.
::END
$PROG_INFO_INSTALL$=Install Date
$PROG_INFO_INSTALL_TXT$::
The original date that Serv-U was first installed on the computer.
::END
$PROG_INFO_VERSION$=Serv-U File Server Version Number
$PROG_INFO_VERSION_TXT$::
The full version number for the current installation.
::END
$PROG_INFO_CONTACT$=Contact Information
$PROG_INFO_CONTACT_TXT$::
The contact information for RhinoSoft.com. If you're administering Serv-U using a language other than English, contact information is also provided for the
Authorized RhinoSoft.com Reseller responsible for the translation.
::END
$PROG_INFO_DEV$=Development Information
$PROG_INFO_DEV_TXT$::
Information on the development and localization (if applicable) for the Serv-U File Server.
::END
$PROG_INFO_LEGAL$=Legal Disclaimer
$PROG_INFO_LEGAL_TXT$::
The Serv-U legal disclaimer.
::END
$LIMITS_SETTINGS_HEADER$=Limits and Settings
$LIMITS_SETTINGS_BASICS_BODY1$::
Serv-U offers advanced options which can be used to customize how it may be used as well as ways to apply limits and custom settings to Users,
Groups, Domains, and the Server in its entirety. The limits stack intelligently, with User settings
overriding Group settings, Group settings overriding Domain settings, and Domain settings overriding Server settings. In addition, limits can be applied only
during certain days of the week or times of the day. It is possible to grant exceptions to administrators and restrict specific Users more than others,
providing total control over the Server. The Limits and Settings in Serv-U are split into five categories: Connection, Password,
Directory Listing, Data Transfer, and Advanced.
To apply a limit, select the appropriate category, click on the Add button, select the limit, then select or enter the value. For example, to
disable the Lock users in home directory option for a Domain, follow these steps:
::END
$LIMITS_SETTINGS_BASICS_LIST1$::
Select Domain Limits & Settings link from the Serv-U Management Console.
Select Directory Listing from the "Limit Type" drop-down box.
Click the Add button.
Select Lock users in home directory from the "Limit" drop-down box.
Uncheck the option.
Click the Save button.
::END
$LIMITS_SETTINGS_BASICS_BODY2$::
The limits list displays the current limits applied to the domain. Limits with a light-blue shade to the background are default values. Limits with a white
background are values that override the defaults. After completing the above steps, a new Lock users in home directory limit appears in the
list that displays "No" for the value. Because of inheritance rules, this option applies to all users in the domain unless overridden at the Group or User
level. For more information on this method of inheritance, see the $LINK_HELP_UIC$ section of the Help documentation.
Limits can be deleted by selecting them and clicking the Delete button. To edit an overridden value, select the limit and click the
Edit button. Default rules cannot be edited or deleted. Create a new limit to override a default one.
To create a limit that is restricted to a specific time of day or days of the week, click the Advanced button from the New / Edit Limit dialog.
The additional options allow you to Apply limit only at this time of day at which point a start and stop time for the new limit can be entered.
To restrict the limit to certain days of the week, uncheck the boxes next to the days you don't want the limit applied. When a limit is restricted in this way,
default values (or the value of other limit overrides) are applied when the time of day or day of the week restrictions are not met for this limit.
::END
$LIMITS_SETTINGS_SERVER$::
The following is a reference of all available Server limits, organized by category.
::END
$LIMITS_SETTINGS_DOMAIN$::
The following is a reference of all available Domain limits, organized by category.
::END
$LIMITS_SETTINGS_GROUP$::
The following is a reference of all available Group limits, organized by category.
::END
$LIMITS_SETTINGS_USER$::
The following is a reference of all available User limits, organized by category.
::END
$CONNECTION_LS_HEADER$=Connection
$CONNECTION_LS_USER_GROUP_LIST_HEADER$=Connection
$CONNECTION_LS_HOMEDIR$=Automatically create home directories
$CONNECTION_LS_HOMEDIR_TXT$::
Instructs Serv-U on whether or not to automatically create the home directory specified when creating a new user account if the directory does not already
exist.
::END
$CONNECTION_LS_ANTI_TIMEOUT$=Block anti-timeout schemes
$CONNECTION_LS_ANTI_TIMEOUT_TXT$::
Blocks the use of commands such as "NOOP", which is commonly used to keep FTP Command Channel connections open during long file transfers or other periods
of inactivity where no information is being transferred on the control channel. When these are blocked, Serv-U disconnects the client when the connection
has been idle, i.e., not transferring data, for a specified period of time.
::END
$CONNECTION_LS_IDLE$=Automatic idle connection timeout
$CONNECTION_LS_IDLE_TXT$::
Specifies the number of minutes that must pass after the last client data transfer before a session is disconnected for being idle.
::END
$CONNECTION_LS_SERVER_SESSIONS$=Maximum number of sessions on server
$CONNECTION_LS_SERVER_SESSIONS_TXT$::
Specifies the maximum number of concurrent sessions that may be allowed on the entire Server.
::END
$CONNECTION_LS_SERVER_IP_SESSIONS$=Maximum sessions per IP address on server
$CONNECTION_LS_SERVER_IP_SESSIONS_TXT$::
Specifies the maximum number of concurrent sessions that may be opened to the entire Server from a single IP address.
::END
$CONNECTION_LS_USER_IP_SESSIONS$=Maximum sessions per IP address for user account
$CONNECTION_LS_USER_IP_SESSIONS_TXT$::
Specifies the maximum number of concurrent sessions that a User may open from a single IP address.
::END
$CONNECTION_LS_USER_SESSIONS$=Maximum number of sessions per user account
$CONNECTION_LS_USER_SESSIONS_TXT$::
Specifies the maximum number of concurrent sessions that may be opened from a single User account.
::END
$CONNECTION_LS_SECURE$=Require secure connection before login
$CONNECTION_LS_SECURE_TXT$::
Requires that a connection be secure, (e.g., FTPS, SFTP, or HTTPS), before it is accepted.
::END
$CONNECTION_LS_TIMEOUT$=Automatic session timeout
$CONNECTION_LS_TIMEOUT_TXT$::
Specifies the number of minutes a session is allowed to last before being disconnected by the Server.
::END
$CONNECTION_LS_BLOCK_IP_SESSION_TIMEOUT$=Block IP Address Of Timed Out Session
$CONNECTION_LS_BLOCK_IP_SESSION_TIMEOUT_TXT$::
Specifies the number of minutes for which the IP address of a timed out session is blocked.
::END
$CONNECTION_LS_ALLOW_XFORWARDED_FOR$=Allow X-Forwarded-For to change HTTP connection IP addresses
$CONNECTION_LS_ALLOW_XFORWARDED_FOR_TXT$::
When enabled, the "X-Forwarded-For" HTTP header parameter changes the IP address of the client for Serv-U. This is useful when all HTTP
connections are coming from a proxy server or load balancer. Proxy servers and load balancer typically append this parameter to the HTTP
header so that HTTP servers can identify the actual client IP address and apply security rules as needed.
::END
$CONNECTION_LS_REQUIRE_PTR$=Require reverse DNS name
$CONNECTION_LS_REQUIRE_PTR_TXT$::
Requires that users connecting to the server connect from an IP address that has a valid reverse DNS name, also known as a PTR record. Checks
for the existence of a valid PTR record but does not check its contents.
::END
$CONNECTION_LS_ALLOW_FTP_FTPS$=Allow FTP and FTPS Connections
$CONNECTION_LS_ALLOW_FTP_FTPS_TXT$::
Allows the user to connect using the FTP and FTPS protocols. Uncheck "Allow FTP and FTPS connections" to disable the FTP and FTPS protocols.
::END
$CONNECTION_LS_ALLOW_SFTP$=Allow SFTP Connections
$CONNECTION_LS_ALLOW_SFTP_TXT$::
Allows the user to connect using the SFTP protocol. Uncheck "Allow SFTP connections" to disable the SFTP protocol.
::END
$CONNECTION_LS_ALLOW_HTTP_HTTPS$=Allow HTTP and HTTPS Connections
$CONNECTION_LS_ALLOW_HTTP_HTTPS_TXT$::
Allows the user to connect using the HTTP and HTTPS protocols. Uncheck "Allow HTTP and HTTPS connections" to disable the HTTP and HTTPS protocols.
::END
$CONNECTION_LS_DOMAIN_SESSIONS$=Maximum number of sessions on domain
$CONNECTION_LS_DOMAIN_SESSIONS_TXT$::
Specifies the maximum number of concurrent sessions that may be allowed on the current Domain.
::END
$CONNECTION_LS_DOMAIN_IP_SESSIONS$=Maximum sessions per IP address on domain
$CONNECTION_LS_DOMAIN_IP_SESSIONS_TXT$::
Specifies the maximum number of concurrent sessions that may be opened to the current Domain from a single IP address.
::END
$CONNECTION_LS_GROUP_SESSIONS$=Maximum number of sessions for group
$CONNECTION_LS_GROUP_SESSIONS_TXT$::
Specifies the maximum number of concurrent sessions that may be allowed for all Users that are a member of the Group.
::END
$CONNECTION_LS_GROUP_IP_SESSIONS$=Maximum sessions per IP address for group
$CONNECTION_LS_GROUP_IP_SESSIONS_TXT$::
Specifies the maximum number of concurrent sessions that may be opened from a single IP address for all Users of the Group.
::END
$PASSWORD_LS_HEADER$=Password
$PASSWORD_LS_ANON_PASS$=Check anonymous passwords
$PASSWORD_LS_ANON_PASS_TXT$::
Specifies whether or not Serv-U should validate email addresses supplied as the password to login anonymously.
::END
$PASSWORD_LS_ENCRYPT_PASS$=Password Encryption Mode
$PASSWORD_LS_ENCRYPT_PASS_TXT$::
Specifies the level of password encryption on user passwords. The options are: "One-way encryption (more secure)"
which fully encrypts passwords and cannot be reversed, "Simple two-way encryption (less secure)" which encrypts
passwords in a reversible format for easy recovery, and "No encryption (not recommended)" which stores passwords in
clear text. When this setting is changed, existing passwords are not updated and must be re-saved to be stored in
the new format.
::END
$PASSWORD_LS_USER_PASS_RECOVERY$=Allow users to recover password
$PASSWORD_LS_USER_PASS_RECOVERY_TXT$::
If enabled, allows users to recover passwords using the Web Client password recovery utility at the login page.
::END
$PASSWORD_LS_MASK_PASS$=Mask received passwords in logs
$PASSWORD_LS_MASK_PASS_TXT$::
Masks the passwords received from clients from being shown in log files. Disabling this allows passwords to be displayed
in log files, which can be useful for debugging connection problems or auditing User account security.
::END
$PASSWORD_LS_MIN_PASS_LEN$=Minimum password length
$PASSWORD_LS_MIN_PASS_LEN_TXT$::
Specifies the minimum number of characters required in a User account's password. Specifying 0 characters indicates that there is no minimum requirement.
::END
$PASSWORD_LS_CHANGE_PASS$=Allow users to change password
$PASSWORD_LS_CHANGE_PASS_TXT$::
Specifies whether or not Users are allowed to change their own passwords.
::END
$PASSWORD_LS_EXPIRE_PASS$=Automatically expire passwords
$PASSWORD_LS_EXPIRE_PASS_TXT$::
Specifies the number of days a password is valid before it must be changed. Specifying 0 days means passwords never expire.
::END
$PASSWORD_LS_COMPLEX_PASS$=Require complex passwords
$PASSWORD_LS_COMPLEX_PASS_TXT$::
Specifies that all User account passwords must contain at least one uppercase and one non-alphabetic character to be considered valid.
::END
$PASSWORD_LS_SSH_AUTH_TYPE$=SSH authentication type
$PASSWORD_LS_SSH_AUTH_TYPE_TXT$::
Specifies how SSH authentication is to occur. Options include: "Password and Public Key" - requires both a password and a public key
(when specified) for login; "Password or Public Key" - requires either a password or public key for login; "Public Key Only" - requires
that a public key is provided for successful login, a password is not allowed; "Password Only" - requires that a password is provided
for successful login, a public key is not allowed.
::END
$DIRECTORY_LISTING_LS_HEADER$=Directory Listing
$DIR_LIST_HIDE_HIDDEN$=Hide files marked as hidden from listings
$DIR_LIST_HIDE_HIDDEN_TXT$::
Hides files and folders from directory listings that have the Windows "hidden" system attribute set on them.
::END
$DIR_LIST_LOCK_HOMEDIR$=Lock users in home directory
$DIR_LIST_LOCK_HOMEDIR_TXT$::
Locks Users into their home directory, and does not allow Users to browse above that folder. In addition, their home directory is displayed as "/" masking the
actual physical location.
::END
$DIR_LIST_USE_LOWER$=Use lowercase for file names and directories
$DIR_LIST_USE_LOWER_TXT$::
Forces Serv-U to display all file names and directories using lowercase characters, regardless of the actual letter case in use by the file or directory.
::END
$DIR_LIST_UNLOCK_ROOT$=Allow root ("/") to list drives for unlocked users
$DIR_LIST_UNLOCK_ROOT_TXT$::
Allows Users to change directory to the root ("/") of the system and display all drives on the computer. This option only works when the User is not locked
in their home directory.
::END
$DIR_LIST_TREAT_SHORTCUTS$=Treat Windows shortcuts as target in links
$DIR_LIST_TREAT_SHORTCUTS_TXT$::
Instructs Serv-U to treat all valid .lnk (shortcut) files as a UNIX symbolic link.
::END
$DIR_LIST_SHORTCUT_LINKS$=Interpret Windows shortcuts as links
$DIR_LIST_SHORTCUT_LINKS_TXT$::
Instructs Serv-U to treat all valid .lnk files as the actual destination object. In other words, if a .lnk file points to another file, the destination file
is shown in the directory listing instead of the .lnk file itself.
::END
$DATA_TRANSFER_LS_HEADER$=Data Transfer
$DATA_TRANSFER_DELETE_PARTIAL$=Delete partially uploaded files
$DATA_TRANSFER_DELETE_PARTIAL_TXT$::
Instructs Serv-U to delete incomplete file uploads. If this option is enabled, Users are not able to restart interrupted uploads using the REST (Restart)
FTP command.
::END
$DATA_TRANSFER_SERVER_MAX_DL$=Maximum download speed for server
$DATA_TRANSFER_SERVER_MAX_DL_TXT$::
Limits the maximum bandwidth that can be used Server-wide for all downloads. Setting a limit of 0 KB/s means unlimited bandwidth.
::END
$DATA_TRANSFER_SERVER_MAX_UL$=Maximum upload speed for server
$DATA_TRANSFER_SERVER_MAX_UL_TXT$::
Limits the maximum bandwidth that can be used Server-wide for all uploads. Setting a limit of 0 KB/s means unlimited bandwidth.
::END
$DATA_TRANSFER_MAX_SESSION_DL$=Maximum download speed per session
$DATA_TRANSFER_MAX_SESSION_DL_TXT$::
Limits the maximum download bandwidth for each individual session. Setting a limit of 0 KB/s means unlimited bandwidth.
::END
$DATA_TRANSFER_MAX_SESSION_UL$=Maximum upload speed per session
$DATA_TRANSFER_MAX_SESSION_UL_TXT$::
Limits the maximum upload bandwidth for each individual session. Setting a limit of 0 KB/s means unlimited bandwidth.
::END
$DATA_TRANSFER_MAX_USER_DL$=Maximum download speed for user accounts
$DATA_TRANSFER_MAX_USER_DL_TXT$::
Limits the maximum download bandwidth shared between all sessions associated with an individual User account. Setting a limit of 0 KB/s means unlimited bandwidth.
::END
$DATA_TRANSFER_MAX_USER_UL$=Maximum upload speed for user accounts
$DATA_TRANSFER_MAX_USER_UL_TXT$::
Limits the maximum upload bandwidth shared between all sessions associated with an individual User account. Setting a limit of 0 KB/s means unlimited bandwidth.
::END
$DATA_TRANSFER_MAX_UL_SIZE$=Maximum Upload File Size
$DATA_TRANSFER_MAX_UL_SIZE_TXT$::
Restricts the maximum single file size a user can upload to Serv-U. File size measured in kilobytes.
::END
$DATA_TRANSFER_INTERPRET_LINE_FEED$=Interpret line feed byte as a new line when in ASCII mode
$DATA_TRANSFER_INTERPRET_LINE_FEED_TXT$::
When uploading and downloading files using ASCII mode, Serv-U will assume <LF> characters are the same as <CR><LF>
end-of-line markers. Most Windows applications expect <CR><LF> to represent a new-line, as does the FTP protocol.
However, since the definition of a new-line sequence is not fully defined in Windows, this option allows Serv-U
to assume <LF> is the same as <CR><LF>. When uploading in ASCII mode stand-alone <LF> characters are changed to
<CR><LF> prior to writing to the file. When downloading in ASCII mode, stand-alone <LF> characters are changed to
<CR><LF> prior to sending to the client.
::END
$DATA_TRANSFER_DOMAIN_MAX_DL$=Maximum download speed for domain
$DATA_TRANSFER_DOMAIN_MAX_DL_TXT$::
Limits the maximum bandwidth that can be used Domain-wide for all downloads. Setting a limit of 0 KB/s means unlimited bandwidth.
::END
$DATA_TRANSFER_DOMAIN_MAX_UL$=Maximum upload speed for domain
$DATA_TRANSFER_DOMAIN_MAX_UL_TXT$::
Limits the maximum bandwidth that can be used Domain-wide for all uploads. Setting a limit of 0 KB/s means unlimited bandwidth.
::END
$DATA_TRANSFER_GROUP_MAX_DL$=Maximum download speed for all group members
$DATA_TRANSFER_GROUP_MAX_DL_TXT$::
Limits the maximum total bandwidth that can be used by all members of the Group for all downloads. Setting a limit of 0 KB/s means unlimited bandwidth.
::END
$DATA_TRANSFER_GROUP_MAX_UL$=Maximum upload speed for all group members
$DATA_TRANSFER_GROUP_MAX_UL_TXT$::
Limits the maximum total bandwidth that can be used by all members of the Group for all uploads. Setting a limit of 0 KB/s means unlimited bandwidth.
::END
$ADVANCED_LS_HEADER$=Advanced
$ADVANCED_CHECK_DIRSIZE$=Automatically check directory sizes during upload
$ADVANCED_CHECK_DIRSIZE_TXT$::
Instructs Serv-U to occasionally check the size of directories in which a maximum directory size has been specified. This attribute ensures that Serv-U always
has updated directory sizes available instead of having to calculate them at transfer time, which can be a time consuming operation.
::END
$ADVANCED_URL_CHARS$=Convert URL characters in commands to ASCII
$ADVANCED_URL_CHARS_TXT$::
Instructs Serv-U to convert special characters contained in command parameters to plain ASCII text. Certain Web browsers can encode special characters contained
in file names and directories when using the FTP protocol. This attribute allows Serv-U to decode these special characters.
::END
$ADVANCED_RENAME_OVERWRITE$=Warn end users when using old web browsers
$ADVANCED_RENAME_OVERWRITE_TXT$::
When enabled (default) Serv-U allows files to be renamed to files where the destination already exists. When disabled users are not allowed to rename a file or
directory to a path name that already exists.
::END
$ADVANCED_WARN_OLD_BROWSER$=Allow Rename Overwrite
$ADVANCED_WARN_OLD_BROWSER_TXT$::
When enabled (default) Serv-U will warn users that they are using an outdated browser and should upgrade the browser to take advantage of performance and feature enhancements to improve their experience.
::END
$ADVANCED_DISABLE_NAGLE$=Disable usage of Nagle algorithm
$ADVANCED_DISABLE_NAGLE_TXT$::
Disables waiting for the ACK TCP handshake before sending the next packet. This option is typically only used for connections with very large latencies, such
as satellite links.
::END
$ADVANCED_INLINE_OOB$=Inline out-of-band data
$ADVANCED_INLINE_OOB_TXT$::
Parse out-of-band socket data into the regular TCP data stream, treating it like normal data. This option is useful to counter denial-of-service attacks
that send large amounts of out-of-band (OOB) data to socket stacks that cannot handle large amounts of OOB data.
::END
$ADVANCED_SEND_KEEPALIVE$=Send keep alive packets to detect broken connections
$ADVANCED_SEND_KEEPALIVE_TXT$::
Periodically sends keep-alive packets to determine if the socket is still connected.
::END
$ADVANCED_ADAPTIVE_TIMEOUT$=Use adaptive time-out on fast file uploads
$ADVANCED_ADAPTIVE_TIMEOUT_TXT$::
Slowly lower packet time out for consistently fast transfers during file uploads. In case the transfer does not complete successfully, adaptive timeouts makes
it easier to resume the upload since Serv-U recognizes more quickly that the transfer is dead and thus allow access to the file sooner.
::END
$ADVANCED_MAX_SFTP_VER$=Maximum Supported SFTP Version
$ADVANCED_MAX_SFTP_VER_TXT$::
Specifies the maximum verison of SFTP permittted for SFTP connnections. Serv-U supports SFTP versions 3-6.
::END
$DOMAIN_SETTINGS_HEADER$=Settings
$DOMAIN_SETTINGS_BASICS$::
The Server Settings and Domain Settings tab allows you to configure basic Server or Domain settings that affect performance, security, and network
connectivity. To configure a setting, simply enter the desired value in the appropriate area and click the Save button. For more information
on the settings that can be configured, look below.
::END
$CONNECTION_SETTINGS_HEADER$=Connection Settings
$CONNECTION_SETTINGS_ANTIHAMMER$=Block users who connect more than 'x' times within 'y' seconds for 'z' minutes
$CONNECTION_SETTINGS_ANTIHAMMER_TXT$::
Also known as anti-hammering, enabling this option is a method of preventing brute force password guessing systems from using dictionary style attacks to
locate a valid password for a user account. Using strong, complex passwords defeats most dictionary attacks. However, enabling this option ensures that
Serv-U does not waste time processing connections from these illegitimate sources. When configuring this option, ensure that there is some room available for
legitimate users to correct an incorrect password before they are blocked.
When enabled, this option temporarily blocks IP addresses for 'z' minutes that fail to successfully login after 'x' attempts within 'y' seconds. IP addresses
blocked in this way can be viewed in the appropriate IP Access rules tab. A successful login resets the counter tracking attempted logins.
::END
$CONNECTION_SETTINGS_HIDE_SSH_SERVER_ID$=Hide server information from SSH identity
$CONNECTION_SETTINGS_HIDE_SSH_SERVER_ID_TXT$::
After a successful SSH login, the server sents identification information to the client. Normally, this information includes the server name and version
number. Enable this option to prevent the information from being given to the client.
::END
$CONNECTION_SETTINGS_DEFAULT_CLIENT$=Default Web Client
$CONNECTION_SETTINGS_DEFAULT_CLIENT_TXT$::
Specifies whether the Web Client or FTP Voyager JV should be used by all HTTP clients by default. A third option (the default option) is to prompt the
User for the client they want to use instead. This option is also available at the Group and User level.
::END
$SUPPORT_LINK_HEADER$=Client Support Link
$SUPPORT_LINK_BODY1$::
The Client Support Link is a powerful feature that allows a direct method of contact to be inserted into the Web Client and FTP Voyager JV in the event
that a client requires support or assistance. The basic syntax for this feature is protocol:path. This option is highly flexible and allows
for any network shortcut to be used, such as:
::END
$SUPPORT_LINK_LIST1$::
http://www.website.com/support/
mailto:service@website.com?subject=Serv-U File Server Support
aim:goim?screenname=ExampleAdminUser&message=I need help with your Serv-U File Server!
::END
$SUPPORT_LINK_BODY2$::
Any format can be used as long as the client's machine understands the provided protocol.
::END
$CUSTOM_LOGO_SETTINGS_HEADER$=Custom Logo Settings
$CUSTOM_LOGO_SETTINGS$=Specify a custom logo to be displayed on the login and Web Client pages.
$CUSTOM_LOGO_SETTINGS_TXT$::
Dimensions for custom logos must have a width of 400 pixels and a height of 100 pixels. If a logo does not meet this criteria an
error message will appear when you attempt to save the logo. Please note: JPEG images which use CMYK instead of RGB encoding may not work
properly on certain browsers. Please test your logo image to make sure it is displaying properly on all browsers.
To add a logo, simply click on the "Browse" button in the "Custom Logo" group box and select the
path to your logo. Click the "Save" button and the logo will appear below the "Custom Logo Path" input field. To erase a custom logo, clear the path in the
the "Custom Logo Path" input field and click the "Save" button.
::END
$PASSWORD_RECOVERY_EMAIL_HEADER$=Password Recovery Email Message
$PASSWORD_RECOVERY_EMAIL$=Send email messages to users with their login credentials using this customizable password recovery message.
$PASSWORD_RECOVERY_EMAIL_TXT$::
The password recovery email message has a simple default subject and message with the user's login ID and password. This message will be sent if the user
has a valid email address recorded in Serv-U. Users may request this message from the Serv-U login page.
Administrators may also send this message to users using the "Recover Password" button under domain users and global users in the Management Console.
::END
$INTEGRATION_DLL_HEADER$=Integration DLL
$INTEGRATION_DLL_TXT$::
For information about writing a Integration DLL, please see the Serv-U Integration Sample DLL installed with Serv-U in the sub-directory entitled "Serv-U
Integration Sample DLL". The Integration API is documented in this sample.
::END
$ADVANCED_SETTINGS_HEADER$=Advanced Settings
$ADVANCED_SETTINGS_DIRMASK$=Directory Listing Mask
$ADVANCED_SETTINGS_DIRMASK_TXT$::
Specifies the text string sent to FTP clients for file permissions. Windows does not support traditional file permissions like Unix making this option largely
cosmetic, however some clients require a certain mask to operate correctly.
::END
$ADVANCED_SETTINGS_MAX_THUMB$=Maximum Simultaneous Thumbnails
$ADVANCED_SETTINGS_MAX_THUMB_TXT$::
Specifies the maximum number of threads that are dedicated towards generating thumbnail images for HTTP clients and in response to the FTP THUMB command.
Generating thumbnails is a CPU intensive operation. Increasing this value too high may cause thumbnails to take longer to generate, even while Serv-U is
able to handle more client thumbnail requests concurrently.
::END
$ADVANCED_SETTINGS_UPLOAD_ACCESS$=File Upload Access
$ADVANCED_SETTINGS_UPLOAD_ACCESS_TXT$::
Specifies the method in which uploaded files are opened while they are being received from a client. The default Allow read access means
that other clients may attempt to download the file even while it's still being received. Allow full access means other clients can read from
and write to the file while it's being transferred. To prevent any other client from accessing a file while it's still being transferred, select Allow
no access.
::END
$ADVANCED_SETTINGS_DOWNLOAD_ACCESS$=File Download Access
$ADVANCED_SETTINGS_DOWNLOAD_ACCESS_TXT$::
Specifies the method in which downloaded files are opened while they are being sent to a client. The default Allow read access means
that other clients may also attempt to concurrently download the same file. Allow full access means other clients can read from and write to
the file while it's being sent to another client. To prevent any other client from accessing a file while it's still being sent, select Allow no
access.
::END
$NETWORK_SETTINGS_HEADER$=Network Settings
$NETWORK_SETTINGS_UPNP$=Auto-configure firewall through UPnP
$NETWORK_SETTINGS_UPNP_TXT$::
When enabled, Serv-U automatically configures the necessary port forwards in your UPnP-enabled network device (usually a router) so that the File
Server is accessible from outside your network. This is particularly useful in enabling PASV mode FTP data transfers.
::END
$NETWORK_SETTINGS_PACKET_TO$=Packet Time-Out
$NETWORK_SETTINGS_PACKET_TO_TXT$::
Specifies the timeout, in seconds, for a TCP packet transfer. Only very slow networks experiencing high levels of latency may need to change this
value from the default 300 seconds.
::END
$NETWORK_SETTINGS_PASV$=PASV Port Range
$NETWORK_SETTINGS_PASV_TXT$::
Specifies the inclusive range of ports that Serv-U should use for PASV mode data transfers. Serv-U normally allows the operating system to assign it
a random port number when opening a socket for a PASV mode data transfer. This attribute accommodates routers or firewalls that need to know a
specific range of ports in advance by restricting Serv-U's PASV port range to a known range. A range of 10 ports is sufficient for the busiest of
File Servers.
NOTE: Some NAT routers work differently and may require a larger port range. If Serv-U and clients have troubles listing directories
or transferring files, try increasing the port range here and on your router.
::END
$OTHER_SETTINGS_HEADER$=Other Settings
$OTHER_SETTINGS_RATIO_FREE$=Ratio Free Files
$OTHER_SETTINGS_RATIO_FREE_TXT$::
Files listed by opening the Ratio Free Files button are exempt from Transfer Ratio limitations on file transfers. Ratio free files
specified at the Server or Domain level are inherited by all their Users accounts. For more information, see the Help section on $LINK_HELP_RATIOS$.
::END
$OTHER_SETTINGS_ADMIN_PASS$=Change Admin Password
$OTHER_SETTINGS_ADMIN_PASS_TXT$::
The Serv-U Management Console can be password protected when it is launched by double-clicking on the Serv-U system tray icon. When the Management
Console is running in this way, the option to change the password becomes available. By default, there is no admin password.
::END
$CUSTOM_FTP_HEADER$=FTP Settings
$CUSTOM_FTP_COMMANDS_BODY1$::
The Serv-U File Server allows for the customization of the FTP commands that it accepts as well as its responses to FTP commands received. When
configuring these options at the Server level, all Domains inherit these customizations. To customize the FTP behavior for a specific Domain,
select the appropriate Domain, open the FTP Settings tab for the Domain, and click the Use Custom Settings button.
At any time, the Use Default Settings button can be clicked to have the Domain revert back to the Server's default settings.
Customizing the FTP behavior in this way is not recommended except for those very familiar with the FTP protocol and its standard and extended command
set.
::END
$CUSTOM_FTP_GLOBAL_PROPS$=Global Properties
$CUSTOM_FTP_GLOBAL_PROPS_TXT$::
When using custom settings, the Global Properties button becomes available.
::END
$CUSTOM_FTP_GLOBAL_RESP$=Global FTP Responses
$CUSTOM_FTP_GLOBAL_RESP_TXT$::
Global FTP responses are responses shared amongst most FTP commands, such as the error message sent when a file isn't found. Customizing a global FTP
response ensures that the response is used by all other FTP commands rather than having to customize it for each individual FTP command. FTP command
responses can contain special macros that allow real-time data to be inserted in to the response. See the Help section on $LINK_HELP_SYSTEM_VARS$
for more information.
::END
$CUSTOM_FTP_SERVER_MSG$=Server Welcome Message
$CUSTOM_FTP_SERVER_MSG_TXT$::
The Server welcome message is sent in addition to the standard "220 Welcome Message" that identifies the Server to clients when they first connect.
If the Include response code in text of message file box is checked, then the 220 response code begins each line of the specified
welcome message. To customize the welcome message, enter the path to a text file in Message File Path input box. Use the Browse
button to select a file on the computer. Serv-U opens this file and send its contents to connecting clients.
::END
$CUSTOM_FTP_ADVANCED$=Advanced Options
$CUSTOM_FTP_GLOBAL_ADVANCED_TXT$::
Block "FTP_bounce" attacks and FXP (server-to-server transfers) - Checking this box blocks all server-to-server file transfers
involving this Serv-U File Server by only allowing file transfers to the IP address in use by the command channel. For more information on
"FTP_bounce" attacks, see <a href="http://www.cert.org/advisories/CA-1997-27.html" target="_blank">CERT advisory CA-97.27</a>.
Include response code on all lines of multi-line responses - The FTP protocol defines two ways in which a multi-line response can be
issued by an FTP server. Some older FTP clients have trouble parsing multi-line responses that don't contain the 3-digit response code on each line.
Check this box if your clients are using an FTP client experiencing problems with multi-line responses from Serv-U.
Use UTF-8 encoding for all sent and received paths and file names - By default, Serv-U treats all file names and paths as UTF-8 encoded strings. It
also sends all file names and paths as UTF-8 encoded strings, such as when sending a directory listing. Unchecking this option prevents Serv-U from UTF-8
encoding these strings. When this option is unchecked, UTF8 is not included in the the FEAT command response to indicate to clients that the server is not
using UTF-8 encoding.
::END
$CUSTOM_FTP_EDIT$=Editing FTP Commands & Responses
$CUSTOM_FTP_EDIT_TXT$::
To edit FTP Commands, select the FTP command to edit and click the Edit button.
::END
$CUSTOM_FTP_INFO$=Information
$CUSTOM_FTP_INFO_TXT$::
Under the Information tab, basic information about the command is shown along with a link to more information on our website. Each
FTP command can also be disabled by checking the Disable command checkbox. Disabled commands are treated as unrecognized commands
when they are received from a client.
::END
$CUSTOM_FTP_RESPONSES$=FTP Responses
$CUSTOM_FTP_RESPONSES_TXT$::
Under the FTP Responses tab, all possible FTP responses to the command as issued by the Server can be modified by clicking on the
Edit button for each response. FTP command responses can contain special macros that allow real-time data to be inserted in to the
response. See the Help section on $LINK_HELP_SYSTEM_VARS$ for more information.
::END
$CUSTOM_FTP_MSGFILE$=Message Files
$CUSTOM_FTP_MSGFILE_TXT$::
Certain FTP commands allow a message file to be associated with them. The contents of a message file are sent along with the standard FTP response. In
addition, a secondary message file path is available as a default option. This allows for message files to be specified using a path relative to the
User's home directory for the Message File. If the first message file isn't found, then Serv-U attempts to use the Secondary
Message File instead. By specifying an absolute file path in the secondary location, you can ensure that each User receives a message file.
The following is a list of all FTP commands that allow specifying a message file:
::END
$CUSTOM_FTP_MSGFILE_LIST$::
CDUP
CWD
QUIT
::END
$CUSTOM_FTP_COMMAND_ADVANCED_TXT$::
Some FTP commands contain advanced configuration options that offer additional ways to configure the behavior of the command. Where available, the
configuration option is described in detail in the Management Console. The following is a list of FTP commands containing advanced configuration
options:
::END
$CUSTOM_FTP_ADV_COMMAND_LIST$::
LIST
MDTM
NLST
::END
$FTP_RESP_CASEFILE1_HEADER1$=Case File - Custom FTP Command Response
$FTP_RESP_CASEFILE1_BODY1$::
Users connecting to the server need to know how much quota space is available in a given folder when they have completed a transfer. To do this, edit
the response to the STOR command to include a report on available space. By default, the 226 (command successful) response to the STOR command (which
stores files on the server) is:
"Transfer complete. $TransferBytes bytes transferred. $TransferKBPerSecond KB/sec."
Modify this to include an extra variable:
"Transfer complete. $TransferBytes bytes transferred. $TransferKBPerSecond KB/sec. Remaining storage space is $QuotaLeft."
The last sentence shows the user how much storage space is left at the end of each file upload. The same can be done for the DELE command, so that
every time a user deletes a file, their updated quota value, showing an increase in available space, is displayed. This can be done for any FTP command
response.
::END
$ENCYRPTION_HEADER$=Encryption
$ENCRYPTION_BODY$::
Serv-U supports two methods of encrypted data transfer - Secure Socket Layer (SSL) and Secure Shell 2 (SSH2). SSL is used to secure the File Transfer
Protocol (FTP) and Hypertext Transfer Protocol (HTTP). SSH2 is a method of securely interacting with a remote system that supports a method of file
transfer commonly referred to as SFTP. Despite its name, SFTP does not have anything in common with the FTP protocol itself.
In order for each method of encryption to work, a certificate and/or private key must be supplied. SSL requires the presence of both, while SSH2 only
requires a private key. If you do not possess either of these required files, Serv-U can create them for you.
Encryption options specified at the Server level are automatically inherited by all Domains. Any encryption options specified at the Domain level
automatically overrides the corresponding Server-level option. Certain configuration options are only available to the Server.
::END
$SSL_SETUP_HEADER$=Configuring SSL for FTPS and HTTPS
$SSL_SETUP_NOTE$::
When creating SSL/TLS, SSH, and HTTPS encrypted Domains within Serv-U, it is important to know that encrypted Domains cannot share listeners. Because
SSL/TLS and SSH encryption is based on encrypting traffic sent between IP addresses, each Domain must have unique listeners in order to operate
properly. In the case that multiple encrypted Domains are created that share listeners, the Domain created first takes precedence causing other
encrypted Domains to fail to function properly. To operate multiple encrypted Domains, modify the listeners of each Domain to ensure they listen on
unique port numbers.
::END
$SSL_SETUP_EXISTING$=Using An Existing Certificate
$SSL_SETUP_EXISTING_LIST$::
Obtain an SSL certificate and private key file from a certificate authority.
Place these files in a secured directory in the server.
Use the appropriate Browse button to select both the certificate and private key files.
If a CA (Certificate Authority) PEM file has been issued, enter or browse to the the file.
Enter the password used to encrypt the private key file.
Click the Save button.
::END
$SSL_SETUP_EXISTING_TXT$::
If the provided file paths and password are all correct, Serv-U begins using the certificate immediately to secure FTPS and HTTPS connections
using the provided certificate. If the password is incorrect or Serv-U cannot find either of the provided files, an error message is displayed
that explains the encountered error.
::END
$SSL_CREATE_CERT$=Creating A New Certificate
$SSL_CREATE_CERT_LIST$::
Click the Create Certificate button to get started.
Specify the Certificate Set Name that is used to name each of the files Serv-U creates.
Specify the output path where the created files are to be placed. In most cases, the installation directory is a safe location (i.e, C:Program FilesRhinoSoft.comServ-U).
Specify the city/town in which the server or corporation is located.