Windows 10 acessando compartilhamento do Samba 4 no Debian 11 [RESOLVIDO]

adbeel
(usa Debian)

Enviado em 31/08/2021 - 13:55h

Tenho um sistema em Java com o DB PostgreSQL 12 que acessa dado arquivo.xml de um diretório com vários outros para montar determinado formulário de manipulação de uma tabela específica do DB.
O sistema funciona perfeito no Debian 11, Ubuntu 18 dentre outros. Tudo com o compartilhamento funcional com Samba 4.
No Windows 10, que também acessa compartilhamento Samba, a mesma operação só acessa sempre o último arquivo do diretório.
Testei várias configurações e o problema persiste.
Alguém tem alguma ideia de como resolver o problema? Agradeço antecipadamente.

danniel-lara
(usa Fedora)

Enviado em 31/08/2021 - 14:58h

tem como postar o seu smb.conf ?

adbeel
(usa Debian)

Enviado em 31/08/2021 - 16:00h

#======================= Global Settings =======================
# Adbeel Goes Filho. Update to Samba 4. 20210831.

[global]

## Browsing/Identification ###

# Change this to the workgroup/NT-domain name your Samba server will part of

workgroup = AGOES
netbios name = zeus
server string = AGOES - %h server

unix charset = UTF-8

# server min protocol = NT1
# client min protocol = NT1
# client max protocol = SMB3

server min protocol = SMB2_10
client min protocol = SMB2
client max protocol = SMB3

ntlm auth = yes

realm = agoes
server role = standalone server
dns forwarder = 192.168.0.5

# log level = 2

# server string is the equivalent of the NT Description field

hosts allow = 10.0. 192.168. 127.
local master = no
preferred master = no

guest ok = no
map to guest = Bad User

# username map = /etc/samba/smbusers

allow insecure wide links = yes
unix extensions = no

# Automaticaly Loads module “vfs_widelinks”, directories out of Samba shares. 20210828.

wide links = yes

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server

# Obsolete wins support = yes

# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both

# Obsolete wins server = 192.168.0.5

# This will prevent nmbd to search for NetBIOS names through DNS.
dns proxy = no

# What naming service and in what order should we use to resolve host names
# to IP addresses
; name resolve order = lmhosts host wins bcast

#### Networking ####

# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
; interfaces = 127.0.0.0/8 eth0

# interfaces = 10.0.0.0/16 enp1s0
interfaces = 127.0.0.0/8 192.168.0.0/16 eno1

# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself. However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
; bind interfaces only = true

bind interfaces only = yes

#### Debugging/Accounting ####

# This tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba/log.%m

# Put a capping on the size of the log files (in Kb).
max log size = 1000

# If you want Samba to only log through syslog then set the following
# parameter to 'yes'.
; syslog only = no

# We want Samba to log a minimum amount of information to syslog. Everything
# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
# through syslog you should set the following parameter to something higher.
### syslog = 0

# Do something sensible when Samba crashes: mail the admin a backtrace
panic action = /usr/share/samba/panic-action %d

####### Authentication #######

# "security = user" is always a good idea. This will require a Unix account
# in this server for every user accessing the server. See
# /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/ServerType.html
# in the samba-doc package for details.

### security = share
security = user
### security = domain
### security = ADS

# You may wish to use password encryption. See the section on
# 'encrypt passwords' in the smb.conf(5) manpage before enabling.

# Obsolet encrypt passwords = true

# If you are using encrypted passwords, Samba will need to know what
# password database type you are using.
passdb backend = tdbsam

obey pam restrictions = yes

; guest account = nobody
invalid users = root

# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
; unix password sync = no

# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<kahan@informatik.tu-muenchen.de> for
# sending the correct chat script for the passwd program in Debian Sarge).
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\sUNIX\spassword:* %n\n *Retype\snew\sUNIX\spassword:* %n\n *password\supdated\ssuccessfully* .

# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# 'passwd program'. The default is 'no'.
; pam password change = no

########## Domains ###########

# Is this machine able to authenticate users. Both PDC and BDC
# must have this setting enabled. If you are the BDC you must
# change the 'domain master' setting to no
#

### domain logons = yes

#
# The following setting only takes effect if 'domain logons' is set
# It specifies the location of the user's profile directory
# from the client point of view)
# The following required a [profiles] share to be setup on the
# samba server (see below)
; logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
; logon path = \\%N\%U\profile

# The following setting only takes effect if 'domain logons' is set
# It specifies the location of a user's home directory (from the client
# point of view)

logon drive = H:
logon home = \\%N\%U

# The following setting only takes effect if 'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in 'DOS' file format convention
; logon script = logon.cmd

# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe. The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u

########## Printing ##########

# If you want to automatically load your printer list rather
# than setting them up individually then you'll need this
; load printers = yes

# lpr(ng) printing. You may wish to override the location of the
# printcap file
; printing = bsd
; printcap name = /etc/printcap

# CUPS printing. See also the cupsaddsmb(8) manpage in the
# cupsys-client package.
; printing = cups
; printcap name = cups

# When using [print$], root is implicitly a 'printer admin', but you can
# also give this right to other users to add drivers and set printer
# properties
; printer admin = @ntadmin


############ Misc ############

# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
; include = /home/samba/etc/smb.conf.%m

# Most people will find that this option gives better performance.
# See smb.conf(5) and /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/speed.html
# for details
# You may want to add the following on a Linux system:
# SO_RCVBUF=8192 SO_SNDBUF=8192
socket options = TCP_NODELAY

# The following parameter is useful only if you have the linpopup package
# installed. The samba maintainer and the linpopup maintainer are
# working to ease installation and configuration of linpopup and samba.
; message command = /bin/sh -c '/usr/bin/linpopup "%f" "%m" %s; rm %s' &

# Domain Master specifies Samba to be the Domain Master Browser. If this
# machine will be configured as a BDC (a secondary logon server), you
# must set this to 'no'; otherwise, the default behavior is recommended.

domain master = auto

# Some defaults for winbind (make sure you're not using the ranges
# for something else.)
; idmap uid = 10000-20000
; idmap gid = 10000-20000
; template shell = /bin/bash
;
; The following was the default behaviour in sarge
; but samba upstream reverted the default because it might induce
; performance issues in large organizations
; See #368251 for some of the consequences of *not* having
; this setting and smb.conf(5) for all details
;
; winbind enum groups = yes
; winbind enum users = yes

# Default idmap config used for BUILTIN and local windows accounts/groups
idmap config *:backend = tdb
idmap config *:range = 2000-9999

# idmap config for domain FFTPJ
idmap config DOMAIN:backend = rid
idmap config DOMAIN:range = 10000-99999

# Use template settings for login shell and home directory
winbind nss info = template
winbind enum users = Yes
winbind enum groups = Yes
winbind use default domain = yes


#======================= Share Definitions =======================

[homes]
comment = Meus Documentos
browseable = no

# By default, the home directories are exported read-only. Change next
# parameter to 'yes' if you want to be able to write to them.

writable = yes

# File creation mask is set to 0700 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0775.

create mask = 0700

# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.

directory mask = 0700

# Restrict access to home directories
# to the one of the authenticated user
# This might need tweaking when using external authentication schemes

valid users = %S

# Un-comment the following and create the netlogon directory for Domain Logons
# (you need to configure Samba to act as a domain controller too.)
;[netlogon]
; comment = Network Logon Service
; path = /home/samba/netlogon
; guest ok = yes
; writable = no
; share modes = no

# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
; comment = Users profiles
; path = /home/samba/profiles
; guest ok = no
; browseable = no
; create mask = 0600
; directory mask = 0700

[printers]
comment = All Printers
browseable = no
path = /var/spool/samba
printable = yes
public = yes
writable = no
create mode = 0700

# Windows clients look for this share name as a source of downloadable
# printer drivers
[print$]
comment = Printer Drivers
path = /var/lib/samba/printers
browseable = yes
read only = yes
guest ok = no
# Uncomment to allow remote administration of Windows print drivers.
# Replace 'ntadmin' with the name of the group your admin users are
# members of.
; write list = root, @ntadmin

# A sample share for sharing your CD-ROM with others.
;[cdrom]
; comment = Samba server's CD-ROM
; writable = no
; locking = no
; path = /cdrom
; public = yes

# The next two parameters show how to auto-mount a CD-ROM when the
# cdrom share is accesed. For this to work /etc/fstab must contain
# an entry like this:
#
# /dev/scd0 /cdrom iso9660 defaults,noauto,ro,user 0 0
#
# The CD-ROM gets unmounted automatically after the connection to the
#
# If you don't want to use auto-mounting/unmounting make sure the CD
# is mounted on /cdrom
#
; preexec = /bin/mount /cdrom
; postexec = /bin/umount /cdrom

[satis]
comment = Sistema Satis
path = /home/satis/public_html
valid users = adbeel @satis
admin users = adbeel
public = yes
writable = yes
read list = adbeel @satis
write list = adbeel
read only = no
guest ok = no
printable = no
browseable = yes
follow symlinks = yes
create mask = 0775
directory mask = 0775

[util]
comment = Util
path = /util
valid users = @satis
public = yes
writable = no
guest ok = no
printable = no
browseable = yes
read only = yes

adbeel
(usa Debian)

Enviado em 18/09/2021 - 11:46h

Fiz várias e infrutíferas tentativas. No Windows habilitei nas suas configurações o protocolo SMB, e nada.
Testei com outras máquinas e funcionou perfeitamente com Debian, Ubuntu e iOS. Somente no Windows 10 não funciona. Não testei com outros windows porque não os tenho mais.
Repetindo o problema:
1. Tenho um sistema no Linux que possui um diretório /forms com vários arquivos .xml que servem para montar uma tela de forma automática. No Linux e iOS funciona bem, mas no Windows 10, dos vários arquivos existentes, ele somente acessa o último. É como ser o sistema não reconhecesse a lista de diretórios (No windows ele lista os arquivos perfeitamente no Gerenciador de arquivos e no prompt);
2. Já mudei a versão do Java desde a 12 até agora na 16 e o problema persiste, somente no Windows 10.
3. Tenho também um diretório /sqls on existem vários arquivos .xml com comandos sql específicos. Apresenta também o mesmo problema, somente no acesso de chamada pega somente o último arquivo. Exemplo fonte Java:
...
String w_arquivo = fileGetFill("type=mid&file=1");
...
public static String fileGetFull(String w_options){
String w = "";
String w_dir = lib.config.DIR_FORMS; // Diretório dos arquivos .xml dos FORMS.
String w_type= lib.sql.sql_field(w_options,"type").trim().toLowerCase();
if (w_type.equals("") || w_type.equals("form")) w_type="mid";
if (w_type.equals("sql")) w_dir = lib.config.DIR_SQLS; // Diretório dos arquivos .xml dos SQLS.
String w_file= lib.sql.sql_field(w_options,"file").trim().replace("./",""); // Normalização
File dirList = new File(w_dir);
File listFile[] = dirList.listFiles();
try {
for (int w_i=0; w_i < listFile.length; w_i++ ) {
//******************************************************************
w = ""+listFile[w_i].toString().replace("./","");
//******************************************************************
if ( w.contains(w_file)) { // Sai ao encontrar o arquivo solicitado.
break;
}
}
}
} catch (Exception e){
w = "";
lib.util.erro("Error. File="+w_file+". "+e.getMessage());
}
return w;
}
...
Há alguma coisa a mais que possa tentar?

Buckminster
(usa Debian)

Enviado em 19/09/2021 - 16:11h

Essas configurações abaixo estão no [homes].
Este homes é o compartilhamento para o Windows?

# File creation mask is set to 0700 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0775.

create mask = 0700

# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.

directory mask = 0700


O [satis] é o compartilhamento do sistema que as máquinas Windows conseguem acessar somente o último arquivo?

Tente criar de teste um compartilhamento somente para máquinas Windows de acordo com o exemplo abaixo alterando/acrescentando no Global:

[global]
workgroup = SAME_WORKGROUP_AS_CONFIGURED_IN_WINDOWS
server string = Samba Server %v
netbios name = HOST_NAME_OF_YOUR_LINUX_MACHINE_ON_NETWORK
security = user
map to guest = bad user
dns proxy = no

[yourshare]
path = /PATH/TO/YOURSHARE
valid users = YOUR_WINDOWS_USER_NAME
browsable = yes
writeable = yes
guest ok = no
read only = no
directory mask = 0775
create mask = 0775

Verifique também se não é o firewall ou o Selinux (se tiver).
E verifique as permissões das pastas e arquivos, pois as permissões do samba são diferentes das permissões do sistema e elas devem bater umas com as outras.


________________________________________________
Always listen the Buck!
Sanou tua dúvida, resolveu teu problema?
Então marque como Resolvido e escolha a Melhor Resposta.

adbeel
(usa Debian)

Enviado em 23/09/2021 - 12:04h

Prezado colega, primeiramente obrigado pela valorosa contribuição. Finalmente consegui resolver o problema que, após várias tentativas inerentes ao uso do sistema de arquivos e configuração do Samba, persistindo o problema, resolvi ir por outros caminhos e resolvi da seguinte forma:
1. Usei 2 computadores, um com Windows 10 e outro com Linux Debian 11;
2. Acessei o programa em Java em ambos usando o Netbeans 12.5;
3. Coloquei um "trace" em locais específicos do programa e avaliei nas duas plataformas. Resultado no fonte em Java 16_0_2:
...
String w_file= lib.sql.sql_field(w_options,"file"); // Aparece algo em torno de /teste/teste,xml em Linux e Windows 10;
String w_fs = System.getProperty("file.separator"); // Pega o separador de arquivos usado pelo sistema operacional.
File dirList = new File("/teste"); // Lista diretório /teste padrão.
File listFile[] = dirList.listFiles(); // Acessa os arquivos do diretório /teste com comandos implícitos da linguagem,
// Os arquivos aparecem como "/teste/teste.xml" no Linux e Windows 10.
w = listFile[w_i].toString(); // No Linux o separador de arquivos aparece como "/" e no Windows 10 como "\".
// Normalizei então o separador de arquivos, visto que no Linux (/) funciona e no Windows 10 não (\):
...
for (int w_i=0; w_i < listFile.length; w_i++ ) {
w = w.replace(w_fs, "/"); // Padronizei tudo como "/".
if (w.contains(w_file)){
System.out.println("File "+w_file+" - w = "+w+" > " );
if ( lib.files.isFile(w,"") ) {
// System.out.println(" Found File "+w_i+" "+" "+w_ud+": "+w_file+" - "+w);
break;
}
}
}
...
Ou seja agora os arquivos são comparados com "/teste/teste.xml" e "/teste.xml" sempre, fazendo com que a função funcionasse, e não "/teste/teste.xml" e "\teste.xml", onde "\teste.xml" jamais estaria contido em "/teste/teste.xml", fazendo com que a função ocasionasse problema.
Em Resumo:
1. Sistema de arquivos Samba 4 funcionando perfeitamente no Debian 10;
2. Acesso aos compartilhamentos do Samba pelo Windows 10 funcionando perfeitamente;
3. Java apresenta esse detalhe que só foi percebido com o "trace" e uma simples alteração no separador de arquivos resolveu.
4. Sistema funcionando perfeitamente em todas as plataformas testadas.

Obrigado pela ajuda. Deixo aqui minha experiência para prováveis futuros problemas semelhantes.

Buckminster
(usa Debian)

Enviado em 23/09/2021 - 14:49h

Por isso ele só acessava o último arquivo, ele não conseguia "subir" no caminho porque não reconhecia o separador.
Marque o tópico como resolvido.


________________________________________________
Always listen the Buck!
Sanou tua dúvida, resolveu teu problema?
Então marque como Resolvido e escolha a Melhor Resposta.