Configure the database connection of Serv-U

Earlier versions of Serv-U (such as versions earlier than 4.1) rely on plug-ins to connect to databases. The latest version 5.0.0.9 provides support for ODBC databases, the configuration process of the Access database is as follows:

1. Create a database file. Assume It is ServU. Create a table in the database. Assume the name is user and four columns are created in the Table. Assume the names are username, password, accessrule, and homedir respectively.

2. Create an ODBC Data Source. Suppose you have created a system DSN named test.

3. Create a new "new domain" in ServU, create it according to the wizard, and select "store in ODBC database" in the last step"

4. Click the newly created domain name in the tree control on the left of ServU, select the "ODBC" tab on the right, and fill in the fields as needed.Note: there is a small problem in the 5.0.0.9 online document. It indicates that at least one table-User Account table is required. This table requires at least three columns: User Name, user password, and home directory. however, in practice, a column is also required: directory/IP access rules.According to the above process, the corresponding input here:

ODBC source name: Test

Table Name of user: User

Column name of Account name: Username

Column name of password: Password

Column name of DIR/IP access rule: Access

Column name of Home Directory: homedir

The above are the minimum Database Configuration Requirements for ServU. Click the application button after the configuration is complete.

Test: Open the database directly, add a user testuser to the table user, and then use the FTP client software to log on as the testuser user (Note: ServU uses MD5 to encrypt the password, if the plain text cannot be entered directly in the password field of the database table, it is best to use ServU to create a user and then copy the value of the password column in the table to testuser)

If the newly created domain cannot be started, you can view the task log in server-> activity-> session log.