linux-cifs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paulo Alcantara <pc@cjr.nz>
To: Martijn de Gouw <martijn.de.gouw@prodrive-technologies.com>,
	"linux-cifs@vger.kernel.org" <linux-cifs@vger.kernel.org>
Subject: Re: cifs.upcall requests ticket for wrong host when using dfs
Date: Fri, 03 Jan 2020 17:14:48 -0300	[thread overview]
Message-ID: <878smoqouf.fsf@cjr.nz> (raw)
In-Reply-To: <5260c45c-0a31-168d-f9db-83bb6bd4a2cf@prodrive-technologies.com>

Martijn de Gouw <martijn.de.gouw@prodrive-technologies.com> writes:

> I tried kernel 5.4.6, including this fix, but still no luck:
> [   25.825075] CIFS: Attempting to mount //domain.com/common
> [   27.127925] CIFS VFS:  BAD_NETWORK_NAME: \\domain.com\common
> [   31.406697] CIFS: Attempting to mount //DC01.domain.com/common/Pd_Std
> [   31.414527] srv rsp padded more than expected. Length 98 not 73 for cmd:1 mid:1
> [   31.414533] Status code returned 0xc000006d STATUS_LOGON_FAILURE
> [   31.414537] CIFS VFS: \\DC01.domain.com Send error in SessSetup = -13
> [   31.414544] CIFS VFS: cifs_mount failed w/return code = -13
> [   31.414590] CIFS: Attempting to mount //DC01.domain.com/common/Pd_Std
> [   31.422410] Status code returned 0xc000006d STATUS_LOGON_FAILURE
> [   31.422416] CIFS VFS: \\DC01.domain.com Send error in SessSetup = -13
> [   31.422423] CIFS VFS: cifs_mount failed w/return code = -13
>
> Where 4.19 prints:
> [  132.012498] CIFS: Attempting to mount //domain.com/common
> [  132.183038] CIFS VFS: error -2 on ioctl to get interface list
> [  132.344343] CIFS: Attempting to mount //nas01/common$/pd_std

Thanks for testing it.

Could you post dmesg output of both versions with debugging enabled as per
instructions in [1]?

Thanks,
Paulo

[1] https://wiki.samba.org/index.php/LinuxCIFS_troubleshooting

  reply	other threads:[~2020-01-03 20:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-03 14:11 cifs.upcall requests ticket for wrong host when using dfs Martijn de Gouw
     [not found] ` <87png0boej.fsf@cjr.nz>
2020-01-03 16:30   ` Martijn de Gouw
2020-01-03 20:14     ` Paulo Alcantara [this message]
2020-01-06 15:07       ` Martijn de Gouw
2020-01-06 23:30         ` Paulo Alcantara
2020-01-07 16:13           ` Martijn de Gouw
2020-01-08 17:46             ` Paulo Alcantara
2020-01-09 12:27               ` Martijn de Gouw
2020-01-09 13:06                 ` Paulo Alcantara
2020-01-30 17:46                   ` Jacob Shivers
2020-01-30 18:55                     ` Steve French
2020-01-30 19:06                       ` Jacob Shivers

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=878smoqouf.fsf@cjr.nz \
    --to=pc@cjr.nz \
    --cc=linux-cifs@vger.kernel.org \
    --cc=martijn.de.gouw@prodrive-technologies.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).