[Samba] parse_dfs_path_strict: Hostname XXX is not ours.

[Michael Tokarev]

On 9/15/26 10:38, Michael Tokarev via samba wrote:
> Hi!
> 
> I noticed massive logging on one of our servers, like the above.
> 
> [2026/09/15 09:06:08.354265,  0, pid=2251327] source3/smbd/msdfs.c:120(parse_dfs_path_strict)
>    parse_dfs_path_strict: Hostname ekis-files is not ours.
> [2026/09/15 09:06:08.490609,  0, pid=2251327] source3/smbd/msdfs.c:120(parse_dfs_path_strict)
>    parse_dfs_path_strict: Hostname EKIS-FILES.RGS.INT is not ours.
> [2026/09/15 09:06:19.610801,  0, pid=2251327] source3/smbd/msdfs.c:120(parse_dfs_path_strict)
>    parse_dfs_path_strict: Hostname ekis-files is not ours.
> 
> etc etc.
Replying to myself.

That was one confused windows client machine.

It become confused when I changed a "type" of share on ekis-files from regular
share to a `msdfs proxy = \\mars\files` - to switch to another file/samba server.
After restart of samba fileserver processs on ekis-files, the above started
happening, until I undid the change and converted this share on ekis-files back
to regular one.

It would be interesting to understand what's happening here and why the client
becomes confused this way, and maybe what is happening on the wire.

But at least the cause is known.

Thanks,

/mjt