Comment 2 for bug 1981414

I can reproduce the bug with a NetApp filer (not sure which model or version of OnTap). I could also reproduce it with a Dell filer (again not sure which model or version of OneFS) but the sysadmins have found a way to work around the bug by using specific sets of ACLs on the share itself and its subdirectories. In any case I'm not certain how to reproduce the bug without making an SMB server available to you.

Any way, here is what I see on the client side on Ubuntu 18.04, Ubuntu 20.04 or Ubuntu 22.04 workstations (obfuscated):

$ sudo nmap -p445 --script smb-protocols xxxxx.xxxxx.xxx.xx
Starting Nmap 7.80 ( https://nmap.org ) at 2022-07-13 20:59 CEST
Nmap scan report for xxxxx.xxxxx.xxx.xx (xxx.xxx.xx.xxx)
Host is up (0.0036s latency).

PORT STATE SERVICE
445/tcp open microsoft-ds

Host script results:
| smb-protocols:
| dialects:
| 2.02
| 2.10
| 3.00
|_ 3.11

Nmap done: 1 IP address (1 host up) scanned in 0.38 seconds
$
$
$ smbclient //xxxxx.xxxxx.xxx.xx/SHARE/PARTAGES/NEUROSPIN -U username -W DOMAIN -k -c 'rename foo.bar bar.txt'
WARNING: The "syslog" option is deprecated
NT_STATUS_OBJECT_NAME_NOT_FOUND renaming files \xxxxx.xxxxx.xxx.xx\SHARE\PARTAGES\NEUROSPIN\foo.bar -> \xxxxx.xxxxx.xxx.xx\SHARE\PARTAGES\NEUROSPIN\bar.txt
$