STATUS_PATH_NOT_COVERED is 'normal' indicating that there is a DFS referral to a different target server share - so the server you are mounting is redirecting you to another one. Also note that the error that is logged "CIFS VFS: DFS capability contradicts DFS flag" indicates that the server reported a different value for share flags and capabilities (which is probably a server bug). Since this is Ubuntu 18.04 it is very easy to try with recent kernels too and the 5.0 kernel had a huge improvement in DFS caching and failover and is worth trying as an experiment. Why don't you check and see if https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.0/ works around (what may be) a server bug with the illegal flags? That kernel includes the good work by Paulo to improve DFS caching and failover. On Wed, Feb 27, 2019 at 8:38 AM Alexis Fortin-Côté <alexis.fortin-cote.1@xxxxxxxxx> wrote: > > Hi, > Thanks for your help. > But it doesn't seem to be an authentication failure. I tried all sec option. Some clearly failed early (in the wireshark trace) due to authentification problem. Its seems to be able to authenticate with ntlmv2. > But fails latter in the exchange. > > https://pastebin.com/zkRHtTvq > > Frame 25 Create Response, Error: STATUS_PATH_NOT_COVERED > > Any idea? > > Thanks again. > > Alex > > ________________________________________ > De : Robin P. Blanchard <robin.blanchard@xxxxxxxxx> > Envoyé : 22 février 2019 14:13 > À : Alexis Fortin-Côté > Cc : linux-cifs@xxxxxxxxxxxxxxx > Objet : Re: mount -t cifs fails while smbclient succeed > > Compare: > > failed: lines 21-42 > > I think you may need to mount with a different sec option: > > > sec= > Security mode. Allowed values are: > > · none - attempt to connection as a null user (no name) > > · krb5 - Use Kerberos version 5 authentication > > · krb5i - Use Kerberos authentication and forcibly enable packet > signing > > · ntlm - Use NTLM password hashing > > · ntlmi - Use NTLM password hashing and force packet signing > > · ntlmv2 - Use NTLMv2 password hashing > > · ntlmv2i - Use NTLMv2 password hashing and force packet signing > > · ntlmssp - Use NTLMv2 password hashing encapsulated in Raw > NTLMSSP message > > · ntlmsspi - Use NTLMv2 password hashing encapsulated in Raw > NTLMSSP message, and force packet signing > > The default in mainline kernel versions prior to v3.8 was sec=ntlm. > In v3.8, the default was changed to sec=ntlmssp. > > On Fri, Feb 22, 2019 at 9:30 AM Alexis Fortin-Côté > <alexis.fortin-cote.1@xxxxxxxxx> wrote: > > > > > > Hi, > > I have trouble mounting a windows share on my Ubuntu 18.04 workstation. > > I've tried every thing I found using google search to no avail. > > > > The following smbclient command works, so I know my Username and Password are working > > smbclient -U ulaval.ca\\alfoc //132.203.235.15/Partages/FSS > > > > But the following mount fails with errors : > > sudo mount -t cifs -o cred=/home/alexis/smbcred,vers=2.0 //fssdc1.fss.ulaval.ca/Partages/FSS/ /home/alexis/win/ > > > > mount error(22): Invalid argument > > > > I've logged the failing and successful trace with wireshark > > failed : https://pastebin.com/7UTBNgs2 > > success : https://pastebin.com/kQ80vVmr > > > > I'm using Kernel 4.20.11-042011-generic > > I'm not sure about the server configuration, but it looks like its a windows server that support smb vers=1.0 and vers=2.0 > > mount.cifs version: 6.8 > > > > dmesg with debug information reads when it fails: > > [ 2021.652324] Status code returned 0xc0000016 STATUS_MORE_PROCESSING_REQUIRED > > [ 2021.667748] CIFS VFS: DFS capability contradicts DFS flag > > [ 2021.673168] Status code returned 0xc0000257 STATUS_PATH_NOT_COVERED > > [ 2021.675001] CIFS VFS: cifs_mount failed w/return code = -22 > > > > Thanks for helping, > > Please respond (cc) to this address. > > > > Alex > > > > -- Thanks, Steve
