New online and offline license activation method

Syncplify.me Server! v3.1.5.45 has introduced (per our customers’ request) a brand new online/offline license activation method that greatly simplifies the purchase process.

You don’t have to deal with the “System ID” anymore, in fact the Instance Controller now features a brand new “I have a License Code” button that you can push to activate the short and human-friendly license code you bought online. Note: the old “I have a License File” method is still supported for backward compatibility, but it is actually used only for offline activation of Enterprise licenses.

liccode

Continue reading

Project codename: Foundation

More frequently than expected we receive questions from our users relative to the “codenames” of the various editions of our Syncplify.me Server! software. Since now our version 3 is solid enough to allow us to fully focus on version 4 development, we think this is a good time to answer that question, and give our readers few more details regarding what to expect in the upcoming new major version. Continue reading

Linux sftp client error 6: invalid packet (solution)

Some users of Syncplify.me Server! have reported that when trying to connect to Syncplify.me Server! using the command-line sftp client from certain (but not all) Linux versions they are suddenly disconnected with the error message shown in the picture here below:

linuxbefore

The error code 6 (invalid packet) signifies that the Linux sftp client was not able to negotiate a secure session with the server due to the (client) inability to verify the contents of the KEX packet coming from the server.

Continue reading

Syncplify.me Server! scripting: Session.Terminate and Blacklist

In a previous article we’ve been talking about the new properties and methods introduced by Syncplify.me Server! v3 to improve the session object. One of such methods is Session.Terminate that basically instructs the FTP(S) or SFTP server to forcefully terminate the session as soon as the script execution ends.

In such post we have mentioned the addition of another useful function, often used in conjunction with Session.Terminate: the Blacklist function (which name is pretty self-explanatory). In this article we will explain how to use it.

First of all, let’s see the functions definition:

There are 3 parameters:

  1. IPorNetwork: the first parameter clearly should be the specific IP address (e.g.: 192.168.172.25) or the network/subnet (e.g.: 192.168.172.0/255.255.255.0) that you want to blacklist
  2. AMinutes: this is pretty intuitive too, it is the number of minutes you want the above IP address or network to be blacklisted for (unless you are permanently blacklisting it, see point #3 here below)
  3. AType: this parameter can be either ttTemporary or ttPermanent. If you want to temporarily blacklist the IP/network you will use ttTemporary and the IP/network will stay in the blacklist only for AMinutes minutes. Instead if you use ttPermanent the IP/network will be blacklisted forever (unless manually removed) and the AMinutes parameter will be ignored.

Continue reading

Syncplify.me Server!: No worries about POODLE SSLv3 bug.

By now, everyone has heard about the POODLE bug, that’s scaring every system administrator these days.

Unfortunately it is a design flaw in SSLv3, therefore the only thing you can do to go around it is to disable SSLv3 from all your servers (whatever they are, IIS, Apache, …, all SSL-capable servers).

Fortunately Syncplify.me Server! has – by design – a very easy way to do that. As shown in the picture below, just make sure the SSLv3 option is unchecked, and save your configuration. There you go, you’re safe now.

poodle

True impersonation and [USER_HOME] directory

One of the main new features that come with Syncplify.me Server! v3.0 is true impersonation of Windows and Active Directory users.

Unlike previous versions, the new v3.0 actually impersonates the authenticated Windows or AD user and therefore accesses the underlying file system with such user’s privileges, limitations, and ACL. Syncplify.me Server!’s native file and directory permissions still apply, but they are applied only *after* the operating system rules, therefore they can further restrict the OS configuration, but not expand it (for safety reasons). Continue reading

How-to: configure Syncplify.me Server! HA instances

Note: this article refers to Syncplify.me Server! v3.x; As of Syncplify.me Server! v4.0 support for high-availability (HA) has become even better; you can read more about v4.0 HA features here.

One of the main new features in Syncplify.me Server! v3.0 is the ability to run in high availability (HA) configurations.

A highly available configuration is a deployment in which 2 or more servers share the same storage and configuration/user database. A network balancer is then used to decide whether to operate such servers in an active/active mode (where all nodes accept incoming client connections simultaneously) or in an active/passive mode (where some nodes accept client connections, and some other nodes kick in to substitute one of the active nodes that has stopped working).

This article explains how to configure Syncplify.me Server! (with HA licenses) in order to operate in a highly available configuration. Please, read on… Continue reading

How-to: terminate a client session (or all of them)

As of version 3.0, Syncplify.me Server! allows you to forcefully terminate an unwanted client session, or even terminate all active sessions if needed.

You can do so by running the Configuration Manager, switching to the real-time monitor panel, and right-click with your mouse on the session you wish to terminate. A popup menu will appear and let you choose whether you want to end the selected session, or all the currently active sessions.

terminating

Syncplify.me Server! v3.0: free upgrade for existing customers

All existing customers who paid for Syncplify.me Server! v1.x or v2.x are entitled to a free upgrade to the “equivalent higher” edition of version 3.0.

What is the equivalent “higher edition”? For example, if you bought a v2.x “Professional” (used to be $179) you will now be upgraded to v3.0 “Pro One” ($219 MSRP) at no cost. And if you bought a v2.x “Professional Plus” (used to be $279) you will not be upgraded to the v3.0 “Pro Multi” ($349 MSRP) at no cost. And so on…

How to receive your free upgrade to v3.0? In the next 48 hours all customers will receive an email with the instructions. But, in case you don’t receive it (spam filters aren’t always friendly) you can simply contact us and request your free upgrade to v3.0.

If you contact us directly, please, remember to include your order number or license code, so we can identify you and provide you with the correct v3.0 upgrade license. Thank you!

How many concurrent file transfer from the same client?

Sometimes our users ask us how many concurrent file transfers can be initiated simultaneously by one client. The answer deserves a little bit of explanation.

First of all it is important to understand that this article is entirely focused on how to optimize the client side, in fact the server uses I/O completion ports and RTL critical sections to optimize concurrency under heavy load (hundreds or thousands of incoming client connections) and is therefore self-optimized.

The client side, instead, is very different. First of all the client has a GUI (graphical user interface) that needs to be synchronized with the “desktop” of the operating system. Furthermore, on the client side, the concept of “CPU core affinity” becomes very relevant. What is it? Let’s try to provide a simplified explanation… Continue reading