Before installing WS_FTP Server Web Transfer Module, you need the following:
To install Microsoft .NET 3.0, you need to have Windows® Server 2003 Service Pack 1 or later, Windows XP Professional Service Pack 2 or later, or Windows Server 2008.
The pre-installation checklist in the section, "Installing WS_FTP Server Web Transfer Module," describes how to configure the requirements.
The end user can use any computer with an operating system that can support the following:
The WS_FTP installer automatically activates certain components in your Windows 2008 installation (in addition to the ones activated by a normal Server install). Before installing WS_FTP Server, you should be sure that these changes conform to your organization's security policies.
The following list shows features activated by the WS_FTP Server Web Transfer Module install under the IIS7 role. Features shown as indented indicate a nested relationship with the non-indented feature above it.
Common HTTP Features
Application Development
Health and Diagnostics
Security
Performance
Management Tools
The following list shows the 2008 stand-alone features activated during WS_FTP Server install:
.Net Framework 3.0 Features
Remote Server Administration Tools
Windows Process Activation Service
Additionally, the Web Transfer Module install process does the following:
Also, if HTTPS is not enabled on the site hosting the Web Transfer Module, the install will:
If you choose to install WS_FTP Server Web Transfer Module, it should be installed on the same computer as WS_FTP Server. This section provides a pre-installation checklist and install procedure for installing WS_FTP Server Web Transfer Module.
WS_FTP Server Web Transfer Module installs an IIS web application to communicate with the WS_FTP Server database and FTP file system. Before you run the WS_FTP Server Web Transfer Module installation, you need to install the prerequisite software and configure the WS_FTP Server computer.
For the installation requirements and procedure, see the section "Installing and Configuring WS_FTP Server, or refer to the WS_FTP Server Release Notes.
You can download and install .NET Framework 3.0 from the Microsoft Download Center.
You need the Windows OS disk to install IIS. Go to Control Panel > Add or Remove Programs, then select Add/Remove Windows Components. Select Internet Information Services (or Application Services on Windows 2003), then follow the on-screen instructions.
Note that this Windows user account is used differently depending on the WS_FTP Server host settings and the user database configured for that host:
To install WS_FTP Server Web Transfer Module:
Example: D:\launch.exe
- OR -
If you downloaded the software from our Web site, double-click the executable (.exe) file to begin the installation.
Next, the Impersonation Account for Web Transfer Module screen opens.
The Web Transfer Module needs a Windows account to use for access to the FTP file system.
On the WS_FTP Server computer, you should have created a Windows account that has full access to the top directory of the WS_FTP Server host, as described in the pre-installation steps. Use that account username and password here.
Domain or Server. Enter either the valid Windows domain name of the WS_FTP Server computer, or the Windows computer name.
User name. Enter the applicable user name for the Windows account.
Password. Enter the password for the account.
This account username and password will also appear in the WS_FTP Server Manager, under Home > Modules > Web Access Settings. If necessary, you can modify this account after completing the installation.
The installation program also configures the Web Transfer web application to accept SSL connections on port 443. A self-signed certificate is installed. This allows your users to use HTTPS for secure transfers.
Next, the Destination Folder dialog opens.
If you want to install to a different folder, click Change, then browse to the destination folder, or create a new folder, then click OK. You will be returned to the Destination Folder dialog. Click Next.
You need to enable web access for users that will use the Web Transfer Client, and provide them the web address to log on, as described in the section, "Configuring WS_FTP Server Web Transfer Module."
If you purchased the WS_FTP Server Web Transfer Module as an add-on module to WS_FTP Server 7.5, WS_FTP Server 7.5 with SSH, and WS_FTP Server 7.5 Corporate, you need to refresh your WS_FTP Server 7.5, WS_FTP Server 7.5 with SSH, and WS_FTP Server 7.5 Corporate license. To refresh, from the Start menu, select Program Files > Ipswitch WS_FTP Server > Activate or Refresh WS_FTP Server License. If you purchased a WS_FTP Server Corporate license, you do not to refresh your license.
WS_FTP Server Web Transfer Module does not require installation on a user's computer. Your WS_FTP Server users can access the files in their accounts using any browser, and the address (URL) that you provide them.
However, you must administer the following changes in WS_FTP Server 7.5, WS_FTP Server 7.5 with SSH, and WS_FTP Server 7.5 Corporate Manager:
The Web Access page shows all eligible users, which is all users on all of your WS_FTP Server hosts.
The address is: http://<local_machine>/thinclient/
where <local_machine> is the domain name of the computer on which you installed the Web Transfer Client. If you specified a custom port (other than the default port 80) during installation, you need to enter it in the address.
For example, if the local computer domain name is host1.wsftp.com, then the address your users need to log on to the Web Transfer Client is:
http://host1.wsftp.com/thinclient/
You should test this address before sending it out to users.
You can also launch the Web Transfer Client from the WS_FTP Server program group (Programs > Ipswitch WS_FTP Server > WS_FTP Server Web Transfer Client.)
If you add a user to the default host (specified in Server > Server Settings > System Details), the user will log onto the Web Transfer Client using their WS_FTP server user name and password. If you add a user to a host that is not the default host, the user must log onto the Web Transfer Client using the host name, host separator, and username and password; for example: user2@host2.domain.com
For secure transfer, the Web Transfer Client is installed with SSL capability, which runs on port 443. The installation creates an SSL certificate which is used when the user connects via HTTPS. You can enable secure transfer by changing the address used to log on to the Web Transfer Client to use HTTPS, for example: https://host1.wsftp.com/thinclient/login.aspx
If you specified a custom port (other than the default port 443) during installation, you need to enter it in the address.
If your server is running IIS 7.0, users may not be able to upload file larger than 30 megabytes, receiving the following error:
HTTP Error 404.13 - CONTENT_LENGTH_TOO_LARGE
To correct this problem:
For example, modify the following:
<requestLimits maxAllowedContentLength ="
30000000"
/>
to increase the value to 1073741824, which equals 1 GB:
<requestLimits maxAllowedContentLength ="1000000000" />
If the upload exceeds the IIS maximum upload size, the browser displays a page error and does not return to the Web Transfer Client page.
Though we cannot change the browser behavior, both of these upload values can be set in the web.config file (C:\Program Files\Ipswitch\WebClients\ThinClient\Web.config).
When you save changes to the Web.config file, all active WS_FTP Server Web Transfer Client sessions will be reset, which means that any user logged on via the Web Transfer Client will be returned to the Logon page, and will have to log on again.
<add key="MaxUploadSize" value="50"/>
The value is in MB, so the maximum upload size for the Web Transfer Client is 50 MB.
<httpRuntime maxRequestLength="2097151"/>
The value is in KB, so the maximum upload size is 2 GB.
The IIS limit can also be set in other locations, namely machine.config, and IIS metabase, though we recommend using the web.config settings.
http://my_domain/thinclient/