TerraMaster Forum

viewtopic.php?p=44098#p44098

Have you found a solution yet? Specifically for TOS7.

We sincerely apologize for the delayed response due to internal task scheduling.

Regarding the issue you reported, we have identified the root cause in our lab environment and plan to fix it in a future TOS 7 release. Please stay tuned for upcoming system updates.

Before the official fix is released, you may refer to the following temporary workaround:

For clarity, we define another SMB server as follows: A --Target SMB server

Temporary Workaround Steps:

1. Configure SMB parameters on the NAS Go to: SMB Settings > Advanced > Custom, and add the following parameter:
There is no need to enable the “MSDFS VFS module” option in the UI at this time. After adding the parameter, click Apply.

2. Create a symbolic link on the NAS
Log in to the NAS via terminal and run the following command to create an MSDFS link:
3. Authenticate on the Windows client on your Windows PC, you need to first access the SMB service of server B and complete authentication (i.e., access \\B_server_IP and enter the credentials).

Result：

After completing the above steps, when accessing the NAS SMB share from Windows, you will see a folder with the name of the created symlink.
This folder actually maps to the shared directory on server B.

Thank you very much. It seems to have worked.

I actually only use it to map all my NAS shares to a single folder, so I only use one drive letter.