Applies to: Syncplify.me Server! Version(s): 4.x - 5.x
If you run Syncplify.me Server! hosted on a VM in the cloud or at some co-location provider, you are probably aware that your ISP uses traffic shapers to optimize the transfer speed and to prevent malicious users from abusing network resources.
In some cases, though, such strategy (packet/traffic shaping) clashes against the very nature of the SSH/SFTP protocol, in which both control and data packets are sent on the same connection. In particular, you may experience issues between the requested SSH socket buffer and the advertised buffer size on the network. If that happens, we got you covered! As of version 4.0, in fact, you can use a special Registry key to force Syncplify.me Server! to use a socket buffer size that matches the one advertised by your network.
Create a SSHSockBuf value (of type DWORD) under the HKLM\SOFTWARE\Syncplify.me\ServerV4\VirtualServers\your_vserver_name
(use "ServerV5" instead of "ServerV4" if you're running Syncplify.me Server! v5.x)
You don’t even need to restart your Syncplify.me Server! after doing this. At the next client connection, your server will automatically apply the new socket buffer.