I have Samba on openSUSE Leap 15.4. I have a legacy Windows 2003 computer (WHS v1) on my network. At some point in openSUSE updates (even before 15.4), my ability for WHS to browse DFS links on openSUSE broke. I also have Windows 2008 and Windows 10 systems which continue to work as expected. I recently discovered that the source of the problem is that the Windows API FindFirstFile no longer works on a DFS link. It works fine when accessing the target share directly. *ALSO*, I can access a file on the DFS link if I use the filename directly, example "copy \\samson\dfs\data\test.txt <file://samson/dfs/data/test.txt> .", avoiding usage of FindFirstFile. I realize this is SMB1, which is deprecated, but I'd really like to fully use my WHS system as long as possible (it's not open to the Internet) for backups and such.
Jeremy Allison
2023-Feb-09 17:26 UTC
[Samba] SMB1 Windows API FindFirstFile broken for DFS
On Thu, Feb 09, 2023 at 10:30:45AM -0600, Kenneth Hagin via samba wrote:>I have Samba on openSUSE Leap 15.4. I have a legacy Windows 2003 computer >(WHS v1) on my network. At some point in openSUSE updates (even before >15.4), my ability for WHS to browse DFS links on openSUSE broke. I also >have Windows 2008 and Windows 10 systems which continue to work as expected. >I recently discovered that the source of the problem is that the Windows API >FindFirstFile no longer works on a DFS link. It works fine when accessing >the target share directly. *ALSO*, I can access a file on the DFS link if I >use the filename directly, example "copy \\samson\dfs\data\test.txt ><file://samson/dfs/data/test.txt> .", avoiding usage of FindFirstFile. I >realize this is SMB1, which is deprecated, but I'd really like to fully use >my WHS system as long as possible (it's not open to the Internet) for >backups and such.To debug this needs wireshark traces to compare between a working and failing system. Also it's not clear what client and what server are being used in your examples.