Cannot access SMB share via Kerberos

[sebma]

The associated forum post URL from https://forum.rclone.org

What is the problem you are having with rclone?

It seems rclone is using NTLM by default which has been disabled by our security team therefore I get a couldn't connect SMB: response error: The attempted logon is invalid. This is either due to a bad username or authentication information. error.

What is your rclone version (output from rclone version)

# rclone version
rclone v1.61.1
- os/version: centos 7.9.2009 (64 bit)
- os/kernel: 3.10.0-1160.62.1.el7.x86_64 (x86_64)
- os/type: linux
- os/arch: amd64
- go/version: go1.19.4
- go/linking: static
- go/tags: none

Which OS you are using and how many bits (e.g. Windows 7, 64 bit)

CentOS Linux release 7.9.2009 , 64 bits

Which cloud storage system are you using? (e.g. Google Drive)

SMB Share

The command you were trying to run (e.g. rclone copy /tmp remote:tmp)

# rclone --low-level-retries 1 ls myNAS-SMB:
2024/04/24 15:45:13 ERROR : : error listing: couldn't connect SMB: response error: The attempted logon is invalid. This is either due to a bad username or authentication information.
2024/04/24 15:45:13 Failed to ls with 2 errors: last error was: couldn't connect SMB: response error: The attempted logon is invalid. This is either due to a bad username or authentication information.

A log from the command with the -vv flag (e.g. output from rclone -vv copy /tmp remote:tmp)

# rclone --low-level-retries 1 -vv ls myNAS-SMB:
2024/04/24 15:42:10 DEBUG : rclone: Version "v1.61.1" starting with parameters ["rclone" "--low-level-retries" "1" "-vv" "ls" "myNAS-SMB:"]
2024/04/24 15:42:10 DEBUG : Creating backend with remote "myNAS-SMB:"
2024/04/24 15:42:10 DEBUG : Using config file from "/root/.config/rclone/rclone.conf"
2024/04/24 15:42:10 DEBUG : pacer: low level retry 1/1 (error couldn't connect SMB: response error: The attempted logon is invalid. This is either due to a bad username or authentication information.)
2024/04/24 15:42:10 DEBUG : pacer: Rate limited, increasing sleep to 200ms
2024/04/24 15:42:10 ERROR : : error listing: couldn't connect SMB: response error: The attempted logon is invalid. This is either due to a bad username or authentication information.
2024/04/24 15:42:10 DEBUG : 4 go routines active
2024/04/24 15:42:10 Failed to ls with 2 errors: last error was: couldn't connect SMB: response error: The attempted logon is invalid. This is either due to a bad username or authentication information.

How to use GitHub

• Please use the 👍 reaction to show that you are affected by the same issue.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.

[Animosity022]

You have a really old version.

You'd want to update and re-test.

[sebma]

@Animosity022 Same behaviour with rclone v1.66.0 on another system :

 $ rclone version
rclone v1.66.0
- os/version: ubuntu 22.04 (64 bit)
- os/kernel: 5.15.0-58-generic (x86_64)
- os/type: linux
- os/arch: amd64
- go/version: go1.22.1
- go/linking: static
- go/tags: none
$ rclone -vv --low-level-retries 1 ls myNAS-SMB:
2024/04/25 12:05:16 DEBUG : rclone: Version "v1.66.0" starting with parameters ["rclone" "-vv" "--low-level-retries" "1" "ls" "myNAS-SMB:"]
2024/04/25 12:05:16 DEBUG : Creating backend with remote "myNAS-SMB:"
2024/04/25 12:05:16 DEBUG : Using config file from "/home/administrateur/.config/rclone/rclone.conf"
2024/04/25 12:05:17 DEBUG : pacer: low level retry 1/1 (error couldn't connect SMB: response error: The attempted logon is invalid. This is either due to a bad username or authentication information.)
2024/04/25 12:05:17 DEBUG : pacer: Rate limited, increasing sleep to 200ms
2024/04/25 12:05:17 ERROR : : error listing: couldn't connect SMB: response error: The attempted logon is invalid. This is either due to a bad username or authentication information.
2024/04/25 12:05:17 DEBUG : 6 go routines active
2024/04/25 12:05:17 Failed to ls with 2 errors: last error was: couldn't connect SMB: response error: The attempted logon is invalid. This is either due to a bad username or authentication information.
$