Re: [Samba] Winbindd
* a Samba server that is a member of a Windows domain should run winbindd to allocate IDs for users/groups in its own domain and trusted domains. In my specific situation, the UNIX id's are set up first so they don't conflict with legacy systems/GIDs/UIDs, NT user names match the UNIX user names and users maintain their own UNIX and NT passwords separately ie. it's up to them to make them the same. Is this specific situation, winbindd is going to do more harm than good, if I understand correctly. Right? If it's only a member server then it would have to be getting its information from the resource domain BDC and by the definition above this information is all wrong (other than the username and password) so it would be pointless. Or am I missing something? Where does PAM fit into this? -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] I'm confused. What is winbindd supposed to get me?
I've got a Samba member server as part of a Windows NT domain. User accounts have the same name in both domain. I was having all sorts of trouble when winbindd was running with wierd groups showing up. I happened to screw up the winbindd configuration without noticing causing it to crash, but I ran snmd and nmbd anyway and suddenly everything started working perfectly. The docs say you MUST run winbindd. I'm confused. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] pam_modules.h present but cannot be compiled
Shouldn't I be worried about this? As far as I know I'm using PAM for authentication, but it seems to be working. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] getting Samba 3.0.1 to use NIS UID's/GID's instead of its own
There are two NT domains, the resource domain (pretend it's RESDOM) and the user domain (MASDOM) where RESDOM trusts MASDOM. My Samber server (COOL) is registered in the RESDOM domain. I can do smbclient -L COOL -U MASDOM/myname and it asks for a password and displays the shares correctly, even picking up the NIS logon share. The problems start, however, when I want to connect to the myname share - it won't authenticate. I have a share set up to /tmp and when I write to it, instead of getting the NIS UID and GID, I get GID 1 and UID MASDOM+myname. I want it to pick up the NIS one and use it instead. Here's some stuff from smb.conf [global] workgroup = RESDOM security = DOMAIN netbios name = COOL name resolve order = lmhosts wins bcast preferred master = false local master = no wins support = no NIS homedir = yes guest account = qguest map archive = no winbind separator = + winbind enum users = yes winbind enum groups = yes winbind uid = 1-2 winbind gid = 1-2 [tmp] path = /tmp create mask = 775 guest ok = yes log.winbindd says (among other things): MASDOM is a mixed (or NT4) mode domain ... nsswitch/winbindd_pac.c:winbindd_pam_auth_crap(275) pam auth crap domain: MASDOM user: myname ... getpwname masdom+myname name_to_sid name=myname name_to_sid [rpc] myname for domain MASDOM ... log.192.168.1.3 says (among other things) '/usr/users/MASDOM+myname' does not exist or is not a directory, when connecting to [myname] connect to service tmp initially as user MASDOM+myname (uid=1, gid=1) (pid 7222) /usr/local/samba/bin/testparm complains: 'winbind separator = +' might cause problems with group membership I got that configuration string from Samba documentation. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] you'd better fix this before releasing 3.0.1
Solaris 2.6 gcc 2.95.3 Compiling tdb/tdbbackup. Linking bin/tdbbackup Undefinedfirst referenced Symbol in file smb_snprintf tdb/tdbackup.o I thought we'd fixed this already. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] you'd better fix this before releasing 3.0.1
I'm doing this off a fresh samba.3.0.1pre1.tar.gz downloaded yesterday. gcc 2.95.3 PATH=/usr/bin:/usr/local/bin:/usr/sbin:/usr/ccs/bin:/usr/ucb Some idiosyncracies in ./configure were found. The following were present but cannot be compiled netinet/ip.h security/pam_module.h net/if.h it also warned about ldap, but I'm linking to an NT network, not ADS. We have (from the Makefile): ~ TDBBACKUP_OBJ = tdb/tdbbackup.o tdb/tdbback.o lib/snprintf.o \ ~^^ $(TDBBASE_OBJ) I have: TDBBACKUP_OBJ = tdb/tdbbackup.o tdb/tdbback.o $(TDBBASE_OBJ) -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: RE: [Samba] you'd better fix this before releasing 3.0.1
Yeah, I suppose that would help. *bangs head against wall, then shoots himself* Do you really mean pre1 or did you mean rc1? Rc1 is newer than pre1. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] how do I get winbind going?
I've been bashing my head against this same old problem and I've pretty much nailed it down to winbindd. I'm trying to make a Solaris box run SAMBA 3.0.1.pre3 and exist as a member server without acting as a BDC ie. security=domain. There is no Kerberos or LDAP available. All user accounts are on NIS (not NIS+). The install gives me a /etc/init.d/samba.server script that successfully starts smbd and nmbd. But I can't get anything to authenticate. HOW TO INSTALL AND TEST SAMBA informs me that the winbindd daemon has to be running. Further investigation indicates that winbindd links to PAM. /etc/pam.conf contains stuff, so I have to assume (probably not a good idea) that PAM is working. However, there is no pam_winbind.so file and the documentation (http://www.samba.org/samba/docs/man/winbind.html) appears to say this is only required with linux. So I don't understand how winbind is going to talk to PAM. FInally, what are the side-effects of stopping nscd? Does NIS require it? -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] A device attached to the system is not functioning
(sorry if this is a duplicate, I sent this out on a different email address and it appears to have disappeared of the face of the earth, or I'm blind and/or stupid) I'm attempting to do a network neighbourhood browse of a server called bart. I get a windows box that says \\Bart is not available A device attached to the system is not functioning. log.smbd reports open_sockets_smbd: accept: Software caused connection abort log.192.168.1.103 reports (fake IP) lib/util_sock.c:get_peer_addr(940) getpeername failed. Error was Transport endpoint is not connected -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] samba 3.0.1 pre1 undefined symbol
I'm trying to compile samba and got an error. ld: fatal: Symbol referencing errors Undefined symbol smb_snprintf first referenced in file tdb/tdbback.o Solaris 2.7 gcc 2. gcc version 3.3 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] problem installing 3.0.0 to Solaris 7
this is the error message resulting from make install (snip) Installing bin/CP437.so as /usr/local/samba/lib/charset/CP437.so ./install-sh -c bin/libsmbclient.so /usr/local/samba/lib make: execvp: ./install-sh: Permission denied make: [installclientlib] Error 127 (ignored) : bin/libsmbclient.a /usr/local/samba/lib ./install-sh -c /usr/local/samba/src/samba-3.0.0rc4/source/include/libsmbclient.h /usr/local/samba/include make: execvp: ./install-sh: Permission denied make: [installclientlib] Error 127 (ignored) -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] problem installing 3.0.0 to Solaris 7
make: execvp: ./install-sh: Permission denied Make sure the execute bits are set on install.sh. I noted in my installationit is 644. It should be chmod'ed to 755. Yep, that fixed it. How do I go about telling the development team that this is busted? -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
