I created a local mounting point with the CBFS_SYMLINK_LOCAL | CBFS_SYMLINK_NETWORK combination of flags. Why is this disk visible via Network Neighborhood?

When a mounting point is created with CBFS_SYMLINK_NETWORK, it consists of two parts — an optional disk name (either a drive letter, e.g., Z:, or a "hidden" mounting point) and a UNC name, a mandatory network path that consists of the server name and the share name.

The CBFS_SYMLINK_LOCAL flag affects only the disk name. If the flag is set, the "disk name" (the drive letter or a "hidden" mounting point) will be visible only for the specified session.

The "UNC name" is always globally visible and accessible for all sessions. Yet, you can hide it in Explorer and further prevent access to the disk from different sessions. The mounting point can be hidden by specifying CBFS_SYMLINK_NETWORK_HIDDEN_SHARE. Access can be controlled and forbidden by checking the session Id in the OnCreateFile and OnOpenFile callbacks (then, if the session isn't allowed to access the mounting point, your code should return the ERROR_ACCESS_DENIED error).

Ready to get started?

Learn more about Callback Technologies or download a free trial.

Download Now