If you are looking for a tool that provides secure file transfer or a wide range of remote access services, VShell packs all the necessary features for dealing with such tasks.
It packs a clean and user-friendly interface that can help you access network resources and transfer data pretty quickly. VShell offers users the possibility to assign root directory access points to different users.
It is possible to automatically disconnect the file transfer sessions, provided that you have specified the time period, and you may also input the number of connections per user. The application includes a dedicated window that monitors the file transfer process, and gives information about the username, login time, IP, protocol, and sent or received bytes.
VShell also offers SSH2 support, which ensures that your data is securely transferred, and it is also able to encrypt the data by selecting from a wide range of ciphers, such as 3DES, Twofish, Blowfish, AES-128, AES-192, and AES-256.
The program can track failed authentications by IPs, and you can block the access of that address for future connections. It features dedicated filters that can help you select which hosts can connect by IP, hostname, or netmask.
VShell can generate logs that contain information about errors, warnings, connections, authentications, SFTS, and others. The log is automatically saved to the output destination.
It is also possible to configure the authentication process by limiting the number of failed attempts to a specified number, and by selecting the required authentication methods.
To sum up, VShell proves to be a decent solution for all users who need to securely transfer data and access network resources.

Limitations:
· 30 days evaluation period
· Nag screen

What's New in This Release:
Changes:
· VShell now logs the number of connections that are currently open to the server.
Bug fixes:
· Under certain high load circumstances, VShell could have stopped accepting new connections for a short period of time.
· On certain platforms, connections that used public-key authentication and loaded the user's profile may have caused the Windows LSASS process to leak memory.
· VShell may have crashed if an unknown packet type was received.
· VShell FTPS could have crashed while processing an incoming data connection.
· VShell may have failed to upload files or create new folders if the destination folder had the Owner Rights security principal specified in the access control list.
· The VShell Control Panel license evaluation dialog was not automatically dismissed after valid license information was entered.