All of lore.kernel.org
 help / color / mirror / Atom feed
From: samba-bugs@samba.org
To: cifs-qa@samba.org
Subject: [Bug 14713] SMBv3 negotiation fails with a Solaris server
Date: Wed, 26 May 2021 18:59:56 +0000	[thread overview]
Message-ID: <bug-14713-10630-PO8Nql0Izy@https.bugzilla.samba.org/> (raw)
In-Reply-To: <bug-14713-10630@https.bugzilla.samba.org/>

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

--- Comment #29 from Richard Flint <richard.flint@gmail.com> ---
Unfortunately, as I mentioned by email. The connection does indeed also fail
with server_encrypt_data=false.

After setting server_encrypt_data=false I try to mount with vers=3.1.1 and
without the seal option (since encryption is off on the server). This results
in the following mysterious error:

mount error(13): Permission denied
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log
messages (dmesg)

[249955.014343] CIFS: Attempting to mount //nonsuch/myshare
[249955.020762] CIFS: VFS: \\nonsuch failed to connect to IPC (rc=-13)
[249955.023383] CIFS: VFS: cifs_mount failed w/return code = -13

see wireshark trace in your email "3.1.1_encryptionoff.pcap".

Trying with smbclient on the same share with the same user and same password
with server_encrypt_data=false on the server and no --encrypt option results in
success:

smbclient //nonsuch/myshare --debuglevel=10 --user=myuser

see wireshark trace in your email "3.1.1_smbclient.pcap".

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

  parent reply	other threads:[~2021-05-26 19:00 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-14713-10630@https.bugzilla.samba.org/>
2021-05-25 14:14 ` [Bug 14713] SMBv3 negotiation fails with a Solaris server samba-bugs
2021-05-25 18:19 ` samba-bugs
2021-05-25 18:26 ` samba-bugs
2021-05-25 18:51 ` samba-bugs
2021-05-25 19:03 ` samba-bugs
2021-05-25 19:09 ` samba-bugs
2021-05-25 19:09 ` samba-bugs
2021-05-25 19:13 ` samba-bugs
2021-05-25 19:19 ` samba-bugs
2021-05-25 19:27 ` samba-bugs
2021-05-25 19:37 ` samba-bugs
2021-05-25 19:42 ` samba-bugs
2021-05-25 19:43 ` samba-bugs
2021-05-25 19:47 ` samba-bugs
2021-05-25 20:31 ` samba-bugs
2021-05-25 20:38 ` samba-bugs
2021-05-25 20:55 ` samba-bugs
2021-05-25 21:40 ` samba-bugs
2021-05-25 22:33 ` samba-bugs
2021-05-26  8:57 ` samba-bugs
2021-05-26  9:00 ` samba-bugs
2021-05-26  9:47 ` samba-bugs
2021-05-26 15:36 ` samba-bugs
2021-05-26 18:59 ` samba-bugs [this message]
2021-05-26 21:51 ` samba-bugs
2021-05-26 21:54 ` samba-bugs
2021-05-26 22:09 ` samba-bugs
2021-05-26 22:26 ` samba-bugs
2021-05-26 22:39 ` samba-bugs
2021-05-27 17:33 ` samba-bugs
2021-05-30 13:51 ` samba-bugs
2021-06-04  6:42 ` samba-bugs
2021-06-04 10:17 ` samba-bugs
2022-02-20 19:07 ` samba-bugs
2022-05-11 18:46 ` samba-bugs

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-14713-10630-PO8Nql0Izy@https.bugzilla.samba.org/ \
    --to=samba-bugs@samba.org \
    --cc=cifs-qa@samba.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.