Dago Pacheco wrote:

Ralph Angenendt escribió:

...

Dago Pacheco wrote:

...

Hi.... I have this CentOS 4.3 server that is used as a file, web and mail server just for LAN hosts. After an up2date procedure (in wich there was a lot of package involved.... about 500) I started having problems with file shareing in samba server.

As the Release Notes state (you did read those, didn't you?):

samba

samba has been updated to version 3.0.25b. This addresses several
critical issues affecting interoperability with Windows 2003™ and
Windows Vista™ (resolved in recent upstream releases).

All revisions to samba made for this update entailed invasive
code changes in some critical code paths. This made backporting
to version 3.0.10 non-feasible. As such, all samba packages were
rebased to version 3.0.25b instead.

Because of the rebase, some option interpretation methods
and components behaviors changed significantly. This means
that after upgrading samba, the configuration file will need
to be manually edited.

More details in those release notes.

But I just have Win2K users...... I'll check those release notes

Right, however the Vista and 2003 server thing is the reason for doing the changes in that way (rebasing and not backporting).

Once rebasing decision is made (not my decision ... made upstream :_) ), all config files need to be re-evaluated and changed as necessary, regardless of the clients involved, as there are different options ... some added, some removed, etc.

run this command:

testparm

Also you may want to look here:

http://samba.org/samba/history/samba-3.0.25b.html

Also follow the links to 3.0.25a, 3.0.25 to see what items should change (in the config file) on an upgrade from 3.0.10 TO 3.0.25b.

The bottom line is that your config file may need some work to function properly, and what you potentially need to change totally depends on what you currently have in your smb.conf file.

Thanks, Johnny Hughes

Dago Pacheco wrote:

Johnny Hughes escribió:

...

Dago Pacheco wrote:

...

Ralph Angenendt escribió:

...

Dago Pacheco wrote:

...

Hi.... I have this CentOS 4.3 server that is used as a file, web and mail server just for LAN hosts. After an up2date procedure (in wich there was a lot of package involved.... about 500) I started having problems with file shareing in samba server.

As the Release Notes state (you did read those, didn't you?):

samba

samba has been updated to version 3.0.25b. This addresses several critical issues affecting interoperability with Windows 2003™ and Windows Vista™ (resolved in recent upstream releases).

All revisions to samba made for this update entailed invasive code changes in some critical code paths. This made backporting to version 3.0.10 non-feasible. As such, all samba packages were rebased to version 3.0.25b instead.

Because of the rebase, some option interpretation methods and components behaviors changed significantly. This means that after upgrading samba, the configuration file will need to be manually edited.

More details in those release notes.

...

But I just have Win2K users...... I'll check those release notes

Right, however the Vista and 2003 server thing is the reason for doing the changes in that way (rebasing and not backporting).

Once rebasing decision is made (not my decision ... made upstream :_) ), all config files need to be re-evaluated and changed as necessary, regardless of the clients involved, as there are different options ... some added, some removed, etc.

run this command:

testparm

Also you may want to look here:

http://samba.org/samba/history/samba-3.0.25b.html

Also follow the links to 3.0.25a, 3.0.25 to see what items should change (in the config file) on an upgrade from 3.0.10 TO 3.0.25b.

The bottom line is that your config file may need some work to function properly, and what you potentially need to change totally depends on what you currently have in your smb.conf file.

Thanks, Johnny Hughes

---

---

CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos

ok... I'll try to reconfig samba, but by the way... is there any chance to get back to the previous version?

sure, you can reinstall it manually

and remove it from yum updates in the future

however, that is not recommended

Dago Pacheco wrote:

[please edit your mails]

what is not recomended?..... reinstall it or remvoe it from yum update?

Go back to the old version. You will *NOT* reveive any support or security updates for that.

however... the procedure for reinstall it should be:

yum remove samba

then manually install it from source code?

Erm, no. Not from source code, but the old rpm.

But as Johnny said: reevaluate your config files to see where it goes wrong. Don't go back to old insecure versions.

Ralph

Dago Pacheco wrote:

another detail.

When i try this command " smbclient //192.168.0.10/informatica -Uinformatica" and i give the correct password i get this

[root@servidor ~]# smbclient //192.168.0.10/informatica -Uinformatica Unknown parameter encountered: "hosts equiv" Ignoring unknown parameter "hosts equiv" Password: Domain=[MAKIMET] OS=[Unix] Server=[Samba 3.0.25b-1.el4_6.4] Server not using user level security and no password supplied. tree connect failed: NT_STATUS_BAD_NETWORK_NAME

OK ... I already told you to run testparm and to validate all your smb.conf lines.

Here is the first problem ... in 3.0.25, the command "host equiv=" is not longer valid and needs to be removed ... see this link:

http://www.samba.org/samba/history/samba-3.0.25.html

Start out by using testparm and fix all the errors and then you can go from there.

What i can notice here is that is says that the server is not using security..... what is that for?

It says it is not using "user level" security ... you probably have some other level of security in your config file. The different levels are detailed here [search for "security (G)"]:

http://us4.samba.org/samba/docs/man/manpages-3/smb.conf.5.html

(there is security = user, security = share, security = server, security = domain )

The only thing that is going to work is to look at your smb.config file, see what is set and figure out what you need to have set.

Johnny Hughes escribió:

OK ... I already told you to run testparm and to validate all your smb.conf lines.

Here is the first problem ... in 3.0.25, the command "host equiv=" is not longer valid and needs to be removed ... see this link:

http://www.samba.org/samba/history/samba-3.0.25.html

Start out by using testparm and fix all the errors and then you can go from there.

...

What i can notice here is that is says that the server is not using security..... what is that for?

It says it is not using "user level" security ... you probably have some other level of security in your config file. The different levels are detailed here [search for "security (G)"]:

http://us4.samba.org/samba/docs/man/manpages-3/smb.conf.5.html

(there is security = user, security = share, security = server, security = domain )

The only thing that is going to work is to look at your smb.config file, see what is set and figure out what you need to have set.

---

---

CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos

ok....This is the thing.... security level was set to "share". When thigs worked fine, there were a lot of shared folders that could be access by anyone in the network, but when it comes to acces the remote home folder, from windows client, samba checked the user/password used to loged in to windows and use it. Now whit security level set to "share", I can access the public folders, but when it comes to the "home" folders, smaba promt me to enter a password as an invited user. If I change security level to "user", samba promt user to enter user and password, that's good, but even if I enter a good login.... nothing happend, it doesn't validate it... and then, I can't access home and public folders.

This is the output for testparm

[root@servidor ~]# testparm Load smb config files from /etc/samba/smb.conf Processing section "[homes]" Processing section "[printers]" Processing section "[administracion]" Processing section "[biblioteca]" Processing section "[cartas]" Processing section "[fax]" Processing section "[formatos]" Processing section "[fotografias]" Processing section "[informes]" Processing section "[instaladores]" Processing section "[memos]" Processing section "[of_tecnica]" Processing section "[planos]" Processing section "[procedimientos]" Loaded services file OK. 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.) Server role: ROLE_STANDALONE Press enter to see a dump of your service definitions

[global] workgroup = MAKIMET netbios aliases = servidor server string = Servidor Maestranza interfaces = 192.168.0.10/255.255.255.0 security = SHARE obey pam restrictions = Yes pam password change = Yes username map = /etc/samba/smbusers log level = 3 log file = /var/log/samba/%m.log acl compatibility = winnt server signing = auto socket options = TCP_NODELAY IPTOS_LOWDELAY hostname lookups = Yes printcap name = /etc/printcap os level = 10 preferred master = No domain master = Yes dns proxy = No ldap ssl = no preload = global administracion biblioteca cartas fax formatos fotografias informes instaladores memos of_tecnica planos procedimientos read only = No create mask = 0777 force create mode = 0777 directory mask = 0777 force directory mode = 0777 guest ok = Yes hosts allow = 192.168.0., 127.0.0.

[homes] comment = Home directory for %S valid users = bodega, calidad, contador, cvaldivieso, dibujotec1, dibujotec2, faena, hcatalan, hfigueroa, personal, planning, produccion, root, secretaria, tvillagran, ymoya, ocastro, hsandoval, afigueroa, mahumada, chidalgo, informatica, @makimet force group = makimet create mask = 0700 directory mask = 0700 browseable = No

[printers] comment = All Printers path = /var/spool/samba printable = Yes browseable = No

[administracion] comment = Archivos Administracion path = /home/publicos/administracion force user = root force group = makimet

[biblioteca] comment = Biblioteca Electronica path = /home/publicos/biblioteca force user = root force group = makimet

[cartas] comment = Cartas Enviadas path = /home/publicos/cartas force user = root force group = makimet

[fax] comment = Historico Fax path = /home/publicos/fax force user = root force group = makimet

[formatos] comment = Formatos Oficiales path = /home/publicos/formatos force user = root force group = makimet

[fotografias] comment = Historico Fotografias path = /home/publicos/fotografias force user = root force group = makimet

[informes] comment = Informes Tecnicos path = /home/publicos/informes force user = root force group = makimet

[instaladores] comment = Programas de Instalacion path = /home/publicos/instaladores force user = root

[memos] comment = Historico Memos path = /home/publicos/memos force user = root force group = makimet

[of_tecnica] comment = Documentos Oficina Tecnica path = /home/publicos/of_tecnica force user = root force group = makimet

[planos] comment = Archivos CAD r14 path = /home/publicos/planos force user = root force group = makimet

[procedimientos] comment = Manuales de Procedimento path = /home/publicos/procedimientos force user = root force group = makimet

hope u can help me thanks

ok... finally I get to solve my problem. I just have to start from the begining modifying the defaoult smb.conf file and then readd every samba user by "smbpasswd -a " command. This is my smb.conf:

#////////////////////////////////////////////////////////smb.conf/////////////////////////////////////////////////////////////////////////

#======================= Global Settings =====================================

[global]

# ----------------------- Netwrok Related Options ------------------------- # # workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH # # server string is the equivalent of the NT Description field # # netbios name can be used to specify a server name not tied to the hostname # # Interfaces lets you configure Samba to use multiple interfaces # If you have multiple network interfaces then you can list the ones # you want to listen on (never omit localhost) # # Hosts Allow/Hosts Deny lets you restrict who can connect, and you can # specifiy it as a per share option as well # workgroup = MAKIMET server string = Servidor Makimet

netbios name = Servidor

interfaces = lo eth0 192.168.0.10/24 hosts allow = 127.0.0 192.168.0.

# --------------------------- Logging Options ----------------------------- # # Log File let you specify where to put logs and how to split them up. # # Max Log Size let you specify the max size log files should reach

# logs split per machine log file = /var/log/samba/%m.log # max 100KB per log file, then rotate max log size = 100

# ----------------------- Standalone Server Options ------------------------ # # Scurity can be set to user, share(deprecated) or server(deprecated) # # Backend to store user information in. New installations should # use either tdbsam or ldapsam. smbpasswd is available for backwards # compatibility. tdbsam requires no further configuration.

security = user passdb backend = tdbsam

# ----------------------- Domain Members Options ------------------------ # # Security must be set to domain or ads # # Use the realm option only with security = ads # Specifies the Active Directory realm the host is part of # # Backend to store user information in. New installations should # use either tdbsam or ldapsam. smbpasswd is available for backwards # compatibility. tdbsam requires no further configuration. # # Use password server option only with security = server or if you can't # use the DNS to locate Domain Controllers # The argument list may include: # password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name] # or to auto-locate the domain controller/s # password server = *

; security = domain ; passdb backend = tdbsam ; realm = MY_REALM

; password server = <NT-Server-Name>

# ----------------------- Domain Controller Options ------------------------ # # Security must be set to user for domain controllers # # Backend to store user information in. New installations should # use either tdbsam or ldapsam. smbpasswd is available for backwards # compatibility. tdbsam requires no further configuration. # # Domain Master specifies Samba to be the Domain Master Browser. This # allows Samba to collate browse lists between subnets. Don't use this # if you already have a Windows NT domain controller doing this job # # Domain Logons let Samba be a domain logon server for Windows workstations. # # Logon Scrpit let yuou specify a script to be run at login time on the client # You need to provide it in a share called NETLOGON # # Logon Path let you specify where user profiles are stored (UNC path) # # Various scripts can be used on a domain controller or stand-alone # machine to add or delete corresponding unix accounts # ; security = user ; passdb backend = tdbsam

; domain master = yes ; domain logons = yes

# the login script name depends on the machine name ; logon script = %m.bat # the login script name depends on the unix user used ; logon script = %u.bat ; logon path = \%L\Profiles%u # disables profiles support by specifing an empty path ; logon path =

; add user script = /usr/sbin/useradd "%u" -n -g users ; add group script = /usr/sbin/groupadd "%g" ; add machine script = /usr/sbin/useradd -n -c "Workstation (%u)" -M -d /nohome -s /bin/false "%u" ; delete user script = /usr/sbin/userdel "%u" ; delete user from group script = /usr/sbin/userdel "%u" "%g" ; delete group script = /usr/sbin/groupdel "%g"

# ----------------------- Browser Control Options ---------------------------- # # set local master to no if you don't want Samba to become a master # browser on your network. Otherwise the normal election rules apply # # OS Level determines the precedence of this server in master browser # elections. The default value should be reasonable # # Preferred Master causes Samba to force a local browser election on startup # and gives it a slightly higher chance of winning the election ; local master = no ; os level = 33 ; preferred master = yes

#----------------------------- Name Resolution ------------------------------- # Windows Internet Name Serving Support Section: # Note: Samba can be either a WINS Server, or a WINS Client, but NOT both # # - WINS Support: Tells the NMBD component of Samba to enable it's WINS Server # # - WINS Server: Tells the NMBD components of Samba to be a WINS Client # # - WINS Proxy: Tells Samba to answer name resolution queries on # behalf of a non WINS capable client, for this to work there must be # at least one WINS Server on the network. The default is NO. # # DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names # via DNS nslookups.

wins support = yes ; wins server = w.x.y.z wins proxy = yes

dns proxy = yes

# --------------------------- Printing Options ----------------------------- # # Load Printers let you load automatically the list of printers rather # than setting them up individually # # Cups Options let you pass the cups libs custom options, setting it to raw # for example will let you use drivers on your Windows clients # # Printcap Name let you specify an alternative printcap file # # You can choose a non default printing system using the Printing option

load printers = yes cups options = raw

; printcap name = /etc/printcap #obtain list of printers automatically on SystemV ; printcap name = lpstat ; printing = cups

# --------------------------- Filesystem Options --------------------------- # # The following options can be uncommented if the filesystem supports # Extended Attributes and they are enabled (usually by the mount option # user_xattr). Thess options will let the admin store the DOS attributes # in an EA and make samba not mess with the permission bits. # # Note: these options can also be set just per share, setting them in global # makes them the default for all shares

; map archive = no ; map hidden = no ; map read only = no ; map system = no ; store dos attributes = yes

# --------------------------------- Agregados ------------------------------ # # Opciones agregadas por adminstrador de sistema

preload = global administracion biblioteca cartas fax formatos fotografias informes instaladores memos of_tecnica planos procedimientos

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

[homes] comment = Home Directories for %S browseable = no writable = yes valid users = bodega,claidad,contador,dibujotec1,dibujotec2,faena,hcatalan,hfigueroa,personal,planning,produccion,root,secretaria,tvillagran,ymoya,ocastro,hsandoval,afigueroa,mahumada,chidalgo,informatica,@makimet force group = makimet ; valid users = MYDOMAIN%S

[printers] comment = All Printers path = /var/spool/samba browseable = no guest ok = no writable = no printable = yes

# Un-comment the following and create the netlogon directory for Domain Logons ; [netlogon] ; comment = Network Logon Service ; path = /var/lib/samba/netlogon ; guest ok = yes ; writable = no ; share modes = no

# Un-comment the following to provide a specific roving profile share # the default is to use the user's home directory ; [Profiles] ; path = /var/lib/samba/profiles ; browseable = no ; guest ok = yes

# A publicly accessible directory, but read only, except for people in # the "makimet" group

[administracion] path = /home/publicos/administracion comment = Archivos Administracion public = yes writable = yes printable = no write list = +makimet force group = makimet

[biblioteca] comment = Biblioteca Electronica path = /home/publicos/biblioteca public = yes writable = yes printable = no write list = +makimet force group = makimet

[cartas] comment = Cartas Enviadas path = /home/publicos/cartas public = yes writable = yes printable = no write list = +makimet force group = makimet

[fax] comment = Historico Fax path = /home/publicos/fax public = yes writable = yes printable = no write list = +makimet force group = makimet

[formatos] path = /home/publicos/formatos comment = Formatos Oficiales public = yes writable = yes printable = no write list = +makimet force group = makimet

[fotografias] comment = Historico Fotografias path = /home/publicos/fotografias public = yes writable = yes printable = no write list = +makimet force group = makimet

[informes] comment = Informes Tecnicos path = /home/publicos/informes public = yes writable = yes printable = no write list = +makimet force group = makimet

[instaladores] comment = Programas de Instalacion path = /home/publicos/instaladores public = yes writable = yes printable = no write list = +makimet force group = makimet

[memos] comment = Historico Memos path = /home/publicos/memos public = yes writable = yes printable = no write list = +makimet force group = makimet

[of_tecnica] path = /home/publicos/of_tecnica comment = Documentos Oficina Tecnica public = yes writable = yes printable = no write list = +makimet force group = makimet ;oplocks = no ;guest account = adm ;map archive = no ;delete readonly = yes ;locking = no ;force user = root ;case sensitive = no ;strict locking = no ;msdfs proxy = no

[planos] path = /home/publicos/planos comment = Archivos CAD r14 public = yes writable = yes printable = no force group = makimet read list = afigueroa,bodega,calidad,ccastro,contador,controldoc,cvaldivieso,dibujotec2,faena,hcatalan,hfigueroa,personal,planning,prevencion,produccion,secretaria,tvillagran,ymoya write list = dibujotec1,root

[procedimientos] comment = Manuales de Procedimento path = /home/publicos/procedimientos public = yes writable = yes printable = no write list = +makimet force group = makimet

/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

but now, I have a little problem, that I hop u can help me to find the correct parameter. In [planos] secction I get an error when an AutoCAD file is open and then i try to save it, it can't be done becouse the file is opened by another session. How can i lock it?

thanks

--