Bug 15279 - smbclient Issue Evaluating Proxy Shares with Subfolders
Summary: smbclient Issue Evaluating Proxy Shares with Subfolders
Status: NEW
Alias: None
Product: Samba 4.1 and newer
Classification: Unclassified
Component: libsmbclient (show other bugs)
Version: 4.15.12
Hardware: All All
: P5 normal (vote)
Target Milestone: ---
Assignee: Samba QA Contact
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-01-06 02:44 UTC by Virtually Nick
Modified: 2023-01-06 13:06 UTC (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Virtually Nick 2023-01-06 02:44:40 UTC 
When using smbclient to connect to a Samba share that is configured with "msdfs proxy", I've observed that the full path provided in the proxy parameter is not always followed.

As an example, I can configure "share1" on "dfs.example.com" as follows:

==
[share1]
    comment = MS DFS Proxy Share
    msdfs root = yes
    msdfs proxy = \fileserver1.example.com\shares\share1
==

When connecting to \\dfs.example.com\share1 from smbclient, I am redirected to, and see the contents of "\\fileserver1.example.com\shares" rather than "\\fileserver1.example.com\shares\share1". In contrast to this, Windows, Mac, and even Linux via mount.cifs go to the expected location, the full path provided in the "msdfs proxy" parameter.

It seems as though smbclient is failing to evaluate the full DFS path provided and is stopping at the root share of the proxy location.

If I can provide any further output to help with debugging, please let me know.