/git/tmp > ls -l FOO/
lrwxrwxrwx 1 vlendec users 23 20. Mai 16:15 link -> msdfs:192.168.234.100\tmp
smb: \> cd foo/link
cd \foo\link\: NT_STATUS_PATH_NOT_COVERED
smb: \> cd FOO/link
Connection to 192.168.234.100 failed (Error NT_STATUS_NETWORK_UNREACHABLE)
Unable to follow dfs referral [\192.168.234.100\tmp]
cd \FOO\link\: NT_STATUS_PATH_NOT_COVERED
See that I have a directory FOO with a valid msdfs link inside. If I try to access that as foo/link it just gives NT_STATUS_PATH_NOT_COVERED. If I access it as FOO/link, it gets one step further. The NETWORK_UNREACHABLE is a different problem (I'm running this on socket wrapper right now). The bug I want to point out is the different behaviour of foo vs FOO.
This is a bug already fixed in master for a different reason: fe839b65a7b4 fixes upload of a special printer driver which relies on a case insensitive file system. The same fix applies to case insensitive DFS links: In both code paths we are using fake internal connection_struct's.
Created attachment 4171 [details]
This is essentially fe839b65a7b4 from master in 3.2
+1 from me. This should be safe to add to 3.3 also IMHO.
Yep, this is 3.3 also. I just did not want to open two bugs :-)
Karolin, please tell me if the patch doesn't apply cleanly to 3.3.
Will be included in 3.3.5 and 3.2.12.