Re: [Samba] APW New Driver Greyed Out
Thank you very much! This solved my problem. Jay Hallo, Rights/printer management changed in samba 3.??? Check in smb.conf enable privileges = yes and try for example net -S -U root rpc rights grant 'wheel' SePrintOperatorPrivilege bardo [EMAIL PROTECTED] schrieb: Ladies and Gentlemen, I have done this before, but for the life of me cannot get it to work today. I am trying to setup SAMBA to allow non-technical users (one per site) to add printer drivers as needed. I am running Samba 3.0.24. Following are the relevant entries from smb.conf. # workgroup = NT-Domain-Name or Workgroup-Name pid directory = /var/run/ workgroup = BACKUPS netbios name = Backup domain master = Yes time server = yes server string = Jefferson City Backup Server Number 1 username map = /usr/local/samba/lib/user.map log level = 3 pritner admin = hallja,@wheel,root use client driver = No [STCLRI7500] use client driver = No comment = St. Charles Regional Office Copier browseable = Yes printable = Yes guest OK = Yes path = /var/spool/samba printer = STCLRI7500 printer admin = @wheel,hallja,root [print$] comment = Printer Driver Download Area use client driver = No path = /var/spool/samba/drivers browseable = Yes guest ok = Yes read only = Yes admin list = root,hallja,@wheel write list = hallja,@wheel,root When I click on the Advanced Tab, the New Driver box is greyed out. From what I have read, this is a permissions problem, but I have been unable to find the problem. Using myself as an example, I log into the server and my Windows user name is mapped to hallja. hallja is a member of the @wheel group. hallja is listed in the smbpasswd file. I have also tried mapping my Windows username to root without any success. Mapping myself to hallja and root yield the same result. The directory /var/spool/samba/drivers exists, and within that directory, I have created W32X86. Permissions on this folder are root:wheel rwxr-xr-x. Looking through the logs, I did not see any obvious errors. I have bumped the logging up to level 5. Is there anything specific in the logs I should be looking for? And, what else should I be looking at? Thanks in ad -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] APW New Driver Greyed Out
Ladies and Gentlemen, I have done this before, but for the life of me cannot get it to work today. I am trying to setup SAMBA to allow non-technical users (one per site) to add printer drivers as needed. I am running Samba 3.0.24. Following are the relevant entries from smb.conf. # workgroup = NT-Domain-Name or Workgroup-Name pid directory = /var/run/ workgroup = BACKUPS netbios name = Backup domain master = Yes time server = yes server string = Jefferson City Backup Server Number 1 username map = /usr/local/samba/lib/user.map log level = 3 pritner admin = hallja,@wheel,root use client driver = No [STCLRI7500] use client driver = No comment = St. Charles Regional Office Copier browseable = Yes printable = Yes guest OK = Yes path = /var/spool/samba printer = STCLRI7500 printer admin = @wheel,hallja,root [print$] comment = Printer Driver Download Area use client driver = No path = /var/spool/samba/drivers browseable = Yes guest ok = Yes read only = Yes admin list = root,hallja,@wheel write list = hallja,@wheel,root When I click on the Advanced Tab, the New Driver box is greyed out. From what I have read, this is a permissions problem, but I have been unable to find the problem. Using myself as an example, I log into the server and my Windows user name is mapped to hallja. hallja is a member of the @wheel group. hallja is listed in the smbpasswd file. I have also tried mapping my Windows username to root without any success. Mapping myself to hallja and root yield the same result. The directory /var/spool/samba/drivers exists, and within that directory, I have created W32X86. Permissions on this folder are root:wheel rwxr-xr-x. Looking through the logs, I did not see any obvious errors. I have bumped the logging up to level 5. Is there anything specific in the logs I should be looking for? And, what else should I be looking at? Thanks in ad -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] winbind and force user
I have winbind up and running and changed all of my users from the Windows 2003 server to the SAMBA server over the weekend, and no-one noticed. I have run into a problem with force user, and it may just be my understanding of how the paramter works. Following is my configuration for the share. [Barbara.Slevin] comment = Barbaba Slevin's Home Directory browseable = No valid users = mo+barbara.slevin,mo+jay.hall force user = mo+barbara.slevin create mode = 0770 directory mode = 0770 writeable = Yes I am logged in as jay.hall. With the force user statement in the configuration, I receive a message stating, The specified network name is no longer available. This happens whether the force user name is in quotes or not. If I remove the force user statement from the share, I am able to connect to the share without any problems. Can I use the force user statement to map to a Windows 2003 user id (e.g. mo+barbara.slevin)? In reading the smb.conf documentation, I got the impression, it must map to a user id on the local system. If this is not the case, any suggestions as to what I am doing wrong would be greatly appreciated. Thanks, Jay -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] winbind uid problem
Thank you. This worked wonderfully. Jay You probably need to remove the winbindd_idmap.tdb file and restart winbindd. Be advised this will delete all current mappings so any files with those UID/GID's may get different owners. The other more complicated option is to run tdbtool on the file and only delete the bad mappings. If you don't know where to find that file run smbd -b | grep LOCKDIR [EMAIL PROTECTED] wrote: I have installed winbind and it is working, but I need to change the uid/gid being used by winbind since I am running into some conflicts with UIDs. UID 10071 is being used by my spamfilter and winbindd is also mapping one of the user IDs from the W2K3 server to 10071. In an attempt to change this, I modified my smb.conf file as follows. [global] workgroup = MO idmap gid = 15000-2 idmap uid = 15000-2 winbind enum users = yes winbind enum groups = yes winbind separator = + security = domain password server = 10.129.10.41 wins server = 10.129.10.41 I restarted the server thinking my users would be remapped in the range 15000-2. However, they are still mapped in the 1-2 as I had originally set in the smb.conf file. I confirmed this using getent passwd. I am running 3.0.23c on FreeBSD 6.2. Any suggestions would be greatly appreciated. Thanks, Jay -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] winbind uid problem
Thank you!!! I had thought it was stored somewhere, but did not know where. I will give this a try tomorrow, after all of the storms pass. Thanks again. Jay Once a uid mapping has been made,it is persistent, and it is stored in the winbindd_idmap.tdb file in the locks directory. If you want the mapping to remap your users, you would have to remove this file. I'd suggest copying it somewhere safe until you're sure this new mapping works for you. hope this helps, Don - Original Message From: [EMAIL PROTECTED] [EMAIL PROTECTED] To: samba@lists.samba.org Sent: Thursday, August 23, 2007 7:42:40 PM Subject: [Samba] winbind uid problem I have installed winbind and it is working, but I need to change the uid/gid being used by winbind since I am running into some conflicts with UIDs. UID 10071 is being used by my spamfilter and winbindd is also mapping one of the user IDs from the W2K3 server to 10071. In an attempt to change this, I modified my smb.conf file as follows. [global] workgroup = MO idmap gid = 15000-2 idmap uid = 15000-2 winbind enum users = yes winbind enum groups = yes winbind separator = + security = domain password server = 10.129.10.41 wins server = 10.129.10.41 I restarted the server thinking my users would be remapped in the range 15000-2. However, they are still mapped in the 1-2 as I had originally set in the smb.conf file. I confirmed this using getent passwd. I am running 3.0.23c on FreeBSD 6.2. Any suggestions would be greatly appreciated. Thanks, Jay -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba Looking for a deal? Find great prices on flights and hotels with Yahoo! FareChase. http://farechase.yahoo.com/ -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] winbind uid problem
I have installed winbind and it is working, but I need to change the uid/gid being used by winbind since I am running into some conflicts with UIDs. UID 10071 is being used by my spamfilter and winbindd is also mapping one of the user IDs from the W2K3 server to 10071. In an attempt to change this, I modified my smb.conf file as follows. [global] workgroup = MO idmap gid = 15000-2 idmap uid = 15000-2 winbind enum users = yes winbind enum groups = yes winbind separator = + security = domain password server = 10.129.10.41 wins server = 10.129.10.41 I restarted the server thinking my users would be remapped in the range 15000-2. However, they are still mapped in the 1-2 as I had originally set in the smb.conf file. I confirmed this using getent passwd. I am running 3.0.23c on FreeBSD 6.2. Any suggestions would be greatly appreciated. Thanks, Jay -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Forcing user/group with winbindd
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [EMAIL PROTECTED] wrote: Is it possible to force a particular user/group to own files when using winbindd? Yes. But you have to fully qualify the name. Depending on the version of Samba you are running, this may either be a hard or soft requirement. cheer,s jerry I have tried this, but cannot seem to get it to work right. I am running Samba-3.0.23c on FreeBSD 6.2. When I add: force user = mo+linda to my smb.conf, I receive the following error message when I try to connect. System Error 64. The specified network name is no longer available. If I remove the force user statement, I am able to connect to the share fine, but the user is not set as I would like for it to be. Following is a copy of the share I am working with. [Test.Share] comment = Test Share valid users = mo+linda, mo+jay write list = mo+linda, mo+jay create mode = 0777 directory mode = 0777 # force user = mo+linda writeable = Yes brosweable = Yes path = /home/linda I have set the permissions on /home/linda to 777 for testing purposes. I'm sure this is something simple that I am doing wrong. Any suggestions would be greatly appreciated. Thanks, Jay -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] username map security=user and 3.0.25a
On my production servers I am currently using username map= to map the Windows IDs to the IDs on my FreeBSD system. This evening, when I upgraded to 3.0.25a, the username map function stopped working. Reverting to 3.0.23d fixed the problem. I found this bugreport, which is similar, but not exactly the setup I am using since I am using security=user https://bugzilla.samba.org/show_bug.cgi?id=4620 I did not see anything in the log files which stood out. What else should I be looking at? Thanks, Jay -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Forcing user/group with winbindd
Is it possible to force a particular user/group to own files when using winbindd? I have tried force user without any success. What I need to be able to do is have the system administrators connect to the user's account and then have the use access files placed in their directory. When I do this currently, the owner is root and the group is domain admins. Following is how the share is configured. [1234] comment = Linda Bell's Home Directory browseable = Yes valid users = mo+linda,mo+jay,mo+karen # write list = mo+linda,mo+jay # force user = linda create mode = 0770 directory mode = 0770 writeable = Yes admin users = mo+jay, mo+karen path = /home/linda Any suggestions would be greatly appreciated. Thanks, Jay -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Sharp AR-M550N and SAMBA
Recently, we added a Sharp AR-M550N copier to our network. This device functions as an MFC (scanner/printer/copier). When I attempt to install the drivers to the SAMBA server, I receive an error message which displays briefly and then I receive the following error message when trying to access the properties of the printer. Function address 0x3119c9f caused a protection fault. (exception code 0xc05). Some or all property pages may not be displayed. I have tried this with the PCL5e and the PCL6 driver with the same results. Has anyone else seen this type of behavior? And, do you think uploading the drivers using rpcclient as opposed to the Add Printer Wizard, would make any difference? Thanks in advance for your assistance. Jay -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] FreeBSD, winbindd and Domain Groups
I have installed SAMBA from the ports collection and have run into a problem. I am using winbind and I am able to list the groups and users from the Windows 2003 Server (wbinfo -u, wbinfo -g, getent passwd, getent group) without any problem. I am able to display the shares on the SAMBA server using net view without any problem. However, when I try to connect to the share, I receive a message stating, The specified network password is not correct. I am using my username and password which I am currently using on the domain. The valid users on the share are set to jay.hall and the ownership on the directory has been changed to jay.hall. In the log.winbindd file I am seeing the following error messages. [2007/05/02 20:20:00, 0] nsswitch/winbindd_group.c:winbindd_getgrent(829) could not lookup domain group OWS_1299767552_admin [2007/05/02 20:20:00, 1] nsswitch/winbindd_group.c:fill_grent_mem(106) could not lookup membership for group rid S-1-5-21-1220945662-1979792683-83952 Any suggestions anyone has would be greatly appreciated. Thanks, Jay -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] SAMBA and ACLs on FreeBSD 6.1
I have winbind working and it is providing security for my shares. Now, I would like to implement ACLs so I can help my backup users manage everything through MMC. Following is a copy of my smb.conf file. [global] workgroup = XX winbind separator = + idmap uid = 1-2 idmap gid = 1-2 winbind enum users = yes winbind enum groups = yes security = domain password server = 10.129.10.YY client schannel = no wins server = 10.129.10.YY log level = 5 # log file = /var/log/samba.%m name resolve order = wins hosts winbind use default domain = Yes realm = XX [Jay.Hall] comment = Jay Hall's Home Directory browseable = yes writeable = yes valid users = XX+jay.hall force user = hallja directory mode = 0770 path = /home/hallja admin users = Jay.Hall Using wbinfo -u and wbinfo -g I am able to pull user and group information from the Domain Controller. When I use MMC to connect to the share defined above, the only search location listed is the IP address of the server. I believe that should be the name/IP address of the domain controller. This leads me to believe I have something wrong in my smb.conf file. Any suggestions would be greatly appreciated. Thanks, Jay -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
RE: [Samba] FreeBSD and Winbind
Thanks to everyone for the help. I still cannot get getent passwd or getent group to work. This is what I have done since last round of e-mails. If anyone sees anything glaringly obvious, please let me know. 1. Compiled samba from source with --prefix=/usr/local/samba --with-smbtar --with winbind. 2. Modified /etc/nsswitch.conf with passwd: files winbind group: files winbind 3. Copied nss_winbind.so to /usr/lib/libnss_winbind.so and created a symbolic link to the file for libnss_winbind.so.2. libnss_winbind.so has permissions of 444 and is owned by root:wheel. 4. Copied nss_wins.so to /usr/lib/libnss_winbind.so and created a symbolic link to the file for libnss_wins.so.2. libness_wins.so has permissions of 444 and is owned by root:wheel. 5. Ran ldconfig -r to reload shared objects. libnss_winbind and libnss_wins are listed. 6. Started winbind. No errors. 7. wbinfo -u and wbinfo -g return the user and group names. 8. getent passwd and getent group only return local groups and users. If anyone sees anything obviously wrong, please let me know. Thanks, Jay Hi Jay, I just went through something similar on the list. If you are able to use wbinfo -u to see the users, but cannot see them with getent, the issue is almost certainly with the libnss_winbind.so library or in your nsswitch.conf configuration. I believe where the libraries need to be located depends on your linux flavor. I can tell you that on Gentoo with 3.024, they are the following: /usr/lib/libnss_winbind.so /usr/lib/libnss_winbind.so.2 - libnss_winbind.so /usr/lib/libnss_wins.so /usr/lib/libnss_wins.so.2 - libnss_wins.so I believe I have seen documentation which locates them in lib/security for Solaris, and I have seen them as both nss_ and libnss_ in various documentation and posts, so you should check the install documentation for FreeBSD. The nsswitch.conf check is quite simple - you need to make sure winbind is listed as an information source. My nsswitch.conf on gentoo needed to have winbind added on the following: passwd: files winbind group: files winbind Depending on what you have installed, you may need compat, db, nis, or other information stores listed at appropriate places in nsswitch.conf or the FreeBSD equivalent. Since I don't run FreeBSD, I don't want to steer you too far off track. Sincerely, Donald -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Wednesday, February 07, 2007 7:15 PM To: samba@lists.samba.org Subject: [Samba] FreeBSD and Winbind I'm hoping this is an easy question, but the way my day has gone I seriously doubt it is going to be. Today, I installed Samba 3.0.24 with winbind support on my FreeBSD 6.2 server. I am able to join my domain and get information concerning groups and passwords from the domain controller (Windows 2003) without any problem. Where I have run into a problem is using getent to get a copy of the usernames/passwords and groups moved to the Samba machine. When I run getent, only information from the local passwd and group files is displayed. Which leads me to believe this is an nsswitch problem. To be more specific I think I have made a mistake copying the libraries to the proper location. I was not able to find libnss_winbind.so in /usr/samba/source/nsswitch. Instead, I found nss_winbind.so. Is this the correct file to copy? And, where should these files be copied to on FreeBSD? From what I have read so far, I am guessing these should be copied to /usr/lib. I have run ldconfig and it shows (using -r) libnss_winbind.so.1 and libnss_winbind.so.2 being listed in the hints file. My nsswitch has the following configuration passwd: files winbind group: files winbind group_compat: nis hosts: files dns networks: files passwd_compat: nis shells: files Any suggestions concerning how to proceed would be greatly appreciated. Thanks, Jay -- 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
Re: Re[2]: [Samba] FreeBSD and Winbind
It was part of the FreeBSD 6.2 install. Jay Where did you find the genent? I installed from the port but I didn't find the genent in my FreeBSD system. Thanks ALex On Thu, 8 Feb 2007 01:30:36 - (GMT) [EMAIL PROTECTED] wrote: On Thursday 08 February 2007 10:44, [EMAIL PROTECTED] wrote: To be more specific I think I have made a mistake copying the libraries to the proper location. I was not able to find libnss_winbind.so in /usr/samba/source/nsswitch. Instead, I found nss_winbind.so. Is this the correct file to copy? And, where should these files be copied to on FreeBSD? From what I have read so far, I am guessing these should be copied to /usr/lib. Why aren't you using the port? It should Just Work(tm). You can keep the nss shared object in /usr/local/lib because FreeBSD will mount the disks very early on. My nsswitch has the following configuration passwd: files winbind group: files winbind group_compat: nis hosts: files dns networks: files passwd_compat: nis shells: files Try removing the _compat entries. For LDAP I have this.. group: files ldap hosts: files dns networks: files passwd: files ldap shells: files And getent works fine. You could try cranking up debugging in Winbindd too (not that I've ever used it) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C Unfortunately, some things came up and I going to be here for a while. So, I changed the debug level on winbindd to 5. Wow, there is a lot logged! When I use wbinfo -u or wbinfo -g, I can see a request to the DC and information being retrieved. However, when I use getent passwd or getent group, nothing is logged by winbindd. Does this mean the request is not getting to winbindd? Thanks, Jay -- 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] FreeBSD and Winbind
I'm hoping this is an easy question, but the way my day has gone I seriously doubt it is going to be. Today, I installed Samba 3.0.24 with winbind support on my FreeBSD 6.2 server. I am able to join my domain and get information concerning groups and passwords from the domain controller (Windows 2003) without any problem. Where I have run into a problem is using getent to get a copy of the usernames/passwords and groups moved to the Samba machine. When I run getent, only information from the local passwd and group files is displayed. Which leads me to believe this is an nsswitch problem. To be more specific I think I have made a mistake copying the libraries to the proper location. I was not able to find libnss_winbind.so in /usr/samba/source/nsswitch. Instead, I found nss_winbind.so. Is this the correct file to copy? And, where should these files be copied to on FreeBSD? From what I have read so far, I am guessing these should be copied to /usr/lib. I have run ldconfig and it shows (using -r) libnss_winbind.so.1 and libnss_winbind.so.2 being listed in the hints file. My nsswitch has the following configuration passwd: files winbind group: files winbind group_compat: nis hosts: files dns networks: files passwd_compat: nis shells: files Any suggestions concerning how to proceed would be greatly appreciated. Thanks, Jay -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] FreeBSD and Winbind
On Thursday 08 February 2007 10:44, [EMAIL PROTECTED] wrote: To be more specific I think I have made a mistake copying the libraries to the proper location. I was not able to find libnss_winbind.so in /usr/samba/source/nsswitch. Instead, I found nss_winbind.so. Is this the correct file to copy? And, where should these files be copied to on FreeBSD? From what I have read so far, I am guessing these should be copied to /usr/lib. Why aren't you using the port? It should Just Work(tm). You can keep the nss shared object in /usr/local/lib because FreeBSD will mount the disks very early on. My nsswitch has the following configuration passwd: files winbind group: files winbind group_compat: nis hosts: files dns networks: files passwd_compat: nis shells: files Try removing the _compat entries. For LDAP I have this.. group: files ldap hosts: files dns networks: files passwd: files ldap shells: files And getent works fine. You could try cranking up debugging in Winbindd too (not that I've ever used it) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C I removed the compat entires with the same result. I am installing the port now to see if that fixes my problem. When I have some more time tomorrow, I will use the debugging on winbind and see what I can find. Thanks, Jay -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] FreeBSD and Winbind
On Thursday 08 February 2007 10:44, [EMAIL PROTECTED] wrote: To be more specific I think I have made a mistake copying the libraries to the proper location. I was not able to find libnss_winbind.so in /usr/samba/source/nsswitch. Instead, I found nss_winbind.so. Is this the correct file to copy? And, where should these files be copied to on FreeBSD? From what I have read so far, I am guessing these should be copied to /usr/lib. Why aren't you using the port? It should Just Work(tm). You can keep the nss shared object in /usr/local/lib because FreeBSD will mount the disks very early on. My nsswitch has the following configuration passwd: files winbind group: files winbind group_compat: nis hosts: files dns networks: files passwd_compat: nis shells: files Try removing the _compat entries. For LDAP I have this.. group: files ldap hosts: files dns networks: files passwd: files ldap shells: files And getent works fine. You could try cranking up debugging in Winbindd too (not that I've ever used it) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C Unfortunately, some things came up and I going to be here for a while. So, I changed the debug level on winbindd to 5. Wow, there is a lot logged! When I use wbinfo -u or wbinfo -g, I can see a request to the DC and information being retrieved. However, when I use getent passwd or getent group, nothing is logged by winbindd. Does this mean the request is not getting to winbindd? Thanks, Jay -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
