RE: [Samba] What exactly IS the winbind daemon?
You are correct, you don't need winbindd unless you are connecting a Windows domain. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Oliver Heering Sent: Thursday, July 28, 2005 7:32 AM To: samba@lists.samba.org Subject: [Samba] What exactly IS the winbind daemon? Hi, maybe this is a newbie-question, but ... here we go: I read the documentation for winbindd several times now but didn't get far. We run Samba as primary domain controller for several dozen clients and over 3000 users and never used winbind, so my question is quite simple: What does winbind provide and when do i need it? I assume that winbind is only used when i use samba as a client in a domain with a MS domain controller, is that correct? mfg, Oliver Heering Medienzentrum der Universität Dortmund http://www.medienzentrum.uni-dortmund.de -- 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] Help! Problem with NT PDC on 3.0.14a
Hello, We are trying to add a 2nd samba server to our domain. We are using an NT 4.0 PDC and connecting to the PDC using winbind. Our network is relatively small - 25 computers. We have no Active Directory servers, no WINS servers, and the existing samba server running 3.0.11 has been running for 18 months with no issues. We are completely stuck trying to add a second server. We've configured the 2nd server EXACTLY the same as the first. It's on the same subnet, we're using the same version of Linux (RHES3), and are using the same smb.conf file (except for the 'netbios name' parameter). The only difference that we can find is the samba version (3.0.14a vs. 3.0.11). Here's the problem: when we try to join the domain, we receive an 'Unable to find a suitable server' error and 'utils/net_ads.c:ads_startup(191) ads_connect: No such file or directory'. This appears to be an Active Directory error, which is confusing since we aren't using Active Directory. If we set the 'wins server' parameter to our PDC, wbinfo -u will correctly show all the user names and passwords, but getent passwd won't list our Domain users. Any thoughts for how we can proceed? We're pretty frustrated, and thinking about just switching the 2nd server to a windows box since this has already taken a few days of time. FYI: our smb.conf is listed below Thanks, Josh Lindenmuth [global] # seperate domain and username (e.g. domain+username) winbind separator = + # valid domain users range idmap uid = 1-2 # valid domain group range idmap gid = 1-2 # allow enumeration of winbind users and groups winbind enum users = yes winbind enum groups = yes # GENERAL SAMBA SETTINGS workgroup = PAYTIME1 dns proxy = no log level = 1 log file = /var/log/samba/%m.log netbios name = LINUX2 load printers = yes server string = Samba App Server password server = * socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 os level = 20 encrypt passwords = yes printcap name = /etc/printcap security = domain max log size = 50 browsable = yes #JAL new DOS mode settings dos filemode = yes dos filetimes = yes dos filetime resolution = yes directory mask = 0775 create mask = 0777 force create mode = 0 mangled names = yes mangle prefix = 6 mangling method = hash2 # disable opportunistic locking - to fix samba issues oplocks = no level2 oplocks = no [share] comment = Shared Drive path = /var/winshare valid users = @PAYTIME1+Domain Users, @PAYTIME1+Domain Admins admin users = PAYTIME1+Administrator, @PAYTIME1+Domain Admins read only = no public = no writable = yes printable = no nt acl support = yes -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] HELP: Permissions in Samba 3.0.2
We are having difficulty setting permissions with Samba 3.0.2. Whenever we use the DOS attrib +r command to make a file read only (or through the file properties) we get an Access Denied error for all users except the owner. This happens even though we've setup our smb.conf to allow Administrator root access (smb.conf below), and the file is rwxrwxrwx. Here is our smb.conf file: - [global] # seperate domain and username (e.g. domain+username) winbind separator = + # valid domain users range idmap uid = 1-2 # valid domain group range idmap gid = 1-2 # allow enumeration of winbind users and groups winbind enum users = yes winbind enum groups = yes winbind use default domain = yes admin users = Administrator # GENERAL SAMBA SETTINGS workgroup = DOMAIN1 dns proxy = no log level = 1 log file = /var/log/samba/%m.log netbios name = SMBSERV1 load printers = yes server string = Samba App Server password server = * socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 os level = 20 encrypt passwords = yes printcap name = /etc/printcap security = domain max log size = 50 browsable = yes # disable opportunistic locking - to fix database issues oplocks = no level2 oplocks = no [SMBNET] comment = Shared Drive path = /var/winshare valid users = @DOMAIN1+Domain Users, @DOMAIN1+Domain Admins read only = no public = no writable = yes printable = no nt acl support = yes Thank you kindly, Josh -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Unexpected results with DOS COPY command and Samba 3.0.2
The DOS copy command does not seem to work as expected with Samba. There are 2 bugs (or issues with our configuration): 1. Copying with a wildcard does not maintain dates (e.g. 'copy G:\SMBNET\file?.txt G:\SMBNET\OUT\' changes the dates to today on Win98 and prior) 2. Copying with a wildcard for a single file creates an incomplete file (e.g. 'copy G:\SMBNET\large?.exe file7.exe' will create a 6K file even though the source is 3M - using xcopy or the full path name works fine) I realize COPY in a DOS .BAT is not the greatest way to move around data, but we have 100's of old DOS batch files that are still using copy commands that I'd hate to mess with. Any suggestions on how to fix this? josh -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
