Why does my process not receive events on mapped network drives?

CBFS Filter can intercept requests that either originate on the local computer (i.e. the system CBFS Filter works on) or come to this system for processing. It cannot monitor events that are initiated and processed remotely.

Example 1:

You have a server S that shares disk ServerDisk. Client C has mounted disk \\S\ServerDisk as disk Z: . Your system M is a monitor with CBFS Filter installed. M also has mounted \\S\ServerDisk as disk T: . Now if some process on M accesses disk T, CBFS Filter handles this access. If some process on C accesses disk Z:, requests go from C to S and never reach M. M has no way to be informed about changes on remote ServerDisk, so CBFS Filter can't handle such requests. If the operation is performed locally on S, CBFS Filter can't handle such requests either.

Example 2:

You have a server S that shares disk ServerDisk. Client C has mounted disk \\S\ServerDisk as disk Z: . Client C2 has mounted disk \\S\ServerDisk as disk T:. CBFS Filter is installed on S. Now if some process on C accesses disk Z:, CBFS Filter handles this access. If some process on C2 accesses disk T:, CBFS Filter can handle such requests as well. If the operation is performed locally on S, CBFS Filter handles such requests fine.

Ready to get started?

Learn more about Callback Technologies or download a free trial.

Download Now