[Samba] SaMBa and Active Directory Functional Level
Hi all, We have an Active Directory domain with two Windows Server 2008 R2 domain controllers, but our domain functional level is still Windows Server 2003. We would like to raise the functional level to Windows Server 2008 R2, but due to the age of some of our SaMBa installations, I would like to know which is the earliest version of SaMBa which supported Active Directory at the Windows Server 2008 R2 functional level. Raising the functional level is irreversible, and one of the SaMBa installations is on a SUN (now Oracle) server running a version of SaMBa (3.6.8) which is unlikely to be upgraded anytime soon; so if it turns out to be incompatible, we will be in deep trouble. Thank you for your help. Yours, David del Campo -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Ruth Lobo del Olmo está ausente de la oficina.
Estaré ausente de la oficina desde el 27/05/2011 y no volveré hasta el 06/06/2011. Atentamente. ** IMPORTANT: The contents of this email and any attachments are confidential. They are intended for the named recipient(s) only. If you have received this email in error, please notify the system manager or the sender immediately and do not disclose the contents to anyone or make copies thereof. *** eSafe scanned this email for viruses, vandals, and malicious content. *** ** -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Problems with group assignments
Dear All, We finally managed to find out what was wrong: winbind was running! It seems that the SaMBa package we had from SUN/Oracle installed and started winbind (unlike in the old server and the Linux server). Once we disabled winbind (why did it think it was necessary to run winbind in the first place?), it all started working again: usernames and passwords are authenticated against AD, and group membership is checked against the local /etc/group file. Thank you all for your help. Yours, David del Campo PS: Maybe someone should amend the smb.conf man page to the effect that if you run winbind, the system will ignore the @, + and symbols under the (in)valid users and write list tags. -Original Message- From: samba-boun...@lists.samba.org [mailto:samba- boun...@lists.samba.org] On Behalf Of F. David del Campo Hill Sent: 23 May 2011 17:16 To: muel...@tropenklinik.de; samba@lists.samba.org Subject: Re: [Samba] Problems with group assignments Dear Daniel, The usernames and passwords are already authenticating against ADS; the problem is the groups. We want the groups to authenticate against the local UNIX groups, NOT ADS (like the original server did, and the documentation states); having the groups work through ADS will make us have to keep the local and ADS groups synchronized manually, which we do not want to do (the new server is also a NFS server, so we cannot have the two types of groups drift apart). David -Original Message- From: Daniel Müller [mailto:muel...@tropenklinik.de] Sent: 23 May 2011 07:52 To: F. David del Campo Hill; samba@lists.samba.org Subject: AW: [Samba] Problems with group assignments What about your ADS? You are authenticate against your ADS?! Why don't use winbind? http://wiki.samba.org/index.php/Samba__Active_Directory Good Luck Daniel --- EDV Daniel Müller Leitung EDV Tropenklinik Paul-Lechler-Krankenhaus Paul-Lechler-Str. 24 72076 Tübingen Tel.: 07071/206-463, Fax: 07071/206-499 eMail: muel...@tropenklinik.de Internet: www.tropenklinik.de --- -Ursprüngliche Nachricht- Von: samba-boun...@lists.samba.org [mailto:samba- boun...@lists.samba.org] Im Auftrag von F. David del Campo Hill Gesendet: Freitag, 20. Mai 2011 14:44 An: samba@lists.samba.org Betreff: [Samba] Problems with group assignments Dear All, We are trying to transfer a SaMBa installation from an old server to a newer more up-to-date one. The original server was sharing files to Windows XP systems in Active Directory (Windows Server 2003 R2 version), but as we move to Windows 7 and Active Directory (Windows Server 2008 R2 version) we need to upgrade the service. The old server was part of a NIS domain, with the valid users, write list, etc entries in its smb.conf referring to the NIS groups using the @ sign (which the documentation says it means is interpreted as an NIS netgroup first (if your system supports NIS), and then as a UNIX group if the name was not found in the NIS netgroup database; see http://samba.org/samba/docs/man/manpages- 3/smb.conf.5.html#INVALIDUSERS). It all worked fine as it picked users' group membership from NIS. The new server is a Solaris 10 box running SaMBa 3.5.5, and we are having problems with it picking up the group memberships. The old server's smb.conf was transplanted to the new server (with a few path changes), and the new server was successfully added to our Active Directory domain. As the new server is NOT a member of NIS, we made a copy of all the smb.conf-relevant groups to its local /etc/group and added all the users to the /etc/passwd file. With these changes we can access the shares using the AD usernames and passwords as long as they are not access-limited by valid users, so the integration of the server into AD is working. But if we add a valid users = @group line to the share in smb.conf, it will completely refuse access to all users, even the ones belonging to the group. Leaving the share accessible to all, but adding a write list = @group line to smb.conf, will allow access, but no one will be able to write to it, even the members of the group. If we chan ge the write list and valid users lines to list the usernames directly instead of through a group membership, it works. To avoid even attempting to talk to NIS, we changed the @ signs for +, but it still kept refusing to recognize group memberships (NIS or local UNIX ones). So it seems our new SaMBa is having problems recognizing group memberships. What am I doing wrong? Have SUN/Oracle done something to stop SaMBa accessing its local UNIX groups? Thank you for your help. Yours
Re: [Samba] Problems with group assignments
Dear Daniel, The usernames and passwords are already authenticating against ADS; the problem is the groups. We want the groups to authenticate against the local UNIX groups, NOT ADS (like the original server did, and the documentation states); having the groups work through ADS will make us have to keep the local and ADS groups synchronized manually, which we do not want to do (the new server is also a NFS server, so we cannot have the two types of groups drift apart). David -Original Message- From: Daniel Müller [mailto:muel...@tropenklinik.de] Sent: 23 May 2011 07:52 To: F. David del Campo Hill; samba@lists.samba.org Subject: AW: [Samba] Problems with group assignments What about your ADS? You are authenticate against your ADS?! Why don't use winbind? http://wiki.samba.org/index.php/Samba__Active_Directory Good Luck Daniel --- EDV Daniel Müller Leitung EDV Tropenklinik Paul-Lechler-Krankenhaus Paul-Lechler-Str. 24 72076 Tübingen Tel.: 07071/206-463, Fax: 07071/206-499 eMail: muel...@tropenklinik.de Internet: www.tropenklinik.de --- -Ursprüngliche Nachricht- Von: samba-boun...@lists.samba.org [mailto:samba- boun...@lists.samba.org] Im Auftrag von F. David del Campo Hill Gesendet: Freitag, 20. Mai 2011 14:44 An: samba@lists.samba.org Betreff: [Samba] Problems with group assignments Dear All, We are trying to transfer a SaMBa installation from an old server to a newer more up-to-date one. The original server was sharing files to Windows XP systems in Active Directory (Windows Server 2003 R2 version), but as we move to Windows 7 and Active Directory (Windows Server 2008 R2 version) we need to upgrade the service. The old server was part of a NIS domain, with the valid users, write list, etc entries in its smb.conf referring to the NIS groups using the @ sign (which the documentation says it means is interpreted as an NIS netgroup first (if your system supports NIS), and then as a UNIX group if the name was not found in the NIS netgroup database; see http://samba.org/samba/docs/man/manpages- 3/smb.conf.5.html#INVALIDUSERS). It all worked fine as it picked users' group membership from NIS. The new server is a Solaris 10 box running SaMBa 3.5.5, and we are having problems with it picking up the group memberships. The old server's smb.conf was transplanted to the new server (with a few path changes), and the new server was successfully added to our Active Directory domain. As the new server is NOT a member of NIS, we made a copy of all the smb.conf-relevant groups to its local /etc/group and added all the users to the /etc/passwd file. With these changes we can access the shares using the AD usernames and passwords as long as they are not access-limited by valid users, so the integration of the server into AD is working. But if we add a valid users = @group line to the share in smb.conf, it will completely refuse access to all users, even the ones belonging to the group. Leaving the share accessible to all, but adding a write list = @group line to smb.conf, will allow access, but no one will be able to write to it, even the members of the group. If we chan ge the write list and valid users lines to list the usernames directly instead of through a group membership, it works. To avoid even attempting to talk to NIS, we changed the @ signs for +, but it still kept refusing to recognize group memberships (NIS or local UNIX ones). So it seems our new SaMBa is having problems recognizing group memberships. What am I doing wrong? Have SUN/Oracle done something to stop SaMBa accessing its local UNIX groups? Thank you for your help. Yours, David del Campo -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Problems with group assignments
Dear All, We are trying to transfer a SaMBa installation from an old server to a newer more up-to-date one. The original server was sharing files to Windows XP systems in Active Directory (Windows Server 2003 R2 version), but as we move to Windows 7 and Active Directory (Windows Server 2008 R2 version) we need to upgrade the service. The old server was part of a NIS domain, with the valid users, write list, etc entries in its smb.conf referring to the NIS groups using the @ sign (which the documentation says it means is interpreted as an NIS netgroup first (if your system supports NIS), and then as a UNIX group if the name was not found in the NIS netgroup database; see http://samba.org/samba/docs/man/manpages-3/smb.conf.5.html#INVALIDUSERS). It all worked fine as it picked users' group membership from NIS. The new server is a Solaris 10 box running SaMBa 3.5.5, and we are having problems with it picking up the group memberships. The old server's smb.conf was transplanted to the new server (with a few path changes), and the new server was successfully added to our Active Directory domain. As the new server is NOT a member of NIS, we made a copy of all the smb.conf-relevant groups to its local /etc/group and added all the users to the /etc/passwd file. With these changes we can access the shares using the AD usernames and passwords as long as they are not access-limited by valid users, so the integration of the server into AD is working. But if we add a valid users = @group line to the share in smb.conf, it will completely refuse access to all users, even the ones belonging to the group. Leaving the share accessible to all, but adding a write list = @group line to smb.conf, will allow access, but no one will be able to write to it, even the members of the group. If we chan ge the write list and valid users lines to list the usernames directly instead of through a group membership, it works. To avoid even attempting to talk to NIS, we changed the @ signs for +, but it still kept refusing to recognize group memberships (NIS or local UNIX ones). So it seems our new SaMBa is having problems recognizing group memberships. What am I doing wrong? Have SUN/Oracle done something to stop SaMBa accessing its local UNIX groups? Thank you for your help. Yours, David del Campo -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Problems with group assignments
Dear Michal, The user authentication must be being handled by AD; the local accounts on the new server have been added to the /etc/passwd and /etc/shadow files, but the passwords in the /etc/shadow file are set to locked (which means that though the account exists and can own files, people cannot actually log in to the system; root can su to them though). As a result AD must be providing the authentication. The usernames in AD and the local files are the same. The /etc/nsswitch.conf file is as follows (comments removed): passwd: files group: files hosts: files dns ipnodes: files dns networks: files protocols: files rpc:files ethers: files netmasks: files bootparams: files publickey: files netgroup: files automount: files aliases:files services: files printers: user files auth_attr: files prof_attr: files project:files tnrhtp: files tnrhdb: files As you can see anything should be handled by the local files. The /etc/samba/smb.conf file is as follows (comments and private removed): [global] workgroup = removed server string = Samba Server on %h netbios name = removed security = ADS hosts allow = removed guest account = nobody log file = /var/samba/log/log.%m max log size = 500 password server = removed, removed realm = removed passdb backend= smbpasswd interfaces= removed local master = no os level = 33 domain master = no preferred master= no dns proxy = no [transit] comment = Temporary Backup for Windows 7 Upgrades path = removed browseable= no read only = yes valid users = user1, user2, user3, user4 # valid users = @group write list= users1, user2, user3, user4 # write list = +sysman As is, the share works, but as you can see I have to specify the usernames and cannot use +group or @group notation as I did on the old server. The old server was also part of the AD domain, so as far as I can see the only differences between the two setups is the SaMBa version and the fact the new server is not part of NIS; that is why I tried the +group notation, to no avail. I also have a Linux (Fedora 14) machine acting as a temporary SaMBa server (version 3.5.8); it is part of the NIS and AD domains and the @group assignments work fine from NIS. Thank you for your help. Yours, David -Original Message- From: Michal Belica [mailto:beli+...@beli.sk] Sent: 20 May 2011 14:46 To: F. David del Campo Hill Subject: Re: [Samba] Problems with group assignments Hi, - Original Message - From: F. David del Campo Hill delca...@stats.ox.ac.uk Sent: Friday, May 20, 2011 2:43:49 PM [...snip...] path changes), and the new server was successfully added to our Active Directory domain. As the new server is NOT a member of NIS, we made a copy of all the smb.conf-relevant groups to its local /etc/group and added all the users to the /etc/passwd file. With these changes we can access the shares using the AD usernames and passwords as long as they are not access-limited by valid users, so the integration of the server into AD is working. But if we add a valid users = @group line to the share in smb.conf, it will Are you using local or AD users and groups or are you mixing them? You say you have joined the server to AD and also added users and groups to /etc/passwd and /etc/group. But when a user connects to the Samba server from Win, (probably) his AD account is used, but in /etc/group, the members are the local users, which need not be the same (depends on more factors, like your NS switch settings for example). Try to check that you're using the AD/local users/groups consistently, or give more info related to this (e.g. from /etc/nsswitch.conf, /etc/smb.conf ...). -- Michal Belica - IT consultant beli+...@beli.sk | www.beli.sk -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Ruth Lobo del Olmo está ausente de la of icina.
Estaré ausente de la oficina desde el 26/02/2010 y no volveré hasta el 01/03/2010. Atentamente. ** IMPORTANT: The contents of this email and any attachments are confidential. They are intended for the named recipient(s) only. If you have received this email in error, please notify the system manager or the sender immediately and do not disclose the contents to anyone or make copies thereof. *** eSafe scanned this email for viruses, vandals, and malicious content. *** ** -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Logging application
How can I log which users open which files and which users copy files to flash drives, etc? -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] User permissions on other users home directory
Hello,
I have 5 users that need to be able to read and write from each others
home directorys. How I have done this is by creating a group office,
adding these 5 users to the office group, and then changing ownership
of users home directorys to user1:office
However, when user1 edits a file in his home directory, user2 can no
longer edit it, even though both users are in the office group.
My smb.conf:
[global]
## Browsing/Identification ###
# Change this to the workgroup/NT-domain name your Samba server will part of
workgroup = VENTURE
# server string is the equivalent of the NT Description field
server string = Server
# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
# wins support = no
# 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
; wins server = w.x.y.z
# 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
# 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 = yes
Debugging/Accounting
# This tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba/%m/%u.log
# Cap the size of the individual log files (in KiB).
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 = user
# You may wish to use password encryption. See the section on
# 'encrypt passwords' in the smb.conf(5) manpage before enabling.
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
# 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 = yes
# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan
ka...@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\s*\spassword:* %n\n
*Retype\snew\s*\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 = yes
# This option controls how unsuccessful authentication attempts are mapped
# to anonymous connections
# map to guest = bad user
## 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
admin users = adamdv angeladv
domain admin = adamdv
#
# 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 = \\server1\profiles\%U
# Another common choice is storing the profile in the user's home directory
# (this is Samba's default)
# 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 = \\server1\%U
# The following setting only takes effect if 'domain logons' is set
[Samba] Backup Server
Hello, I have a small issue. I am doing IT for a multi-user company, and cannot be there to support them 24/7 (I have to go to school, 13 sucks). We have 2 servers, one of them is just standing idle, one of them is acting as a PDC. I will be reinstalling the OS today, and would like to be able to do the following: -User logs in -User is working -PDC fails -User logs out -Selects to logon to second server -Keeps working until I can get the PDC back up again. The way I understand it, this cannot be accomplished with a BDC as a BDC relies on the operation of the PDC and is only used to take stress from the PDC. I was thinking of setting the second server up as a realm, and using rsync to sync the files between the 2 servers, or something like that. Suggestions would be great. Thanks, Adam -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Deploying apps via policy
Can I deploy software/applications through group or domain policy with samba? -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] DFS access
Hi all, This is my first message here, so pardon me if I break some etiquette. I have a Linux (Debian 4, kernel 2.6.18-4-686) SaMBa (3.0.24) server whose shares I want to mount on a Distributed File System running from a Windows Server 2003 R2. The share itself is accessible without problems as long as I try to get to it directly (\\smb\share), but if I try to browse through the DFS I get the \\DFS\share is not accessible. You might not have permission to use this network resource... Configuration information could not be read from the domain controller, either because the machine is unavailable, or access has been denied error message. The SaMBa server is part of the Active Directory domain. Also, a similar server with the same software and smb.conf file (different host and share names, of course) works with that same DFS without any problems whatsoever. Both servers are on the same side of the firewall and reside in the same Organizational Unit of Active Directory. The (sanitized) smb.conf file I use is: [global] workgroup= DOMAIN security = ADS netbios name = smb netbios aliases = smb realm= DOMAIN.UK encrypt passwords= yes password server = * server string= Samba shares for smb on %h bind interfaces only = yes hosts allow = *our IP range* interfaces = *smb IP* log file = /var/log/samba/log.%m log level= 1 passdb:2 auth:2 locking = yes lock directory = /var/log/samba/locks pid directory= /var/run private dir = /etc/samba/private username map = /etc/samba/username.map smb passwd file = /etc/samba/private/smbpasswd show add printer wizard = no utmp directory = /var/log encrypt passwords= yes domain master= no preferred master = no guest account= nobody max log size = 1000 syslog = 0 socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 invalid users= root admin local master = no dns proxy= no panic action = /usr/share/samba/panic-action %d [share] comment = Webservice Documents path = /data/sites/share printable= no browseable = no write list = @sysman valid users = @sysman force user = sysman force group = sysman The log file (sanitized) only reports: [2007/10/12 13:17:45, 0] smbd/map_username.c:map_username(107) can't open username map /etc/samba/username.map. Error No such file or directory [2007/10/12 13:17:45, 1] smbd/sesssetup.c:reply_spnego_kerberos(310) Username STATS\CLIENT$ is invalid on this system Both SaMBa servers have no username.map, and the CLIENT machine works with the other server. Where else should I look for differences between the two SaMBa servers? What is going on? Thank you for your help. David -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Internal error-Panic
Hi, We are running a samba server ( Version 3.0.10-1.4E.6.2 ) on a redHat RHEL release 4 (Nahant Update 3). We have a lot of errors that occurs when windowsXP clients hosts try to read from a Samba Export. We can't upgrade the Samba version because we are blocked by RHEL releases. This is the log returned by the smb server : [2006/09/22 13:53:22, 0] lib/fault.c:fault_report(36) === [2006/09/22 13:53:22, 0] lib/fault.c:fault_report(37) INTERNAL ERROR: Signal 7 in pid 22609 (3.0.10-1.4E.6.2) Please read the appendix Bugs of the Samba HOWTO collection [2006/09/22 13:53:22, 0] lib/fault.c:fault_report(39) === [2006/09/22 13:53:22, 0] lib/util.c:smb_panic2(1504) PANIC: internal error [2006/09/22 13:53:22, 0] lib/util.c:smb_panic2(1512) BACKTRACE: 16 stack frames: #0 smbd(smb_panic2+0x8a) [0xe44260] #1 smbd(smb_panic+0x19) [0xe4448c] #2 smbd [0xe30bff] #3 /lib/tls/libc.so.6 [0x6858e8] #4 smbd [0xe57d0d] #5 smbd [0xe582fe] #6 smbd(tdb_store+0x137) [0xe59426] #7 smbd(set_share_mode+0x1d3) [0xe00f09] #8 smbd(open_file_shared1+0xde2) [0xd1be6d] #9 smbd(reply_ntcreate_and_X+0x88f) [0xceefa8] #10 smbd [0xd2d4c2] #11 smbd(process_smb+0x19b) [0xd2d8fc] #12 smbd(smbd_process+0x15f) [0xd2e624] #13 smbd(main+0x875) [0xec0b37] #14 /lib/tls/libc.so.6(__libc_start_main+0xd3) [0x672e23] #15 smbd [0xccd231] thanks for helping me to undestand what occurs and what these logs means. Jonathan -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] closewait socket state
I have a probleme with my samba server. I have a lot of closewait socket state causing the load average to increase. Samba generate some errors logs but I don't know the signification of Signal 7 in pid xxx. For information, I am running a samba 3.0.10-1.4E.2 under a kernel Linux version 2.6.9-22 with a RHEL 3.4.4-2. Here is the log file (/var/log/messages) : -- Jul 11 13:56:33 linuxd smbd[8481]: yield_connection: tdb_delete for name J failed with error Record does not exist. Jul 11 13:56:33 linuxd smbd[27341]: [2006/07/11 13:56:33, 0] lib/util_sock.c:write_socket_data(430) Jul 11 13:56:33 linuxd smbd[19620]: [2006/07/11 13:56:33, 0] smbd/connection.c:yield_connection(76) Jul 11 13:56:33 linuxd smbd[27341]: write_socket_data: write failure. Error = Broken pipe Jul 11 13:56:33 linuxd smbd[8408]: [2006/07/11 13:56:33, 0] lib/util_sock.c:write_socket_data(430) Jul 11 13:56:33 linuxd smbd[27341]: [2006/07/11 13:56:33, 0] smbd/connection.c:yield_connection(76) Jul 11 13:56:33 linuxd smbd[8489]: [2006/07/11 13:56:33, 0] smbd/connection.c:yield_connection(76) [...] 1 13:56:33 linuxd smbd[17231]: write_socket_data: write failure. Error = Broken pipe Jul 11 13:56:33 linuxd smbd[16632]: write_socket_data: write failure. Error = Broken pipe Jul 11 13:56:33 linuxd smbd[8410]: write_socket_data: write failure. Error = Broken pipe Jul 11 13:56:33 linuxd smbd[2542]: oplock_break: end of file from client Jul 11 13:56:33 linuxd smbd[13744]: write_socket_data: write failure. Error = Broken pipe Jul 11 13:56:33 linuxd smbd[27841]: write_socket_data: write failure. Error = Connection reset by peer Jul 11 13:56:33 linuxd smbd[8484]: write_socket_data: write failure. Error = Broken pipe [...] ul 11 13:56:37 linuxd smbd[9455]: Error writing 134 bytes to client. -1. (Broken pipe) Jul 11 13:56:37 linuxd smbd[8980]: Error writing 58 bytes to client. -1. (Broken pipe) Jul 11 13:56:37 linuxd smbd[8963]: Error writing 58 bytes to client. -1. (Broken pipe) Jul 11 13:56:37 linuxd smbd[14781]: [2006/07/11 13:56:37, 0] lib/fault.c:fault_report(39) Jul 11 13:56:37 linuxd smbd[10470]: Error writing 58 bytes to client. -1. (Broken pipe) Jul 11 13:56:37 linuxd smbd[8706]: Error writing 134 bytes to client. -1. (Broken pipe) Jul 11 13:56:37 linuxd smbd[9066]: Error writing 134 bytes to client. -1. (Broken pipe) Jul 11 13:56:37 linuxd smbd[9450]: Error writing 134 bytes to client. -1. (Broken pipe) Jul 11 13:56:37 linuxd smbd[8715]: Error writing 134 bytes to client. -1. (Broken pipe) [...] Jul 11 13:56:37 linuxd smbd[14781]: BACKTRACE: 16 stack frames: Jul 11 13:56:37 linuxd smbd[9074]: BACKTRACE: 20 stack frames: Jul 11 13:56:37 linuxd smbd[16632]: yield_connection: tdb_delete for name H failed with error Record does not exist. Jul 11 13:56:37 linuxd smbd[14781]:#0 smbd(smb_panic2+0x8a) [0xe9fe90] Jul 11 13:56:37 linuxd smbd[9074]:#0 smbd(smb_panic2+0x8a) [0xe9fe90] Jul 11 13:56:37 linuxd smbd[14781]:#1 smbd(smb_panic+0x19) [0xea00bc] Jul 11 13:56:37 linuxd smbd[9074]:#1 smbd(smb_panic+0x19) [0xea00bc] Jul 11 13:56:37 linuxd smbd[14781]:#2 smbd [0xe8c80f] Jul 11 13:56:37 linuxd smbd[9074]:#2 smbd [0xe8c80f] Jul 11 13:56:37 linuxd smbd[14781]:#3 /lib/tls/libc.so.6 [0x3f38c8] Jul 11 13:56:37 linuxd smbd[9074]:#3 /lib/tls/libc.so.6 [0x3f38c8] Jul 11 13:56:37 linuxd smbd[14781]:#4 smbd [0xeb393d] Jul 11 13:56:37 linuxd smbd[9074]:#4 smbd [0xeb393d] Jul 11 13:56:37 linuxd smbd[14781]:#5 smbd [0xeb3f2e] Jul 11 13:56:37 linuxd smbd[9074]:#5 smbd [0xeb3f2e] Jul 11 13:56:37 linuxd smbd[14781]:#6 smbd(tdb_store+0x137) [0xeb5056] Jul 11 13:56:37 linuxd smbd[9074]:#6 smbd(tdb_store+0x137) [0xeb5056] Jul 11 13:56:37 linuxd smbd[14781]:#7 smbd(set_share_mode+0x1d3) [0xe5cd19] Jul 11 13:56:37 linuxd smbd[9074]:#7 smbd(claim_connection+0x252) [0xd35b16] Jul 11 13:56:37 linuxd smbd[14781]:#8 smbd(open_file_shared1+0xde2) [0xd77dfd] Jul 11 13:56:37 linuxd smbd[9074]:#8 smbd [0xd8b539] Jul 11 13:56:37 linuxd smbd[14781]:#9 smbd(reply_ntcreate_and_X+0x88f) [0xd4af38] Jul 11 13:56:37 linuxd smbd[9074]:#9 smbd(make_connection+0x162) [0xd8ca54] Jul 11 13:56:37 linuxd smbd[14781]:#10 smbd [0xd89412] Jul 11 13:56:37 linuxd smbd[9074]:#10 smbd(reply_tcon_and_X+0x1d3) [0xd52bb6] Jul 11 13:56:37 linuxd smbd[14781]:#11 smbd(process_smb+0x19b) [0xd8984c] Jul 11 13:56:37 linuxd smbd[9074]:#11 smbd [0xd89412] Jul 11 13:56:37 linuxd smbd[14781]:#12 smbd(smbd_process+0x15f) [0xd8a574] Jul 11 13:56:37 linuxd smbd[9074]:#12 smbd(chain_reply+0x178) [0xd89cb8] Jul 11 13:56:37 linuxd smbd[14781]:#13 smbd(main+0x865) [0xf1c567] Jul 11 13:56:37 linuxd smbd[9074]:#13 smbd(reply_sesssetup_and_X+0xabe) [0xd62feb] Jul 11 13:56:37 linuxd smbd[14781]:#14 /lib/tls/libc.so.6(__libc_start_main+0xd3) [0x3e0e23] Jul 11 13:56:37 linuxd smbd[9074]:#14 smbd [0xd89412] Jul 11 13:56:37 linuxd smbd[14781]:#15 smbd
[Samba] unknown UDP message
Hi, I have some serious problem with my Samba server in production environment. For information, I am running a samba 3.0.10-1.4E.2 under a kernel Linux version 2.6.9-22 with a RHEL 3.4.4-2. The problem is that I noticed in the log files the following errors : smbd[25842]: [2006/06/14 11:25:07, 0] smbd/oplock.c:request_oplock_break(1055) smbd[25842]: request_oplock_break: no response received to oplock break request to pid 25225 on port 33355 for dev = 16, inode = 4720682, file_id = 2 Next ... 3 hours later another error appear : smbd[25842]: process_local_message: unknown UDP message command code (8003) - ignoring. smbd[25842]: [2006/06/14 15:00:40, 0] smbd/oplock.c:process_local_message(441) And this last one occured more than 200 times per seconds during 4 seconds and pull the CPU to 100 percent, with a smbd process at 99% : 25842 nobody25 0 12864 3740 3112 R 99.7 0.1 10053:47 smbd By the way, since this time samba connections seems anormaly slow ... So does anyone know something about this problem ? Is there a way to avoid this ? thanks -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Samba on NAS perfs
Hi, I am running a samba 3.0.14a server on a 2.6.15.6 kernel, on a 4T - SATA2 NAS. The disks are formated in xfs and configurated in hard RAID5. Network is bonded with 2 Gbits links using 802.3ad agregation. The NAS is connected on a Gbits switch (Summit 400 - extreme Networks), also configured with dynamic sharing. I am trying to get the best performances in Reading/writting the NAS, and what I am obtaining is very poor ... I have been trying many kind of tests with several clients (win XP console, win XP gui, MACOSX, many linux ...). The fact is first I can't get the first NAS interface overloaded, it never get the turn to the second one. I have very poor transfer rates : -copy to windows from a NAS Samba export : max 20 MBytes/s with many kind of file sizes -copy to Linux (on firewire 800) from a NAS Samba export : max 12 MBytes/s with many kind of file sizes The linux mount is made using CIFS drivers. on the other side, writting on the NAS give me the same results. I have also made some tests with the IOMeter tool on a winXP samba mount, configure with a transfert request size of 32MB, 100% reading, full sequential access. With 4 workers on the same client I get (according to snmp results) a rate of 80 MBytes/s ! PS : Directly on the NAS, using the tool Bonnie++ (not using samba...) we get a pretty 150 MBytes/s with the writting tests. PS2 : We have made theses tests with samba,nfs and Afp exports The clients configurations are the following : - linux clients : Bi-Proc 1Ghz - 1 GB RAM Disks Firewire 800 GbE network - Avid HP WinXP Bi-Proc 3Ghz 2GB RAM 6 SCSI RAID0 drives GbE network Thanks for helping me to understand why we can't get better perfs ? john -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] net rpc vampire not working
I actually fooled with your LdapImport and didn't get it to work straight away and for the most part, I didn't have much of an issue with conversion from openldap slapcat output. Yeah, I haven't had enough different systems to test LdapImport on thoroughly. It works for me in most places but it's definitely best at doing LDAP - LDAP not so much at anything else - LDAP. But I'm slowly hacking away at the various bugs and things, trying to make it more useable. Any bug reports are appreciated of course, as other people have systems they can test on that I can't. I also see the need to use groupOfUniqueNames but I haven't figured that one out either but I'm working on it. groupOfUniqueNames is a nice idea and very neat but in the end the IETF RFC standards maintainers didn't go with it. So the very few systems that support it are likely to end up being orphaned in doing so. The only reason I made any use of it at all is because (a) directory administrator handles it, and (b) it works on Linux using the PADL software and (c) it's interesting. There is no real compelling reason to do it other than that it's interesting. I could make better use of my time by writing some useful code. -- Del -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] net rpc vampire not working
Hi, Can someone help me get net rpc vampire in one of its forms working. The objective is to migrate from an NT4 PDC to a SAMBA 3.0 PDC using LDAP as a back end. I am trying to migrate the user and machine accounts across in a lab environment, separate from the main network (I have replicated the PDC to do this). I have samba-3.0.20b built from the samba team source RPM on Fedora Core 3, and I'm trying to follow the steps here: http://us3.samba.org/samba/docs/man/Samba-HOWTO-Collection/NT4Migration.html also here: http://samba.idealx.org/smbldap-howto.en.html (section 11.1) I have seen the problems listed here: http://lists.samba.org/archive/samba/2004-June/088448.html http://lists.samba.org/archive/samba/2004-July/089147.html and I'm getting the same thing happening to me. I have also tried using net rpc vampire ldif with similar results: I started by creating a samba server and setting it up as a BDC: [global] workgroup = MYDOMAIN netbios name = MYSAMBASERVER server string = Samba Server security = domain encrypt passwords = Yes password server = MYPDC log file = /var/log/samba/%m.log max log size = 0 name resolve order = host wins bcast socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 local master = No domain master = False dns proxy = No wins server = 192.168.1.1 winbind uid = 1-2 winbind gid = 1-2 winbind separator = + create mask = 0777 directory mask = 0777 hosts allow = 192.168. 127. printing = lprng oplocks = No follow symlinks = No idmap uid = 16777216-33554431 idmap gid = 16777216-33554431 template shell = /bin/false winbind use default domain = no Then I added the following parts to smb.conf to give it the LDAP information: ldap suffix = dc=debortoli,dc=local ldap user suffix = ou=People ldap machine suffix = ou=Computers ldap group suffix = ou=Groups Join the domain: net rpc join -U Administrator%PASSWORD service smb start I can verify the domain is joined by using: net rpc testjoin Also, I can see all of the accounts using winbind: service winbind start getent passwd However from this point on nothing in net rpc vampire works. net rpc vampire ldif ./vampire.ldif fails with: Could not retrieve domain trust secret net rpc vampire ldif ./vampire.ldif -S MYPDC -U Administrator%PASSWORD fails with: Cannot import users from DBW at this time, as the current domain: FC3-DBW-3: S-1-5-21-92691229-39247329-4222772032 conflicts with the remote domain DBW: S-1-5-21-423981254-716712060-315576832 This is a suggested fix: * http://lists.samba.org/archive/samba/2004-July/089148.html but it fails like this: # net setlocalsid S-1-5-21-423981254-716712060-315576832 # net rpc vampire ldif Cannot import users from FC3-DBW-3 at this time, as the current domain: FC3-DBW-3: S-1-5-21-423981254-716712060-315576832 conflicts with the remote domain FC3-DBW-3: S-1-5-21-92691229-39247329-4222772032 Alternatively, running this: net rpc vampire ldif ./vampire.ldif -S MYPDC -U Administrator%PASSWORD ... results in an empty ./vampire.ldif file, and two files /tmp/add.ldif and /tmp/mod.ldif. /tmp/mod.ldif is empty and /tmp/add.ldif contains the base LDAP structure but no users other than root and nobody. I have tried the http://samba.idealx.org/smbldap-howto.en.html method (making samba a PDC, stopping the other PDC, restarting samba, etc) but that fails as well with just about the same error messages as above. Is there any way of getting this net rpc vampire tool to work? Has anyone had any success with it? What entries do I need in smb.conf etc to get things working? -- Del -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] net rpc vampire not working
Use http://www.samba.org/samba/docs/man/Samba-Guide/ntmigration.html Thanks, that is a great help. I have it working now. I would recommend that the user is familiar with setup, usage, maintenance of LDAP prior to doing this. Oh, LDAP is no problem. I'm the author of the LdapImport scripts which some of you may have seen http://wiki.babel.com.au/index.php?area=Linux_Projectspage=LdapImport The problem I was having was correct configuration of samba prior to running net rpc vampire. Just some notes on the migration guide above that you might want to incorporate into a later edition: -- example 9.1: security = user is missing? Is this intentional? the configure.pl script from smbldap-tools adds it to smb.conf in any case. May be useful to mention extending the LDAP schema before attempting any of this, e.g. with the samba.schema file. Before Step 7: You can't run ./configure.pl in the smbldap-tools directory unless samba is running. So you need to do service smb start or your OS equivalent first. In fact, before doing that you need to inform samba of your LDAP bind DN password using: smbpasswd -w password Step 8: Since you need to start samba before you run ./configure.pl, and since samba tries to connect to the LDAP server when it starts, you will need to start LDAP before you start samba. So this probably belongs around step 4 or 5. Step 10: You need to do this before starting Samba, so again this needs to happen earlier than step 7. Step 11: Also, starting Samba will attempt to populate the LDAP directory. On Fedora Directory Server (and in fact any non-OpenLDAP server) you may hit troubles doing this because the entries aren't formatted correctly with the top objectClass (on OpenLDAP this parent object class is added automatically). To fix this, what I did was: cd /opt/IDEALX/sbin ./smbldap-populate -e /root/LDAP/smb-populate.ldif vi /root/LDAP/smb-populate.ldif Change the last LDIF entry in this file to include objectClass: top ldapadd -x -c -D 'cn=Directory Manager' -W -f /root/LDAP/smb-populate.ldif ... and you will need to supply your root DN password to the above command. Step 12: This should not actually be necessary on non-OpenLDAP servers. A running LDAP server will notice that its directory has been populated. It is, however, the case that the OpenLDAP directory is completely empty after installation so you may need to do this. Step 14: It might be useful to test this using: net rpc testjoin Step 17: This seems to take a long time. Expect that -- nothing happens in the log file for a few seconds at least, don't panic. -- Del -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] samba-3.0.0 to samba-3.0.10 upgrade
Hello, we got installed a Samba 3.0.0 version in our production servers compiled with enabled-shared with-fhs with-ldap with-ads with-quotas with-acl-support options, we use an ldap server to validate our users and give permissions to be able to use certain shares, got an nscd server enables to caches ldap searchesHello, we got installed a Samba 3.0.0 version in our production servers compiled with enabled-shared with-fhs with-ldap with-ads with-quotas with-acl-support options, we use an ldap server to validate our users and give permissions to be able to use certain shares, got an nscd server enables to caches ldap searches. At this time we need to upgrade to the latest stable version or at least the version used in CentOs 4, Samba-3.0.10-1.4E, so we read the changelogs in the samba site and didnt find anything that can give us troubles so we think everything is compatible, before change the version or makes tests, does anybody know if theres anything we got to know about samba changes or incompatibilities??? TIA. Nati. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Fw: [Samba] problems with username map
Begin forwarded message: Date: Thu, 13 Jan 2005 13:29:52 + From: HeRnAn DeL bOcA [EMAIL PROTECTED] To: samba@lists.samba.org Subject: [Samba] problems with username map if someone knows anything about this problem??? with samba 2.2.7 i've used a username map called smbusers file with this structure user_domain =[EMAIL PROTECTED] user2_domain = [EMAIL PROTECTED] and so on. obviosuly in the smb.conf the option is enable username map = /etc/samba/smbusers and it worked just fine but now i upgraded samba to 3.0 and the option username map is not working is there any solution??? thanks to anybody that can help me Hernan -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] problems with username map
if someone knows anything about this problem??? with samba 2.2.7 i've used a username map called smbusers file with this structure user_domain =[EMAIL PROTECTED] user2_domain = [EMAIL PROTECTED] and so on. obviosuly in the smb.conf the option is enable username map = /etc/samba/smbusers and it worked just fine but now i upgraded samba to 3.0 and the option username map is not working is there any solution??? thanks to anybody that can help me Hernan -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Printer name includes IP address instead of server name
We made some changes to one of our Samba servers that until recently has been primarily a print server. We added PDC with LDAP authentication to it. Somewhere along the way, a different kind of behavior appeared. When users add a printer to their windows machines it now appears as PrinterName on xxx.xxx.xxx.xxx instead of PrinterName on ServerName. Has anyone seen this behavior before? Any ideas on how I might fix it? Samba version 3.0.7 running on Fedora Core 1 Config info follows: [global] netbios name = TITAN dos charset = 850 unix charset = ISO8859-1 workgroup = AGNET server string = ASGC Domain Controller/Print Server map to guest = Bad User obey pam restrictions = Yes passdb backend = ldapsam:ldap://LDAP Server Name username map = /etc/samba/smbusers syslog = 0 log file = /var/log/samba/%m.log max log size = 10 name resolve order = wins lmhosts bcast time server = Yes socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 add user script = /usr/local/sbin/smbldap-useradd -m %u add group script = /usr/local/sbin/smbldap-groupadd -p %g add user to group script = /usr/local/sbin/smbldap-groupmod -m %u %g delete user from group script = /usr/local/sbin/smbldap-groupmod -x %u %g set primary group script = /usr/local/sbin/smbldap-usermod -g %g %u add machine script = /usr/local/sbin/smbldap-useradd -w %u logon script = startup.bat logon path = logon drive = c: logon home = domain logons = Yes os level = 65 preferred master = Yes domain master = Yes wins support = Yes ldap admin dn = LDAP DN Value ldap delete dn = Yes ldap filter = ((uid=%u)(objectclass=posixAccount)) ldap group suffix = ou=Groups ldap idmap suffix = ou=Idmap ldap machine suffix = ou=Computers ldap passwd sync = Yes ldap suffix = o=AlphaGraphics ldap ssl = start tls ldap user suffix = ou=agcorp cups options = raw [printers] comment = All Printers path = /var/spool/samba printer admin = @admins, root guest ok = Yes printable = Yes browseable = No [print$] comment = Printer Driver Download Area path = /var/samba/drivers write list = @admins force group = admins force create mode = 0664 force directory mode = 0775 guest ok = Yes browseable = No -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] hidding mapped drives with samba
Hi everybody is there a way to hide the mapped drives on a samba server even for the client users who has access to it.??? -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] 2 Samba server
On Fri, 30 Jul 2004 10:31:17 -0400 Varjao, Marcio [EMAIL PROTECTED] wrote: Hi, If I run 2 Samba server on 2 diferent Domains but on the same IP Class Will I have problems you shouldn't have any problem. having two samba server on different domains has nothing to do with th e ip class -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Word 2002 Samba problem
Strange problem with Samba (2.2.8) and Word 2002. When trying to open a word document on a Samba share from a Windows 98 workstation, Word hangs and never opens the file. User has full access to the share and can copy the file to the local computer in Explorer and then open the file in Word from the local drive. Then they can copy it back to the server. This is what they've been doing as a workaround. Users who are running Windows XP and Word 2002 do not have this problem. They can access the files directly from the Samba server without issue. The wrench in the works is that this network also has a Netware 4 file server and all the clients have both MS and Netware client software loaded. Now, a bit about my configuration: Samba 2.2.8. WINS support enabled. NOT PDC, just workgroup mode (cause the netware is their primary fileserver and only certain users need access the Samba box) TCP/IP is used for Samba fileserver, not IPX. Any thoughts? ~ At night I dream of a world where Windows doesn't suck. ~ -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] I: smbtar
I try again. I hope to find more person in office. Please can you help me? Thanks a lot Stefano -Messaggio originale- Da: Stefano Del Negro [mailto:[EMAIL PROTECTED] Inviato: giovedì 31 luglio 2003 12.05 A: [EMAIL PROTECTED] Oggetto: smbtar dear smb's experts, I have a trouble with smbtar. I'll try to explain it simply. (I read SAMBA docs and looked for informations on the web, but i didn't found the answer...) I have a IBM X220 + RedHat 7.2. One of the activity assigned to this server is to backup users' directory with smbtar. The problem I have is with PC that run WIN2000 (NTFS). The version of samba is: smbd -V output: Version 2.2.1a nmbd -V output: Version 2.2.1a When i run smbtar on PC with WIN2000-NTFS, if users have directory or files with special characters, like caffè , colibrì etc., I see the following error (data are not saved): smbtar -s pc-stefano -x procaffe -u user -p password -t /home/profiles/m.levis/prova.tar -v serveris pc-stefano share is procaffe\\ tar args is tape is /home/profiles/m.levis/prova.tar blocksize is added interface ip=192.168.1.135 bcast=192.168.1.255 nmask=255.255.255.0 tarmode is now full, system, hidden, noreset, verbose Got a positive name query response from 192.168.1.123 ( 192.168.1.123 ) Domain=[EDP] OS=[Windows 5.0] Server=[Windows 2000 LAN Manager] 51200 ( 684.9 kb/s) \attivita_edp.doc ERRDOS - ERRbadfile (File not found.) opening remote file \Conti ricavì.doc (\) tar: dumped 1 files and directories Total bytes written: 51712 with other clients using WIN95/98 I have no problems. Thanks for your help Stefano -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
R: [Samba] smbtar
Please, can you help me? I'm tryng again... I'll probably give up and use MS Backup from Win2000 to SMB shares instead of using smbtar. I hope somebody will tell me what to do. -Messaggio originale- Da: Mark Cooke [mailto:[EMAIL PROTECTED] Inviato: gioved 31 luglio 2003 12.14 A: Stefano Del Negro Oggetto: Re: [Samba] smbtar Samba not liking the accented 'i' character ? Just a guess, Warning - don't try the 3.0beta3, smbtar is totally broken. Mark On Thu, 2003-07-31 at 11:05, Stefano Del Negro wrote: dear smb's experts, I have a trouble with smbtar. I'll try to explain it simply. (I read SAMBA docs and looked for informations on the web, but i didn't found the answer...) I have a IBM X220 + RedHat 7.2. One of the activity assigned to this server is to backup users' directory with smbtar. The problem I have is with PC that run WIN2000 (NTFS). When i run smbtar on PC with WIN2000-NTFS, if users have directory or files with special characters, like caff , colibr etc., I see the following error (data are not saved): smbtar -s pc-stefano -x procaffe -u user -p password -t /home/profiles/m.levis/prova.tar -v serveris pc-stefano share is procaffe\\ tar args is tape is /home/profiles/m.levis/prova.tar blocksize is added interface ip=192.168.1.135 bcast=192.168.1.255 nmask=255.255.255.0 tarmode is now full, system, hidden, noreset, verbose Got a positive name query response from 192.168.1.123 ( 192.168.1.123 ) Domain=[EDP] OS=[Windows 5.0] Server=[Windows 2000 LAN Manager] 51200 ( 684.9 kb/s) \attivita_edp.doc ERRDOS - ERRbadfile (File not found.) opening remote file \Conti ricav.doc (\) tar: dumped 1 files and directories Total bytes written: 51712 with other clients using WIN95/98 I have no problems. Thanks for your help Stefano -- Mark Cooke [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] smbtar
dear smb's experts, I have a trouble with smbtar. I'll try to explain it simply. (I read SAMBA docs and looked for informations on the web, but i didn't found the answer...) I have a IBM X220 + RedHat 7.2. One of the activity assigned to this server is to backup users' directory with smbtar. The problem I have is with PC that run WIN2000 (NTFS). When i run smbtar on PC with WIN2000-NTFS, if users have directory or files with special characters, like caffè , colibrì etc., I see the following error (data are not saved): smbtar -s pc-stefano -x procaffe -u user -p password -t /home/profiles/m.levis/prova.tar -v serveris pc-stefano share is procaffe\\ tar args is tape is /home/profiles/m.levis/prova.tar blocksize is added interface ip=192.168.1.135 bcast=192.168.1.255 nmask=255.255.255.0 tarmode is now full, system, hidden, noreset, verbose Got a positive name query response from 192.168.1.123 ( 192.168.1.123 ) Domain=[EDP] OS=[Windows 5.0] Server=[Windows 2000 LAN Manager] 51200 ( 684.9 kb/s) \attivita_edp.doc ERRDOS - ERRbadfile (File not found.) opening remote file \Conti ricavì.doc (\) tar: dumped 1 files and directories Total bytes written: 51712 with other clients using WIN95/98 I have no problems. Thanks for your help Stefano -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
R: [Samba] smbtar
Actually I'm using the following versions: smbd -V output: Version 2.2.1a nmbd -V output: Version 2.2.1a Stefano -Messaggio originale- Da: Mark Cooke [mailto:[EMAIL PROTECTED] Inviato: gioved 31 luglio 2003 12.14 A: Stefano Del Negro Oggetto: Re: [Samba] smbtar Samba not liking the accented 'i' character ? Just a guess, Warning - don't try the 3.0beta3, smbtar is totally broken. Mark On Thu, 2003-07-31 at 11:05, Stefano Del Negro wrote: dear smb's experts, I have a trouble with smbtar. I'll try to explain it simply. (I read SAMBA docs and looked for informations on the web, but i didn't found the answer...) I have a IBM X220 + RedHat 7.2. One of the activity assigned to this server is to backup users' directory with smbtar. The problem I have is with PC that run WIN2000 (NTFS). When i run smbtar on PC with WIN2000-NTFS, if users have directory or files with special characters, like caff , colibr etc., I see the following error (data are not saved): smbtar -s pc-stefano -x procaffe -u user -p password -t /home/profiles/m.levis/prova.tar -v serveris pc-stefano share is procaffe\\ tar args is tape is /home/profiles/m.levis/prova.tar blocksize is added interface ip=192.168.1.135 bcast=192.168.1.255 nmask=255.255.255.0 tarmode is now full, system, hidden, noreset, verbose Got a positive name query response from 192.168.1.123 ( 192.168.1.123 ) Domain=[EDP] OS=[Windows 5.0] Server=[Windows 2000 LAN Manager] 51200 ( 684.9 kb/s) \attivita_edp.doc ERRDOS - ERRbadfile (File not found.) opening remote file \Conti ricav.doc (\) tar: dumped 1 files and directories Total bytes written: 51712 with other clients using WIN95/98 I have no problems. Thanks for your help Stefano -- Mark Cooke [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] clarion 1.28 on samba
Hi, im trying to use a database made on clarion under linux/samba but im getting an error on a .dat file the error says can't share /sistema/expedien.dat can anyone help me? thank you very much -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Two winbinds in one machine?
Why don't you use 2 different Linux boxes each one acting as a domain controller? In fact, the box is a domain member, not a domain controller (that's why I use winbind, for fetching accounts and allowing access to the box shares). Anyway, I found a workaround, pretty nasty though: as I am migrating from one domain to another, and the situation is temporary, I pasted the results from one winbind (with wbinfo) in /etc/passwd and /etc/group, shut down this winbind, started the other one, and, in combination, I have accounts from both domains up and running (as seen by 'getent passwd' and 'getent group'). And when migration is done, I'll delete the added entries and rely on winbind. Anyway, I think it would be great if there were a way to make nsswitch.conf work with more than one winbind simultaneously... Yours, Fernando del Valle -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Fernando del Valle Sent: 25 iunie 2003 19:22 To: [EMAIL PROTECTED] Subject: [Samba] Two winbinds in one machine? Hi, I'm switching between two domains, and I need to make a couple of Linux+Samba machines provide the same shares in both domains. I've set up two sambas in the same machine, listening on different subinterfaces, but I can't make winbind to behave properly. As soon as I start the second winbind, the domain accounts provided by the first one become hidden (that is, 'getent passwd' only shows the second domain). I found both winbinds use the same UNIX socket/pipe. I found no way to choose the socket used, or to make winbind share the socket, neither in the configure script nor in the daemon options. Does anyone know how to work around this? I use samba 2.2.3. Why don't you use 2 different Linux boxes each one acting as a domain controller? -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Two winbinds in one machine?
Hi, I'm switching between two domains, and I need to make a couple of Linux+Samba machines provide the same shares in both domains. I've set up two sambas in the same machine, listening on different subinterfaces, but I can't make winbind to behave properly. As soon as I start the second winbind, the domain accounts provided by the first one become hidden (that is, 'getent passwd' only shows the second domain). I found both winbinds use the same UNIX socket/pipe. I found no way to choose the socket used, or to make winbind share the socket, neither in the configure script nor in the daemon options. Does anyone know how to work around this? I use samba 2.2.3. netstat -nap | grep winbindd shows this (.200 and .209 are the PDCs): tcp0 0 192.168.0.242:32918 192.168.0.200:445 ESTABLISHED 24619/winbindd tcp0 0 192.168.0.242:32917 192.168.0.200:445 ESTABLISHED 24619/winbindd tcp0 0 192.168.0.242:32925 192.168.0.209:445 ESTABLISHED 24905/winbindd unix 2 [ ACC ] STREAM LISTENING 114109 24619/winbindd /tmp/.winbindd/pipe unix 2 [ ACC ] STREAM LISTENING 120740 24905/winbindd /tmp/.winbindd/pipe Yours, Fernando del Valle -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
quota group
=get_smb_linux_gen_quota(mnt-mnt_fsname, euser_id, D, 'u');
if (r == -1) {
- r=get_smb_linux_v2_quota(mnt-mnt_fsname, euser_id,
D);
+ r=get_smb_linux_v2_quota(mnt-mnt_fsname, euser_id,
D, 'u');
if (r == -1)
- r=get_smb_linux_v1_quota(mnt-mnt_fsname,
euser_id, D);
+ r=get_smb_linux_v1_quota(mnt-mnt_fsname,
euser_id, D, 'u');
}
} else {
- r=get_smb_linux_xfs_quota(mnt-mnt_fsname, euser_id, D);
+ r=get_smb_linux_xfs_quota(mnt-mnt_fsname, euser_id, D, 'u');
}
+
+ /* Massimo Del Sarto delsarto at inpe.unipi.it */
+ /* if no limits try with quota group ad gid of the dir */
+ if (r != -1)
+ if ( (D.softlimit == 0) (D.hardlimit == 0) ) {
+ if (strcmp(mnt-mnt_type, xfs)) {
+ r=get_smb_linux_gen_quota(mnt-mnt_fsname,
fgrp_id, D, 'g');
+ if (r == -1) {
+
r=get_smb_linux_v2_quota(mnt-mnt_fsname, fgrp_id, D, 'g');
+ if (r == -1)
+
r=get_smb_linux_v1_quota(mnt-mnt_fsname, fgrp_id, D, 'g');
+ }
+ } else {
+ r=get_smb_linux_xfs_quota(mnt-mnt_fsname,
fgrp_id, D, 'g');
+ }
+ }
restore_re_uid();
Re: quota group
At 21.55 05/03/2003 +1100, Andrew Bartlett wrote: On Wed, 2003-03-05 at 20:32, Massimo Del Sarto wrote: I use samba on redhat linux (7.1) For default in redhat each user has also his own group. I created a new group for each samba share that I defined so I can control which users can access to the shares, but if I use the user quota I can't control the quota on this shares. Using a group quota I can assign separate quota to each share (the shares are on the same HD partition): - each user has a quota on the home share - each not home share has its own quota The only problem is that I can't see the quota in windows box. So I modified the smbd/quotas.c to read the quota group associated to the group of the file/directory if the user quota result is 0 (zero). I added a parameter to the function get_smb_linux_* to get an user or a group quota. Wouldn't it be better to report the smaller of the two quotas? I forgotten: - All user have umask set to 002; - In (not home) share I sgid the directory with chmod 2770 share dir and assign a group at this directory (chgrp share group share dir). - In the smb.conf I use inherit permissions = Yes in the share definition. So each files that are created are forced to have the same group of the parent directory In the home directory the files have the gid equal to the uid. In not home (share) directory the files have the gid equal to the group that i created for this share. The result of user quota is 0 (zero) because the user quota are set to 0 (No limit in the user quota) so I can't report a value of 0. Only the group quota is set to a value 0 My patch is tested only in rehat 7.1 and work only on linux. A lot of work must done to extended my idea to all the O.S. Can Stefan Metzmacher do this work and insert in on own patch? Massimo I attach the output of the commnad: diff -u -r samba-2.2.7a/source/smbd/quotas.c samba-2.2.7amds/source/smbd/quotas.c --- samba-2.2.7a/source/smbd/quotas.c Wed Dec 11 10:17:40 2002 +++ samba-2.2.7amds/source/smbd/quotas.cTue Mar 4 09:43:05 2003 @@ -66,13 +66,18 @@ Abstract out the XFS Quota Manager quota get call. / -static int get_smb_linux_xfs_quota(char *path, uid_t euser_id, LINUX_SMB_DISK_QUOTA *dp) +static int get_smb_linux_xfs_quota(char *path, uid_t euser_id, LINUX_SMB_DISK_QUOTA *dp, char type ) Make this a BOOL for type 'group_quota' or even better an enum with values 'USER_QUOTA, GROUP_QUOTA'. If you can repatch this against HEAD, and check with metze (Stefan (metze) Metzmacher [EMAIL PROTECTED]) on how this might conflict with his work in this area. In particular, it might work out best that metze picks this up into his patch. (He is working on being able to modify the quota from an Windows client!). Either way, this certainly is a very nice idea! Andrew Bartlett -- Andrew Bartlett [EMAIL PROTECTED] Manager, Authentication Subsystems, Samba Team [EMAIL PROTECTED] Student Network Administrator, Hawker College [EMAIL PROTECTED] http://samba.org http://build.samba.org http://hawkerc.net -- Ing. Massimo Del Sarto Capo Ufficio CED IRCCS Fondazione Stella Marishttp://www.inpe.unipi.it Tel. +39 050 886268Fax. +39 050 32214 --
