From reading the documentation on C:D, I believed that you must have C:D on both machines taking place in a file copy. However, of course after playing with using File Agent to watch a \\serverA\share network path and copying to another \\serverB\share network path, this seems to work. Which leaves me to believe you could have one central C:D server moving files between other servers.
My question if you did such a thing, would you then be losing any concept of secure connections since you no longer have two nodes handshaking, and instead just one server initiating copies?
Pinned topic Possible security issue with a centralized Connect:Direct server?
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2013-03-15T09:40:09Z at 2013-03-15T09:40:09Z by VolkerFriedrich
VolkerFriedrich 27000468T6196 Posts
Re: Possible security issue with a centralized Connect:Direct server?2013-03-15T09:40:09ZThis is the accepted answer. This is the accepted answer.While Connect:Direct can access files that reside on network shares, it is just plain file I/O over CIFS/SMB.
The connection between Connect:Direct and the sharing file server is not using the Connect:Direct protocol. Connect:Direct can only secure connections between two Connect:Direct nodes.
Having Connect:Direct installed on serverA and serverB allows you take full advantage of Connect:Direct and secure connections.
Having a single central Connect:Direct instance moving files from one network share to another is pretty overkill and would not add any real benefits. xcopy or robocopy could do the same job.