Josh Kelley wrote: > When DFS is enabled, the SMB protocol requires that the client send > the full path to the network share (including server), rather than > just the directory (e.g., \\server\share\parent\subdir1 instead of > just parent\subdir1). This lets the DFS server know what DFS root was > originally requested. The CIFS client fails to do that; it instead > just sends parent\subdir1, which causes parent to be interpreted as a > server name and subdir1 as a share name. This is why searching for > parent\subdir1\parent\subdir1 works; the initial "parent\subdir1" is > parsed out as the server and share, then parent\subdir1 is correctly > processed as the path. That's a great explanation - makes a lot of sense now!
However, this problem doesn't affect us under 2.6.18 - only the newer kernels. Maybe something was broken in the cifs kernel module in newer releases? > I reported this as a bug a while ago, but it apparently hasn't been > fixed yet. See https://bugzilla.samba.org/show_bug.cgi?id=4066. Thanks for that - I'll add a "me too" -- Cheers Jason Haar Information Security Manager, Trimble Navigation Ltd. Phone: +64 3 9635 377 Fax: +64 3 9635 417 PGP Fingerprint: 7A2E 0407 C9A6 CAF6 2B9F 8422 C063 5EBB FE1D 66D1 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
