Unable to establish network share on new NAS due to 'host not found' error (ref#WTSR6V)

[Michael_P_Scelfo (Michael)]

What’s happening?

· Other

How can we help?

· None of the above

Other options

· Other

Describe the issue

trying to establish network share on new NAS, getting host not found error. I used the path in the "get info " area of new music folder. also tried entering my nas credentials and both ways same error: host not found

Describe your network setup

unfi system, using UNAS PRO with Roon Nucleus on same network

[alex_h (Alex)]

Good day @Michael_P_Scelfo !

I hope you’re doing well today.

In our logs we were able to see the following:

10/27 22:19:47 [Local 10/27 18:19:47] Error: [broker/filsystem/drivelistshares/addsharedrive] error adding share: System.Exception: [cifs/mountconfig] invalid cifs path (post windowsization, missing third backslash): smb://UNAS-Pro-77

It means that likely share path was not provided correctly.

Can you please try to add it again but instead of name of the share machine use its ip so it looks like this for you:

smb://192.168.1.xxx/Personal-Drive/Music

or this

smb://192.168.1.xxx/Music

Let us know please whether this works.

Looking forward to your reply!

Regards.

[Michael_P_Scelfo (Michael)]

different issue/error

[vadim]

Hello @Michael_P_Scelfo,

From the diagnostic messages, it appears that the mount attempt is failing due to a login authentication error:

CIFS: Status code returned 0xc000006d STATUS_LOGON_FAILURE

This usually indicates either incorrect credentials, a permission mismatch, or SMB protocol incompatibility.

Please try the following steps:

1. Verify your NAS credentials

• Double-check that the username and password you’re entering in Roon match the NAS user account that has access to the shared folder.
• Make sure this account has read and write permissions to the Personal-Drive share.

2. Use the correct network path format

• In Roon, the share path should look like this:

\\192.168.1.108\Personal-Drive

or, if using a hostname:

\\UNASPRO\Personal-Drive

Avoid copying paths directly from “Get Info,” as those sometimes contain macOS-specific formatting.

3. Ensure SMB v2 or v3 is enabled on your NAS

• The log line

Use of the less secure dialect vers=1.0 is not recommended

suggests the connection might be falling back to SMBv1, which is disabled in modern systems for security reasons.

• Please enable SMB v2/v3 on your NAS and disable SMBv1 if possible.

After applying these steps, try reconnecting the share in Roon again.

If the issue persists, please let us know your NAS model, firmware version, and whether you can access the same share from another device (e.g., your computer) using the same credentials.

[connor]

Hi @Michael_P_Scelfo,

Have you had a chance to try the steps shared in the post above? We’re happy to clarify any details. Thank you!

[connor]

This thread is now closing due to inactivity/lack of response. Please open a new tech support request referencing this thread URL and we’ll merge threads to continue the conversation. Thank you!