problem mounting under Xubuntu
Subsystems (2)
hi,
started using Xubuntu (11.10) and cannot get the mount.cifs to the NAS working.
the following command works from my slackware system:
mount.cifs //nas/public /mnt -o guest
the same command (except added option ro) executed on Xubuntu gives error
CIFS VFS: Send error in SessSetup = -13
I can access the NAS via smbclient.
after days of googling I'm still no wiser. below is a listing of the dmesg output. help, please.
[92841.000417] /build/buildd/linux-3.0.0/fs/cifs/cifsfs.c: Devname: //nas/public flags: 1 [92841.000428] /build/buildd/linux-3.0.0/fs/cifs/connect.c: null user [92841.000434] /build/buildd/linux-3.0.0/fs/cifs/connect.c: file mode: 0x1ed dir mode: 0x1ed [92841.000506] /build/buildd/linux-3.0.0/fs/cifs/connect.c: CIFS VFS: in cifs_mount as Xid: 52 with uid: 0 [92841.000510] /build/buildd/linux-3.0.0/fs/cifs/connect.c: UNC: \\nas\public ip: 192.168.0.10 [92841.000530] /build/buildd/linux-3.0.0/fs/cifs/connect.c: Socket created [92841.000534] /build/buildd/linux-3.0.0/fs/cifs/connect.c: sndbuf 16384 rcvbuf 87380 rcvtimeo 0x6d6 [92841.001152] /build/buildd/linux-3.0.0/fs/cifs/connect.c: CIFS VFS: in cifs_get_smb_ses as Xid: 53 with uid: 0 [92841.001157] /build/buildd/linux-3.0.0/fs/cifs/connect.c: Existing smb sess not found [92841.001165] /build/buildd/linux-3.0.0/fs/cifs/cifssmb.c: secFlags 0x7 [92841.001170] /build/buildd/linux-3.0.0/fs/cifs/transport.c: For smb_command 114 [92841.001174] /build/buildd/linux-3.0.0/fs/cifs/transport.c: Sending smb: total_len 82 [92841.001194] /build/buildd/linux-3.0.0/fs/cifs/connect.c: Demultiplex PID: 6045 [92841.243749] /build/buildd/linux-3.0.0/fs/cifs/connect.c: rfc1002 length 0x65 [92841.243770] /build/buildd/linux-3.0.0/fs/cifs/transport.c: cifs_sync_mid_result: cmd=114 mid=1 state=4 [92841.243777] /build/buildd/linux-3.0.0/fs/cifs/cifssmb.c: Dialect: 2 [92841.243783] /build/buildd/linux-3.0.0/fs/cifs/cifssmb.c: negprot rc 0 [92841.243787] /build/buildd/linux-3.0.0/fs/cifs/connect.c: Security Mode: 0x3 Capabilities: 0xe3fd TimeAdjust: 0 [92841.243791] /build/buildd/linux-3.0.0/fs/cifs/sess.c: sess setup type 1 [92841.243828] /build/buildd/linux-3.0.0/fs/cifs/transport.c: For smb_command 115 [92841.243832] /build/buildd/linux-3.0.0/fs/cifs/transport.c: Sending smb: total_len 232 [92841.247606] /build/buildd/linux-3.0.0/fs/cifs/connect.c: rfc1002 length 0x66 [92841.247623] /build/buildd/linux-3.0.0/fs/cifs/transport.c: cifs_sync_mid_result: cmd=115 mid=2 state=4 [92841.247628] /build/buildd/linux-3.0.0/fs/cifs/misc.c: Null buffer passed to cifs_small_buf_release [92841.247632] /build/buildd/linux-3.0.0/fs/cifs/sess.c: Guest login [92841.247635] /build/buildd/linux-3.0.0/fs/cifs/sess.c: UID = 100 [92841.247638] /build/buildd/linux-3.0.0/fs/cifs/sess.c: bleft 56 [92841.247642] /build/buildd/linux-3.0.0/fs/cifs/sess.c: serverOS=Unix [92841.247646] /build/buildd/linux-3.0.0/fs/cifs/sess.c: serverNOS=Samba 3.0.34 [92841.247650] /build/buildd/linux-3.0.0/fs/cifs/sess.c: serverDomain=WORKGROUP [92841.247654] /build/buildd/linux-3.0.0/fs/cifs/sess.c: ssetup freeing small buf f1f32540 [92841.247657] /build/buildd/linux-3.0.0/fs/cifs/connect.c: CIFS Session Established successfully [92841.247662] /build/buildd/linux-3.0.0/fs/cifs/connect.c: CIFS VFS: leaving cifs_get_smb_ses (xid = 53) rc = 0 [92841.247667] /build/buildd/linux-3.0.0/fs/cifs/connect.c: CIFS VFS: in cifs_get_tcon as Xid: 54 with uid: 0 [92841.247673] /build/buildd/linux-3.0.0/fs/cifs/transport.c: For smb_command 117 [92841.247677] /build/buildd/linux-3.0.0/fs/cifs/transport.c: Sending smb: total_len 90 [92841.248606] /build/buildd/linux-3.0.0/fs/cifs/connect.c: rfc1002 length 0x27 [92841.248620] /build/buildd/linux-3.0.0/fs/cifs/transport.c: cifs_sync_mid_result: cmd=117 mid=3 state=4 [92841.248625] Status code returned 0xc0000022 NT_STATUS_ACCESS_DENIED [92841.248630] /build/buildd/linux-3.0.0/fs/cifs/netmisc.c: Mapping smb error code 0xc0000022 to POSIX err -13 [92841.248635] /build/buildd/linux-3.0.0/fs/cifs/connect.c: CIFS VFS: leaving cifs_get_tcon (xid = 54) rc = -13 [92841.248639] /build/buildd/linux-3.0.0/fs/cifs/connect.c: CIFS Tcon rc = -13 [92841.248643] /build/buildd/linux-3.0.0/fs/cifs/connect.c: build_unc_path_to_root: full_path=\\nas\public [92841.248648] /build/buildd/linux-3.0.0/fs/cifs/transport.c: For smb_command 117 [92841.248652] /build/buildd/linux-3.0.0/fs/cifs/transport.c: Sending smb: total_len 94 [92841.251461] /build/buildd/linux-3.0.0/fs/cifs/connect.c: rfc1002 length 0x3c [92841.251473] /build/buildd/linux-3.0.0/fs/cifs/transport.c: cifs_sync_mid_result: cmd=117 mid=4 state=4 [92841.251478] /build/buildd/linux-3.0.0/fs/cifs/connect.c: CIFS Tcon rc = 0 ipc_tid = 1 [92841.251482] /build/buildd/linux-3.0.0/fs/cifs/cifssmb.c: In GetDFSRefer the path \nas\public [92841.251487] /build/buildd/linux-3.0.0/fs/cifs/transport.c: For smb_command 50 [92841.251490] /build/buildd/linux-3.0.0/fs/cifs/transport.c: Sending smb: total_len 108 [92841.252726] /build/buildd/linux-3.0.0/fs/cifs/connect.c: rfc1002 length 0x27 [92841.252731] /build/buildd/linux-3.0.0/fs/cifs/connect.c: invalid transact2 word count [92841.252743] /build/buildd/linux-3.0.0/fs/cifs/transport.c: cifs_sync_mid_result: cmd=50 mid=5 state=4 [92841.252748] Status code returned 0xc0000002 NT_STATUS_NOT_IMPLEMENTED [92841.252752] /build/buildd/linux-3.0.0/fs/cifs/netmisc.c: Mapping smb error code 0xc0000002 to POSIX err -22 [92841.252756] /build/buildd/linux-3.0.0/fs/cifs/cifssmb.c: Send error in GetDFSRefer = -22 [92841.252760] /build/buildd/linux-3.0.0/fs/cifs/connect.c: cifs_put_smb_ses: ses_count=1 [92841.252762] [92841.252765] /build/buildd/linux-3.0.0/fs/cifs/connect.c: CIFS VFS: in cifs_put_smb_ses as Xid: 55 with uid: 0 [92841.252769] /build/buildd/linux-3.0.0/fs/cifs/cifssmb.c: In SMBLogoff for session disconnect [92841.252773] /build/buildd/linux-3.0.0/fs/cifs/transport.c: For smb_command 116 [92841.252776] /build/buildd/linux-3.0.0/fs/cifs/transport.c: Sending smb: total_len 43 [92841.253503] /build/buildd/linux-3.0.0/fs/cifs/connect.c: rfc1002 length 0x2b [92841.253515] /build/buildd/linux-3.0.0/fs/cifs/transport.c: cifs_sync_mid_result: cmd=116 mid=6 state=4 [92841.256596] /build/buildd/linux-3.0.0/fs/cifs/connect.c: CIFS VFS: leaving cifs_mount (xid = 52) rc = -13 [92841.256600] CIFS VFS: cifs_mount failed w/return code = -13
sorry about the double posting, had problem setting up.
having scanned through last few posts, I hope I've subscribed to the correct list.
additional information about s/ware:
cat /etc/debian_version
wheezy/sid
mount.cifs -V
mount.cifs version: 5.0
dpkg -l | grep util-linux
ii util-linux 2.19.1-2ubuntu3 Miscellaneous system utilities
Although this is a very, very old version of Samba (3.0) in your NAS box, I am surprised that it is returning ERROR_STATUS_NOT_SUPPORTED on GetDFSReferral
Anyone know when that was added to Samba (I thought Samba 3.0 supported it all along).
Quoted 22 lines · jr
sorry about the double posting, had problem setting up.
having scanned through last few posts, I hope I've subscribed to the correct list.
additional information about s/ware:
cat
/etc/debian_version
wheezy/sidmount.cifs -V
mount.cifs version: 5.0dpkg -l | grep util-linux
ii util-linux 2.19.1-2ubuntu3 Miscellaneous system utilities--
To unsubscribe from this list: send the line "unsubscribe linux-cifs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Signature · 3 lines
Thanks, Steve
Maybe add the parameter/option ip=....
Some time ago I had a simular error. Adding the ip helped.
Stef
2011/11/28 Steve French <[email protected]>:
Quoted 42 lines
Although this is a very, very old version of Samba (3.0) in your NAS box, I am surprised that it is returning
ERROR_STATUS_NOT_SUPPORTEDon GetDFSReferralAnyone know when that was added to Samba (I thought Samba 3.0 supported it all along).
Quoted 13 lines · jr
sorry about the double posting, had problem setting up.
having scanned through last few posts, I hope I've subscribed to the correct list.
additional information about s/ware:
cat
/etc/debian_version
wheezy/sidmount.cifs -V
mount.cifs version: 5.0Quoted 9 lines
dpkg -l | grep util-linux
ii util-linux 2.19.1-2ubuntu3 Miscellaneous system utilities--
To unsubscribe from this list: send the line "unsubscribe linux-cifs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html--
Thanks,Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-cifs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 4 lines · Stef Bon
Maybe add the parameter/option ip=....
Some time ago I had a simular error. Adding the ip helped.Stef
thanks Stef, tried it but made no difference.
On Mon, 28 Nov 2011 03:35:22 +0000
jr <[email protected]> wrote:
--------------[snip]----------------
Quoted 16 lines
[92841.247667] /build/buildd/linux-3.0.0/fs/cifs/connect.c: CIFS VFS: in cifs_get_tcon as Xid: 54 with uid: 0 [92841.247673] /build/buildd/linux-3.0.0/fs/cifs/transport.c: For smb_command 117 [92841.247677] /build/buildd/linux-3.0.0/fs/cifs/transport.c: Sending smb: total_len 90 [92841.248606] /build/buildd/linux-3.0.0/fs/cifs/connect.c: rfc1002 length 0x27 [92841.248620] /build/buildd/linux-3.0.0/fs/cifs/transport.c: cifs_sync_mid_result: cmd=117 mid=3 state=4 [92841.248625] Status code returned 0xc0000022 NT_STATUS_ACCESS_DENIED [92841.248630] /build/buildd/linux-3.0.0/fs/cifs/netmisc.c: Mapping smb error code 0xc0000022 to POSIX err -13 [92841.248635] /build/buildd/linux-3.0.0/fs/cifs/connect.c: CIFS VFS: leaving cifs_get_tcon (xid = 54) rc = -13 [92841.248639] /build/buildd/linux-3.0.0/fs/cifs/connect.c: CIFS Tcon rc
Quoted 1 line
= -13
--------------[snip]----------------
Looks like the tree connect is falling down. Does the user you're connecting as have access to the exported share? You may want to check the logs on the NAS and see why it's rejecting the tree connect request.
Signature · 1 line
Jeff Layton <[email protected]>
Quoted 28 lines · Jeff Layton
On Mon, 28 Nov 2011 03:35:22 +0000
jr <[email protected]> wrote:--------------[snip]----------------
Quoted 16 lines
[92841.247667] /build/buildd/linux-3.0.0/fs/cifs/connect.c: CIFS VFS: in cifs_get_tcon as Xid: 54 with uid: 0 [92841.247673] /build/buildd/linux-3.0.0/fs/cifs/transport.c: For smb_command 117 [92841.247677] /build/buildd/linux-3.0.0/fs/cifs/transport.c: Sending smb: total_len 90 [92841.248606] /build/buildd/linux-3.0.0/fs/cifs/connect.c: rfc1002 length 0x27 [92841.248620] /build/buildd/linux-3.0.0/fs/cifs/transport.c: cifs_sync_mid_result: cmd=117 mid=3 state=4 [92841.248625] Status code returned 0xc0000022 NT_STATUS_ACCESS_DENIED [92841.248630] /build/buildd/linux-3.0.0/fs/cifs/netmisc.c: Mapping smb error code 0xc0000022 to POSIX err -13 [92841.248635] /build/buildd/linux-3.0.0/fs/cifs/connect.c: CIFS VFS: leaving cifs_get_tcon (xid = 54) rc = -13 [92841.248639] /build/buildd/linux-3.0.0/fs/cifs/connect.c: CIFS Tcon rcQuoted 1 line
= -13
--------------[snip]----------------
Looks like the tree connect is falling down. Does the user you're connecting as have access to the exported share? You may want to check the logs on the NAS and see why it's rejecting the tree connect request.
Quoted 7 lines
--
Jeff Layton <[email protected]> --
To unsubscribe from this list: send the line "unsubscribe linux-cifs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Not sure if tcon fails or not because, right below, another tree connection request succeeds.
[92841.248643] /build/buildd/linux-3.0.0/fs/cifs/connect.c: build_unc_path_to_root: full_path=\\nas\public [92841.248648] /build/buildd/linux-3.0.0/fs/cifs/transport.c: For smb_command 117 [92841.248652] /build/buildd/linux-3.0.0/fs/cifs/transport.c: Sending smb: total_len 94 [92841.251461] /build/buildd/linux-3.0.0/fs/cifs/connect.c: rfc1002 length 0x3c [92841.251473] /build/buildd/linux-3.0.0/fs/cifs/transport.c: cifs_sync_mid_result: cmd=117 mid=4 state=4 [92841.251478] /build/buildd/linux-3.0.0/fs/cifs/connect.c: CIFS Tcon
rc = 0 ipc_tid = 1
Quoted 5 lines · Jeff Layton
Looks like the tree connect is falling down. Does the user you're connecting as have access to the exported share? You may want to check the logs on the NAS and see why it's rejecting the tree connect request.
looked at logs (via browser) on NetGear NAS, appears not to have been recorded.
yes, I can mount the share(s) as '-o guest' from a slackware box, and I can access the NAS from xubuntu using smbclient, but using the mount.cifs command doesn't work.
Quoted 29 lines · On Mon, 28 Nov 2011 14:47:20 -0600 Shirish Pargaonkar…
Quoted 28 lines · Jeff Layton
On Mon, 28 Nov 2011 03:35:22 +0000
jr <[email protected]> wrote:--------------[snip]----------------
Quoted 16 lines
[92841.247667] /build/buildd/linux-3.0.0/fs/cifs/connect.c: CIFS VFS: in cifs_get_tcon as Xid: 54 with uid: 0 [92841.247673] /build/buildd/linux-3.0.0/fs/cifs/transport.c: For smb_command 117 [92841.247677] /build/buildd/linux-3.0.0/fs/cifs/transport.c: Sending smb: total_len 90 [92841.248606] /build/buildd/linux-3.0.0/fs/cifs/connect.c: rfc1002 length 0x27 [92841.248620] /build/buildd/linux-3.0.0/fs/cifs/transport.c: cifs_sync_mid_result: cmd=117 mid=3 state=4 [92841.248625] Status code returned 0xc0000022 NT_STATUS_ACCESS_DENIED [92841.248630] /build/buildd/linux-3.0.0/fs/cifs/netmisc.c: Mapping smb error code 0xc0000022 to POSIX err -13 [92841.248635] /build/buildd/linux-3.0.0/fs/cifs/connect.c: CIFS VFS: leaving cifs_get_tcon (xid = 54) rc = -13 [92841.248639] /build/buildd/linux-3.0.0/fs/cifs/connect.c: CIFS Tcon rcQuoted 1 line
= -13
--------------[snip]----------------
Looks like the tree connect is falling down. Does the user you're connecting as have access to the exported share? You may want to check the logs on the NAS and see why it's rejecting the tree connect request.
Quoted 7 lines
Quoted 7 lines
--
Jeff Layton <[email protected]> --
To unsubscribe from this list: send the line "unsubscribe linux-cifs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Ahh yeah, you're correct -- the cause of the failure is here:
[92841.251487] /build/buildd/linux-3.0.0/fs/cifs/transport.c: For smb_command 50 [92841.251490] /build/buildd/linux-3.0.0/fs/cifs/transport.c: Sending smb: total_len 108 [92841.252726] /build/buildd/linux-3.0.0/fs/cifs/connect.c: rfc1002 length 0x27 [92841.252731] /build/buildd/linux-3.0.0/fs/cifs/connect.c: invalid transact2 word count [92841.252743] /build/buildd/linux-3.0.0/fs/cifs/transport.c: cifs_sync_mid_result: cmd=50 mid=5 state=4 [92841.252748] Status code returned 0xc0000002 NT_STATUS_NOT_IMPLEMENTED [92841.252752] /build/buildd/linux-3.0.0/fs/cifs/netmisc.c: Mapping smb error code 0xc0000002 to POSIX err -22 [92841.252756] /build/buildd/linux-3.0.0/fs/cifs/cifssmb.c: Send error
in GetDFSRefer = -22
and 22 is -EINVAL. This machine is running 3.0? What may be best is to open a bug at bugzilla.samba.org so we can track this. We may need to see a capture of the traffic between the client and server.
From the supplied info:
[92841.243787] /build/buildd/linux-3.0.0/fs/cifs/connect.c: Security Mode: 0x3 Capabilities: 0xe3fd TimeAdjust: 0
CAP_DFS does not appear to be set. I also note that we never actually check for SMBFLG2_DFS in the cifs.ko code.
It seems like if those bits aren't set, we ought not try to chase DFS referrals at mount time...
Signature · 1 line
Jeff Layton <[email protected]>
Quoted 3 lines · Jeff Layton
and 22 is
-EINVAL. This machine is running 3.0? What may be best is to open a bug at bugzilla.samba.org so we can track this. We may need to see a capture of the traffic between the client and server.
what do I need to do to supply the traffic info?
meanwhile (sorry, not v knowledgable) what can I do by way of using options to get the mount.cifs to work?
Quoted 8 lines · jr
Quoted 4 lines · Jeff Layton
and 22 is
-EINVAL. This machine is running 3.0? What may be best is to open a bug at bugzilla.samba.org so we can track this. We may need to see a capture of the traffic between the client and server.what do I need to do to supply the traffic info?
Quoted 8 lines
meanwhile (sorry, not v knowledgable) what can I do by way of using options to get the mount.cifs to work?
--
To unsubscribe from this list: send the line "unsubscribe linux-cifs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Would be useful if you can capture wireshark traces during successful attempt with smbclient and failing attempt with cifs client.
Quoted 2 lines · Shirish Pargaonkar
Would be useful if you can capture wireshark traces during successful attempt with smbclient and failing attempt with cifs client.
have never used this tool, will install it later tonight. would you be kind enough to suggest/supply command-line/usage?
thanks.
Quoted 8 lines · jr
Quoted 2 lines · Shirish Pargaonkar
Would be useful if you can capture wireshark traces during successful attempt with smbclient and failing attempt with cifs client.
have never used this tool, will install it later tonight. would you be kind enough to suggest/supply command-line/usage?
Quoted 7 lines
thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-cifs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
You can use tcpdump (run that in a separate pty/tty) for each, smbclient mount and cifs client mount commands.
Something like tcpdump -s 4096 -w /tmp/<filename>.cap
and send those two files with captured packets.
and as well and send that file.
Something like
Quoted 17 lines · On Thu, 1 Dec 2011 00:14:53 -0600 Shirish Pargaonkar…
Quoted 8 lines · jr
Quoted 2 lines · Shirish Pargaonkar
Would be useful if you can capture wireshark traces during successful attempt with smbclient and failing attempt with cifs client.
have never used this tool, will install it later tonight. would you be kind enough to suggest/supply command-line/usage?
Quoted 7 lines
thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-cifs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 7 lines
You can use tcpdump (run that in a separate pty/tty) for each, smbclient mount and cifs client mount commands.
Something like tcpdump -s 4096 -w /tmp/<filename>.cap
and send those two files with captured packets.and as well and send that file.
Something like
See the directions here:
http://wiki.samba.org/index.php/LinuxCIFS_troubleshooting#Wire_Captures
Ideally, you'd probably want to open a bug at bugzilla.samba.org so you don't have to email these files around (they can be rather large).
Signature · 1 line
Jeff Layton <[email protected]>
Quoted 6 lines · Shirish Pargaonkar
You can use tcpdump (run that in a separate pty/tty) for each, smbclient mount and cifs client mount commands.
Something like tcpdump -s 4096 -w /tmp/<filename>.cap
and send those two files with captured packets.
I used the tcpdump command as above, two binary files (total 11k) attached, the result of running the following commands as a normal user:
smbclient //nas/public
sudo mount.cifs //nas/public /mnt -o guest
smbclient went ok (I did a du and exit), the mount.cifs failed.
thank you.
Quoted 28 lines · Jeff Layton
On Mon, 28 Nov 2011 03:35:22 +0000
jr <[email protected]> wrote:--------------[snip]----------------
Quoted 16 lines
[92841.247667] /build/buildd/linux-3.0.0/fs/cifs/connect.c: CIFS VFS: in cifs_get_tcon as Xid: 54 with uid: 0 [92841.247673] /build/buildd/linux-3.0.0/fs/cifs/transport.c: For smb_command 117 [92841.247677] /build/buildd/linux-3.0.0/fs/cifs/transport.c: Sending smb: total_len 90 [92841.248606] /build/buildd/linux-3.0.0/fs/cifs/connect.c: rfc1002 length 0x27 [92841.248620] /build/buildd/linux-3.0.0/fs/cifs/transport.c: cifs_sync_mid_result: cmd=117 mid=3 state=4 [92841.248625] Status code returned 0xc0000022 NT_STATUS_ACCESS_DENIED [92841.248630] /build/buildd/linux-3.0.0/fs/cifs/netmisc.c: Mapping smb error code 0xc0000022 to POSIX err -13 [92841.248635] /build/buildd/linux-3.0.0/fs/cifs/connect.c: CIFS VFS: leaving cifs_get_tcon (xid = 54) rc = -13 [92841.248639] /build/buildd/linux-3.0.0/fs/cifs/connect.c: CIFS Tcon rcQuoted 1 line
= -13
--------------[snip]----------------
Looks like the tree connect is falling down. Does the user you're connecting as have access to the exported share? You may want to check the logs on the NAS and see why it's rejecting the tree connect request.
Quoted 6 lines
--
Jeff Layton <[email protected]> --
To unsubscribe from this list: send the line "unsubscribe linux-cifs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Looked at the wireshark traces.
Jeff is right. Tree connect is denied for anonymous user.
Tree connect to IPC$ share succeeds subsequently.
You are authenticating as user jr when using smbclient but as user anonymous when using cifs client. I think that makes a difference during tree connect.
Quoted 9 lines · Shirish Pargaonkar
Looked at the wireshark traces.
Jeff is right. Tree connect is denied for anonymous user.
Tree connect to IPC$ share succeeds subsequently.You are authenticating as user jr when using smbclient but as user anonymous when using cifs client. I think that makes a difference during tree connect.
unfortunately, mount.cifs //nas/public /mnt -o username=jr does not work either (same error 13).
also, the anonymous access to the NAS does work fine from a slackware machine (which uses v 1.48).
do you have any (other) suggestions? again, thanks for your time.