How can I stop these DFS errors from filling up my logs?

I searched the forum, disabled NetBIOS, and kept WSD enabled, but the errors are still appearing.

Feb 20 09:42:55 Juno smbd[273155]: [2026/02/20 09:42:55.992568, 0] ../../source3/smbd/msdfs.c:120(parse_dfs_path_strict)

Feb 20 09:42:55 Juno smbd[273155]: parse_dfs_path_strict: Hostname JunoL is not ours.

Feb 20 09:42:58 Juno smbd[273155]: [2026/02/20 09:42:58.797829, 0] ../../source3/smbd/msdfs.c:120(parse_dfs_path_strict)

Feb 20 09:42:58 Juno smbd[273155]: parse_dfs_path_strict: Hostname JunoL is not ours.

Feb 20 09:45:06 Juno smbd[273155]: [2026/02/20 09:45:06.081588, 0] ../../source3/smbd/msdfs.c:120(parse_dfs_path_strict)

Feb 20 09:45:06 Juno smbd[273155]: parse_dfs_path_strict: Hostname JunoL is not ours.

2 hours ago, Gico said:

Hostname JunoL is not our

The server name is Juno, and this suggests you have a client trying to access JunoL

This is harmless, but to fix it, you can:

Add that as an alias to Netbios

Disable DFS

Fix the issue on the client

Accessing the server through multiple names is intentional.

It allows me to connect to the server in Windows using different user IDs, enabling separation of permissions across different applications.

These messages only started appearing in a recent 7.xx version. I was accessing the server the same way before, and there were no messages.

Edited February 20Feb 20 by Gico

If it's intentional, you can add an alias in SMB extras:

[global]

netbios name = Juno

netbios aliases = JunoL

or disable DFS since you likely don't need that:

[global]

host msdfs = no