WS_FTP Server Web Transfer Client does not require installation on a user's computer. Your WS_FTP Server users can access the files in their accounts using the web browser of their choice, and the address (URL) that you provide them.
However, you must administer the following changes in WS_FTP Server 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 port other than 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:
You should test this address from a remote machine 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: email@example.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" />
See also Configuring Support for Single Sign On.