LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software
User Name
Password
Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.

Notices


Reply
  Search this Thread
Old 08-21-2020, 05:20 PM   #1
cesarsj
Member
 
Registered: Mar 2019
Location: Patos de Minas, MG, Brazil
Distribution: Slackware
Posts: 159

Rep: Reputation: Disabled
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?
 
Old 08-22-2020, 03:02 AM   #2
ondoho
LQ Addict
 
Registered: Dec 2013
Posts: 19,872
Blog Entries: 12

Rep: Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053
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?
 
Old 08-22-2020, 05:55 AM   #3
rpenny
Member
 
Registered: Jul 2019
Posts: 81

Rep: Reputation: Disabled
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
 
Old 08-23-2020, 02:34 AM   #4
allend
LQ 5k Club
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware64-15.0
Posts: 6,357

Rep: Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739
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.
 
Old 08-28-2020, 12:10 PM   #5
cesarsj
Member
 
Registered: Mar 2019
Location: Patos de Minas, MG, Brazil
Distribution: Slackware
Posts: 159

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by rpenny View Post
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
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.)
 
  


Reply

Tags
samba


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] default packaged dhcpcd-6.0.5-i486-3_slack14.1 contains routing bug Crew-L-T Slackware 1 12-02-2014 11:22 PM
xf86-video-intel-2.99.914-x86_64-1.txz breaks GL grissiom Slackware 2 07-29-2014 10:55 PM
Slackware -current 32 bit holds pan-0.134-x86_64-1.txz package gianco Slackware 4 02-25-2011 12:41 PM
Uneeded "/usr/lib64//firefox-3.6.10" directory in mozilla-firefox-4.0b6-x86_64-1.txz michelino Slackware 0 09-21-2010 05:20 AM
libstdc++.so.5 is missing from gcc-4.3.3_multilib-x86_64-4alien.txz samac Slackware 5 08-31-2009 06:57 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Software

All times are GMT -5. The time now is 01:52 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration