RE: [Samba] winbind - getent problem
Than, When you do the getent passwd user you need to actually specify the domain for example if you have 2 domains called DOMA and DOMB and you had users in each you would do getent passwd doma\\username or domb\\username (given \ is your winbind separator ) This should help you with your question I believe James -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Budai Laszlo Sent: Thursday, November 03, 2005 8:11 AM To: samba@lists.samba.org Subject: [Samba] winbind - getent problem Hi, I'm trying to authenticate users from AD. I did join the machine to the domain, and I'm able to see the users list with wbinfo -u. I have the following problem: getent passwd it givs me the list of all users. getent passwd user does not give any answer. what could be the problem? I'm using SUSE Linux 10. with the packages that came with the distrib. Than -- 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 with 3.0.20 admin users=
Hey all, Can anyone help with a problem since upgrading from samba 3.0.14 to 3.0.20 I have a problem from a share. If the admin users = is added it seems to be ignored. Before with 3.0.14 the share was defined like this [cai_hw1] comment = Dr. Cai, Graphics path = /home/meugrads/cai_hw valid users= @cai_hw1 admin users = fau\caig public = no writeable = yes browsable = no directory mask = 0700 create mode = 0700 This setup allow students in the group @cai_hw1 access to the share and then each directory below that was owned by the particular student so other students could do nothing except in their own directory. Since the professor was listed as admin user he could get into any directory to grade the homework etc. ** Please note he was NOT listed in the valid users group (he was not in @cai_hw1 /etc/netgroup) However since upgrading to 3.0.20 with the same conf file the professor is no longer able to get to the share, it gives permission denied. So I added him to the /etc/netgroup file and he can now get accees to the share but gets access denied when going into one of the student directories. Can anyone tell me how admin users and valid users works in the new version, I am not sure if this is a bug or if I neglected to do something. Thanks for your help James Mauser Computer Coordinator College of Engineering and Computer Science Florida Atlantic University 561-239-2546 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] problem after upgrading to samba 3.0.14a
Hey all, I was wondering if anyone could help me out with a problem that I am having on a share (other than home directory) after upgrading to samba 3.0.14a The situation is this: A share is created Like this [me_office] browsable = no comment = ME Front Office valid users = @me_front force group = mefront create mode = 0775 directory mode =0775 read only = no writeable = yes path = /home/mestaff/me_front_office the users in the NIS group me_front get access to files and can read write with no problem, however they are unable to overwrite an exisiting file (even if they created it ) so programs like MSword that have auto-backup turend on, just end up making lots of ~tmp files instead of being able to save the file back. I've had to turn of the autobackup feature in word. And everytime they save the file it needs to be given a different file name or the error access denied comes up. This does NOT happen if writing to the home share. This samba box is joined to a w2k3 AD The domain its connected to is a child domain where all users are seen from the getent passwd command However getent group returns groups with child domain users but NOT parent domain users in the group (this seems to be broken, thus the use for NIS groups) Any thoughts on what to add to the smb.conf file to fix this? This was working fine until the upgrade to 3.0.14a Thanks in advance James Mauser Computer Coordinator College of Engineering and Computer Science Florida Atlantic University 561-239-2546 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] MSWORD problem after upgrade to samba 3.0.14a
Hey all, I was wondering if anyone else is experiencing a problem with Samba 3.0.14a. The problems is after the users connects to a samba share and opens msword, creates a document then does file|save Then opens the file and makes changes then does file|save again, it comes up and says that the backup copy of the file could not be created and never actually saves the file. You have to do save as instead. In msword if you turn off always save a backup copy then file|save works with no problem. This has only happened after upgrading from samba 3.0.10 to 3.0.14a Samba is a member of a windows 2003 AD. Users connect to the share with their AD username I have set logging up quite high but the only thing that stands out is [2005/06/10 16:37:37, 2] smbd/posix_acls.c:set_canon_ace_list(2420) set_canon_ace_list: sys_acl_set_file type file failed for file ~WRD1929.tmp (Operation not supported). Have I overlooked a change I have needed to do since upgrading to 3.0.14a ? Thanks James Mauser Computer Coordinator College of Engineering and Computer Science Florida Atlantic University 561-239-2546 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Trusted Domain Gorups
Hey all, I have posted this question before but never seem to get a response: I was wondering if anyone can help me with the question of groups and trusted domains. We have the setup of 2 AD Domains running in native 2003 (I don't know the specific trust setup as I am not the Admin for the windows side) Dom1 Dom2 I have the following working: Log in to solaris, linux etc using dom1\username or dom2\username Getent passwd shows both dom1\usernames and dom2\usernames Getent group shows both dom1\groups and dom2\groups However in dom2\gorup I have both dom1\user AND dom2\user The getent group will only show the dom2\user If I do a getent group dom1\group I see the groups and the dom1\users with no problem (There are only dom1 users in all the groups) What needs to be done to be able to ensure I can do getent group dom2\group and see BOTH dom1\user and dom2\user I don't believe the OS is important as I have the same on different version of linux, solaris etc. And I have a variety of samba versions with the same issue. I have updated one of the servers to 3.0.14a and still have no luck understanding what the issue is. I will be happy to give whatever log information is needed (although I am not seeing Currently my workaround to this issue is Create a /etc/netgroup entry and add the dom1\user to the group then in smb.conf I reference the netgroup group. This seems like double work since I already have the dom1\users in the dom2\group and on the windows boxes this works fine. Thanks for any and all help that you can provide on this issue: James Mauser Computer Coordinator College of Engineering and Computer Science Florida Atlantic University 561-239-2546 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Question about groups in samba from and AD
I have a question regarding groups that hopefully someone can lead me to a answer on: We have a Active Directory set up in mixed mode and this AD has 2 domains in it (the top level (I'll call main) and one trusted domain (which I'll call trusted) From a linux Fedora core 3 box: We are able to have users log into the linux box with their AD username and password We are able to have users connect to the shares on the linux samba box. We have several linux boxes that users log into with their same username and get the same uid (via ldap) What's not working though is: having permissions bassed off of groups. chgrp trusted\groupname (works) but no users ever get permissions to the group because: getent group trusted\groupname it will retrun the group name with no users (except for users in the trusted domain will show up but none from main) whereas chgrp main\groupname works and users can have permissions to the share with no problem. (but since we don't have access to add groups or users to groups on the main domain we have to use the trusted domain) There are users from the trusted domain and from the main domain in this group We have gotten groups set up but by using netgroup and /etc/groups to allow groups While this is a work around it would be nice to be able to use the groups that are already created on the AD and not have to duplicate efforts James Mauser Coordinator Computer Applications College of Engineering and Computer Science Florida Atlantic University 561-239-2546 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] weired problem after file move
I am using samba 3.0.10.fc3 and am experiencing a weird scenario. I had a user that was trying to move data from one drive to another. However, The destination drive was full and rather than return out of disk space what happened was only 0 length files were created but more importantly is the source files got deleted. I would think that there would be a sanity check on rather the file was moved correctly before finishing the move command (as I believe it should happen is: check space requirement, then file gets copied to destination and then source file gets deleted). The source drive is on a windows server The destination drive is on the samba 3.0.10.fc3 server which has its file system NFS mounted Does anyone have an idea on this, or need more information to know why samba is allowing a file move to a full destination? Thanks for your help James Mauser College of Engineering and Computer Science Florida Atlantic University 561-239-2546 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] solaris 8 and ls -l problems
Hey All, We recently upgraded to samba 3.0.7 running on solaris 8. We have the box joined to as a member server in a Windows 2000 AD and we have pam authentication working to log in to the box with, The idmap backend is set to a ldap server that is also joined the the AD. The UIDS between the boxes are fine as you can do a getent passwd domain\\username (we have the default \ for the winbind separator) and it will return the same uid on the solaris and linux box so that is working, The problem is when doing the command ls -l on a file owned by domain\username you get no response (just sits for hours and hours never returning the listing), if you do the ls command without the -l it works fine. When you do truss ls -l on the same file it returns a few lines that show its looking like its reading the usernames like the following (please note I cut out the usernames) read(3, L K O S K I N E , F A U.., 10484)= 10484 alarm(0)= 0 sigaction(SIGALRM, 0xFFBEC898, 0xFFBEC948) = 0 sigfillset(0xFF3428C8) = 0 sigprocmask(SIG_BLOCK, 0xFFBEC938, 0xFFBEC928) = 0 alarm(1)= 0 Received signal #14, SIGALRM, in sigsuspend() [caught] sigsuspend(0xFFBEC918) Err#4 EINTR setcontext(0xFFBEC600) alarm(0)= 0 sigprocmask(SIG_UNBLOCK, 0xFFBEC938, 0x) = 0 sigaction(SIGALRM, 0xFFBEC898, 0x) = 0 Then it keeps repeating the following: alarm(2)= 0 sigsuspend(0xFFBEC918) (sleeping...) Received signal #14, SIGALRM, in sigsuspend() [caught] sigsuspend(0xFFBEC918) Err#4 EINTR setcontext(0xFFBEC600) All information I can find is there is something wrong with the libnss_winbind.so However, I am totally stuck as to what's happening.. any help or advice would surely be appreciated anymore logs or trace information that is needed please ask. Thanks James Mauser College of Engineering Florida Atlantic University -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
