Where would I be able to download exactly that version samba-4.4.16-x86_64-3_slack14.1.txz?
 

I want to simulate a nobody connections error for each file opened on a samba windows 10 client, only on the production machine, it's samba-4.4.16-x86_64-3_slack14.1.txz, and on the test machine it's samba-4.4 .16-x86_64-1_slack14.1.txz, and with this version I did not detect the problem. I couldn't find the exact package to download, and I can't just clone the vm (vmware virtualizer), as it is a 4 TB NAS, and there is no other storage that would support the clone. Would I be able to assemble this version of the package by copying some specific folders from the production machine to the test machine?

I'm not sure why you didn't post this under Slackware, but since you didn't I may attempt an answer.

• Slackware must have repositories and possibly also stores different versions of a given software. Have a look there. Usually they are directly accessible with a browsable folder structure.
• You could ask Slackware to list the contents of the package in question, and move all these files to the target machine: it "should" work. I would only do this if the target machine is disposable

But something bothers me about your post.
I ask myself what you're really trying to achieve here? Are you really just simulating a specific error? Why? Is there a different problem behind this that you are trying to solve?

Your main problem here is that Samba 4.4.x is EOL, so if you do manage to track down a bug, you will never get it fixed. If it is a bug, it may have already been fixed in a later version.
It may not be a bug, it could be a miss-configuration in your smb.conf, or it could be that SMBv1 is turned off on the Win10 machine, it could be anything, but we cannot help further because you haven't given us anything to work with :)

Looks like a Frankenstein setup to me.
'samba-4.4.16-x86_64-3_slack14.1.txz' is not an official Slackware package name, so I suspect a local build and install.
On Slackware64 14.1, the official package is samba-4.1.0-x86_64-2.txz
On Slackware64 14.2, the official packages is samba-4.4.4-x86_64-3.txz
On Slackware64-current, the official packages is samba-4.12.5-x86_64-1.txz

If the samba-4.4.16-x86_64-3_slack14.1.txz packages was installed correctly, then there will be a file /var/log/packages/samba-4.4.16-x86_64-3_slack14.1 with a list of files in the package.

As @rpenny says, the problem you are tracing is more likely to be from changes to Windows since the Samba packages was installed.

SMBv1 was disabled but even after I activated it, I was unable to simulate the problem in Windows 10, within the testing environment. The settings I put on the NAS Slackware 14.2 are the same as the production. What differentiates is version 4.4.16_x86-64_1 on the test machine and 4.4.16_x86-64_3, and importantly: in production users are searched for on an LDAP server, in the test there was no way to simulate this.


Some configurations:

[global]
server role = classic primary domain controller
workgroup = X
server string = Servidor Samba NASX
netbios name = NASX
netbios aliases = NASX
dos charset = CP850
unix charset = ISO8859-1
encrypt passwords = Yes
wide links = no
log file = /var/log/samba/samba.%m
preserve case = yes
short preserve case = yes
default case = lower
time server = yes
max connections = 0
deadtime = 1
keepalive = 120
utmp = yes
remote browse sync = no
remote announce = no
log level = 2
security = user
printing = lprng
max log size = 5000

Some configurations that I did not have to put in the test VM because of LDAP:

passdb backend = ldapsam:ldaps://ldap.myenterprise.edu.br

ldapsam:trusted = no
ldapsam:editposix = no
ldap ssl = off
ldap admin dn = cn=freenasbdc01,ou=DSA,dc=myenterprise,dc=edu,dc=br
ldap suffix = dc=unipam,dc=edu,dc=br
ldap group suffix = ou=groups
ldap user suffix = ou=people
ldap machine suffix = ou=machines
ldap idmap suffix = ou=Idmap
ldap passwd sync = yes
idmap uid = 2147483648-4294967294
idmap gid = 2147483648-4294967294
idmap backend = ldaps:ldaps://ldap.unipam.edu.br
ldap delete dn = no

Some warnings of testparm in VM of production:

WARNING: The "idmap uid" option is deprecated
WARNING: The "idmap gid" option is deprecated
WARNING: The "idmap backend" option is deprecated
WARNING: You have some share names that are longer than 12 characters.
These may not be accessible to some older clients.
(Eg. Windows9x, WindowsMe, and smbclient prior to Samba 3.0.)