GoodSync Connect uses the GoodSync Transfer Protocol (GSTP) to establish a connection between a GoodSync client and a GoodSync server. The client is the device running the GoodSync Job, while the server is the remote device providing access to the selected files and folders.
Direct Connection
GoodSync first attempts to create a direct peer-to-peer connection between the client and server over TCP/IP. When successful, file data moves directly between the two devices without passing through an intermediate transfer server.
A direct connection normally provides the best available transfer speed and lowest latency because the source and destination communicate directly.
Forwarded Connection
In some network environments, the client may not be able to connect directly to the server. Common causes include:
- Network Address Translation (NAT).
- Firewall or router restrictions.
- VPN or proxy configurations.
- Endpoint-security software blocking the connection.
- Restrictions on inbound network connections.
When a direct connection cannot be established, GoodSync automatically attempts to use a GoodSync Forwarder. The Forwarder provides a network path that both the client and server can reach and relays the encrypted GoodSync Connect traffic between them.
A forwarded connection may be slower than a direct connection because the traffic must travel through an additional network location.
No user action is normally required. GoodSync automatically determines whether a direct connection is available and uses a Forwarder only when the devices cannot communicate directly.
The Forwarder does not store the files being transferred. It only relays the encrypted connection between the GoodSync client and server. GoodSync Connect is not a cloud-storage service, and transferred files remain on the source and destination storage locations selected in the GoodSync Job.