Windows Explorer stops showing SMB shares after a network mounting point with a share is created.

Problem

If a network mounting point is created, and the specified server name is the same as the computer name (which is used by the system for SMB shares), then Windows Explorer will sometimes stop enumeration of SMB shares too early, resulting in only the "shares" that are associated with CBFS Connect network mounting points to be visible.

Description

This is a Windows Explorer bug whereby enumeration of network redirectors and their shares is performed incorrectly. When there are several network redirectors registered, and those redirectors provide shares with the same server name (for example "\\MyMachine"), then Explorer can't show/enumerate all of these shares correctly.

Workaround

Either use some "unique" server name that is different from the SMB server name (for example, instead of V:;machine_name;share_name use V:;unique_server_name;share_name), or use the STGMP_NETWORK_READ_ACCESS and/or STGMP_NETWORK_WRITE_ACCESS flags when creating the mounting point. In the latter case, CBFS Connect will create an SMB share that will be accessible via the network.