[Bug 14713] SMBv3 negotiation fails with a Solaris server

[samba-bugs@samba.org]

https://bugzilla.samba.org/show_bug.cgi?id=14713

--- Comment #33 from Richard Flint <richard.flint@gmail.com> ---
with vers=3.0 (and without seal) specified on the client and
server_encrypt_data=false specified on the server, the following new fun
happens:

mount error(2): No such file or directory
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log
messages (dmesg)

and dmesg says: 

[261829.875860] CIFS: Attempting to mount //nonsuch/myshare
[261829.891575] CIFS: VFS: \\nonsuch\IPC$ validate protocol negotiate failed:
-13
[261829.893269] CIFS: VFS: \\nonsuch failed to connect to IPC (rc=-5)
[261829.895940] CIFS: VFS: \\nonsuch\myshare validate protocol negotiate
failed: -13
[261829.897752] CIFS: VFS: session 00000000bfe08581 has no tcon available for a
dfs referral request
[261829.900102] CIFS: VFS: cifs_mount failed w/return code = -2

I also notice a new message on the server server. Note that cmd=0x3 is now
cmd=0xb - whatever that signifies.

May 26 23:11:53 nonsuch smbsrv: [ID 211007 kern.warning] WARNING: bad
signature, cmd=0xb

A wireshark trace for the above has been emailed to you "3.0_mount.pcap"

As usual, for comparison smbclient works flawless (hopefully -m SMB3 was the
right way to force SMB 3.0 dialect...)
smbclient //nonsuch/myshare -m SMB3 --user=myuser

A wireshark trace for the above smbclient interaction has been emailed to you:
"3.0_smbclient.pcap"

Throughout all this dialogue with you, signing on the server has been
'enabled', but not 'required'.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.