Timeline for Why can I browse this Windows share using smbclient, but cannot mount it with mount.cifs?
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 6 at 18:34 | history | bounty awarded | Dan | ||
| Oct 6 at 18:34 | comment | added | Dan | I've tried the fixes resolver fixes but unfortunately they don't make a difference in terms of overall success. I'm gonna give you the bounty, though, because I think this is on the right track and getting me appreciably closer to success. 🙏 | |
| Oct 6 at 18:33 | comment | added | Dan | Yes, I think this is right: Another possibility is you might be walking a DFS link even when you “direct mount.” | |
| Sep 29 at 23:13 | comment | added | Mike | Another possibility is you might be walking a DFS link even when you “direct mount.” \\SERVERFILE01\shared\Sites\Blah can itself contain another DFS reparse point. smbclient happily follows the whole chain; the kernel client won’t unless the dns_resolver upcall above is working. After fixing the upcalls, try mounting the DFS namespace path (let kernel follow the referral) - bash sudo mount -t cifs //ad.company.com/Shared /mnt/l \ -o prefixpath=Sites/BLAH,domain=COMPANY,username=USERNAME,password=PASSWORD,sec=ntlmssp,vers=3.1.1,port=445 | |
| Sep 29 at 23:09 | comment | added | Mike | One possibility is your request‑key config is incomplete/outdated. The lines you tried only mention cifs.spnego and even use -c, which the current cifs.upcall ignores entirely. You also need a rule for the dns_resolver key type, because the kernel CIFS client asks userspace to resolve DFS referrals via that key. Without it you get the classic mount error(126): Required key not available. See manpage. - manpages.ubuntu.com/manpages/jammy/man8/cifs.upcall.8.html | |
| Sep 29 at 22:23 | comment | added | Dan | I have also tried guides like this one, putting create cifs.spnego * * /usr/sbin/cifs.upcall -c %k in my /etc/request-key.conf, as well as trying it with cifs.upcall -t. Neither of those appears to make any difference. | |
| Sep 29 at 22:22 | comment | added | Dan | Thanks, this is interesting! In the smbclient debug logs I do see it "redirecting" to other fileservers, eventually ending up at \\SERVERFILE01.AD.COMPANY.COM\shared\Sites\Blah. However, if I use that UNC path with mount -t cifs, I still get the same error. Am I missing some other step here 🤔? | |
| S Sep 29 at 22:08 | review | First answers | |||
| Sep 29 at 23:01 | |||||
| S Sep 29 at 22:08 | history | answered | Mike | CC BY-SA 4.0 |