[Samba] mount.cifs fails with protocol SMBv2.x on a DFS share

[L A Walsh]

Christian Garling via samba wrote:
> Take care that smbclient, cifs-utils and keyutils is installed. Also 
> have these lines in /etc/request-key.conf:
>
> create  cifs.spnego     *       *               /usr/sbin/cifs.upcall %k
> create  dns_resolver    *       *               /usr/sbin/cifs.upcall %k
>
> My setup satisfies these requirements. I have tried the connection 
> with these commands (I replaced our domain with example.com):
>
> mount -v -t cifs //office.example.com/technik /mnt/dfs -o 
> username=c.garling,domain=OFFICE,vers=2.0
> mount -v -t cifs //office.example.com/technik /mnt/dfs -o 
> username=c.garling,domain=OFFICE,vers=2.1
Isn't "mount.cifs" and the upcall stuff under the "linux-cifs" project --
a separate project from samba these days? 

Someone on the samba list might know the answers, but if you are having
a problem with the linux mount.cifs command mounting a Windows CIFS share
you might find more help on the linux-cifs list (@vger.kernel.org).

Looking at your dump, I saw a weirdity:
>
> If I do so I can see this in tcpdump:
> ...
> 100.394295512 192.168.23.107 -> 192.168.15.6 SMB2 494 Session Setup 
> Request, NTLMSSP_AUTH, User: OFFICE\c.garling
> 100.397795864 192.168.15.6 -> 192.168.23.107 SMB2 142 Session Setup 
> Response
> 100.397895000 192.168.23.107 -> 192.168.15.6 SMB2 198 Tree Connect 
> Request Tree: \\office.example.com\technik
> 100.398866908 192.168.15.6 -> 192.168.23.107 SMB2 143 Tree Connect 
> Response, Error: STATUS_BAD_NETWORK_NAME
\\office.example.com doesn't look like a valid machine name.  Do you 
have any idea how you might be getting from User 'OFFICE\c.garling' to a 
rather odd
looking machine name (or did you just substitute that in?)...