PeerSync can utilize up to three protocols during the synchronization process. The three features that utilize the protocols are standard PeerSync network operations (SMB), ftp synchronization (FTP), and TCP/ByteReplicator activity (proprietary protocol).
- SMB (CIFS Protocol): When synchronizing between network shares, PeerSync will use the SMB (CIFS) protocol for communication. In addition, PeerSync will rely on the protocols compression, encryption, and security credential systems as well. This applies to Windows to Windows relationships, as well as Windows to non-Windows shares. Generally the SMB ports used are in the range 136-139.
- FTP Protocol: When synchronizing to and from an FTP location, the FTP protocol will be utilized to provide authentication, command execution, and data transfer. Generally, the port FTP will utilize is 21, as well as a number of random non-standardized ports.
- TCP and ByteReplicator Protocol: When synchronizing between shares, the ByteReplicator protocol can be used in conjunction with the SMB (CIFS) protocol in order to provide smart data transfer (byte-level transfer). This proprietary TCP protocol is by default operating on port 7333, but can be modified to use any port.
When synchronizing to or from a TCP location, the TCP protocol will be use to provide encryption, compression, data transfer, and general communication between PeerSync and the Listener. This proprietary TCP protocol is by default operating on port 7333, but can be modified to use any port.
- Can I use DFS Namespaces when specifying folder paths in PeerSync?
- Configure PeerSync Listener's advanced settings
- Does PeerSync Listener have to be installed on both servers when using the ByteReplicator?
- How does the ByteReplicator work?
- PeerSync Security Port Usage
- Set up synchronization/replication over TCP
- What is the disk space requirement for PeerSync?
- Why does ByteReplicator use .BRTMP temporary files?