Solved Remote Storage: unable to use SMB path, no error details given.

[Earthbound]

Version 20.0 update 7 Build 1057 running on Windows Server 2025. I am using the PWA admin console and I am presented with a flag about setting up remote storage.
I created a network storage location and confirmed that the assigned account in the remote storage panel has full read/write access.
I confirmed from workstation and a server on our network that that user account is able to map the SMB path and has full access to the SMB path.
I have all the folders created for all the checked datatypes and confirmed access to them.
Yes, I read through the help about Backup & Storage, but it is lacking any substance to assist in troubleshooting this issue.
I even went as far to create a second SMB location on a different device to ensure that there was no connection issue and use the same testing processes.
I also tested my domain administrators account credentials in that panel and still nada.
The only message I get is: "Cannot connect to SMB" and it does not matter which SMB path I choose.

It would be REALLY nice to know what that specifically means: The path/folder does not exist, if so which one? Or is a permissions issue?

For now, I will keep using the standard backup process and rely on the Scheduled Task I have to copy it to a remote location.

Thank you kindly for any assistance you may offer and have a great day.

 

[Charles_3CX]

Please verify that the path is correct and that the domain name, username, and password are accurate. Additionally, ensure that the user has full permissions to the shared folder on the Windows SMB share side.

Path: smb://<IP_address>/<shared_folder>
Domain: domain.local
Username: domain\user
Password: ********

 

[Earthbound]

Thank you Charles for taking the time to respond! The explicit notation you provided about the path style requiring the smb:// prefix is what was needed. Unfortunately, when I opened the panel for the first time it had my old path from the previous version of 3CX notated as \\servename\share, upon seeing this I assumed that that was a valid way of entering the path information. A simple test on that old existing path by the developers at 3CX to avert this would have gone a long way and putting a default value of "smb://youpathhere" as an example would have quickly avoided this misunderstanding. Putting your example in the help page would also help the average user like me out, I am by no means a 3CX guru. One last item, because there is a domain field, the example of putting Domain\user in the Username field does not work when the domain field is already populated with a domain value. Hoping this helps others in their journey with 3CX.

Have a great day!