Re: solved: Re: [Samba] Letter instead of A4 with driver installed via Samba's Point'n'Print
Kay Obermueller schrieb: Chris Smith schrieb: On Thursday 18 January 2007 17:51, you wrote: Yes, and it printed already correctly as a remote printer from Linux and OS X. Page Size is set to A4. Hmmm...cups updates the ppd in /etc/cups/ppd/ when the printer options are set ans I'm reasonably sure, but not certain, that it uses that ppd as a base when doing cupsaddsmb. Maybe there's an old version in /var/lib/samba/printers/W32X86 or wherever your distro puts it. Regardless you should be able to set the defaults via Windows by drilling down the printers folder on the server, right click on printer, choose properties, then from the Advanced tab select the box 'Printing Defaults...' and continue. Chris After I repeated cupsaddsmb I must have missed the correct menu in Windows to set the paper size. Since I set it in any menu I could find and tested printing with a brand new untouched Windows client everthing is fine and really works without any user intervention! Thank you. Kay Unfortunately this issue is still unsolved. But I had no time for the last weeks. Now I got the HP Laserjet 2200 reinstalled onto Samba and made it print A4 per default after first installation on a windows client but not the Minolta Magicolor 2200. That one showed A4 in it's properties, but still tried to print Letter on first printout. (I even thought on manipulating the little switch behind it's paper tray...) Also setting defaults on the server doesn't work. And that would help very much. What had an influence was to reinstall the HP Laserjets from a console in wich locales were set to de_DE.UTF-8 instead POSIX. Why not for the Magicolor? Kay -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
solved: Re: [Samba] Letter instead of A4 with driver installed via Samba's Point'n'Print
Chris Smith schrieb: On Thursday 18 January 2007 17:51, you wrote: Yes, and it printed already correctly as a remote printer from Linux and OS X. Page Size is set to A4. Hmmm...cups updates the ppd in /etc/cups/ppd/ when the printer options are set ans I'm reasonably sure, but not certain, that it uses that ppd as a base when doing cupsaddsmb. Maybe there's an old version in /var/lib/samba/printers/W32X86 or wherever your distro puts it. Regardless you should be able to set the defaults via Windows by drilling down the printers folder on the server, right click on printer, choose properties, then from the Advanced tab select the box 'Printing Defaults...' and continue. Chris After I repeated cupsaddsmb I must have missed the correct menu in Windows to set the paper size. Since I set it in any menu I could find and tested printing with a brand new untouched Windows client everthing is fine and really works without any user intervention! Thank you. Kay -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Letter instead of A4 with driver installed via Samba's Point'n'Print
Hello everyone, I have already asked for this the cups list/newsgroup, but it seems to me that this might be more a question about Samba. According (hopefully) to these howtos I have setup printers and prepared their cups postscript drivers to be installed automatically via Samba and the so called Point'n'Print method: https://forums.gentoo.org/viewtopic-t-456501-highlight-.html http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/Samba-HOWTO-Collection-3.0-PrintingChapter-11th-draft.html Everything works pretty well except that a new windows client that installs the driver tries to print out as Letter instead of A4. I can then change this setting and it is correctly saved, but only on this particular client. Is there a way to set this beforehand in the driver on the server? In smb.conf this is set: default devmode = Yes Does this have influence on this issue? When I grep for A4 in R020-magicolor.ppd I get: *DefaultPageSize: A4 *DefaultPageRegion: A4 *DefaultImageableArea: A4 *DefaultPaperDimension: A4 In both ppd's. In /etc/cups/ppd and in /var/lib/samba/printers/W32X86/3 it is the same. And I already printed correctly in A4 to this printer from Linux and OS X via IPP before using cupsaddsmb. But here I can find Letter and no A4: #strings /var/lib/samba/ntprinters.tdb | grep Letter result: Letter Letter It seemed to me to be related to what is described here: http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/Samba-HOWTO-Collection-3.0-PrintingChapter-11th-draft.html#AEN851 So I did repeat cupsaddsmb with default devmode = no instead of yes in smb.conf. This gave mixed results. I tried to delete the driver this way, but it was still set to the printer and didn't work: #rpcclient -U'root%x' cups.server.loc -c'deldriver R020-magicolor' Failed to remove driver R020-magicolor for arch [Windows NT x86] - error 0xbb9! Failed to remove driver R020-magicolor for arch [Windows NT x86] - error 0xbb9! result was WERR_UNKNOWN_PRINTER_DRIVER Because I didn't find out how to unset the driver I set a non existent driver NULL: #rpcclient -U'root%x' cups.server.loc -c'setdriver R020-magicolor NULL' Succesfully set R020-magicolor to driver NULL. I hope this was a correct deletion: #rpcclient -U'root%x' cups.server.loc -cdeldriver R020-magicolor Driver R020-magicolor removed for arch [Windows NT x86]. result was WERR_UNKNOWN_PRINTER_DRIVER This time I hopefully prevented Samba from interfere with the device mode in smb.conf: default devmode = No Then I executed cupsaddsmb and specified the driver: #cupsaddsmb -U root -H localhost -h localhost -v R020-magicolor It wrote in it's output that all of it's operations were successfull. As a result on the Magicolor it still tries to print as Letter on the first printout without correction of the setting. But on the the server is also another printer, which I thought I didn't change in that procedure and it's driver was correctly set instead! #rpcclient -U'root%x' cups.server.loc -c'enumprinters' flags:[0x80] name:[\\cups\R020-magicolor] description:[\\cups\R020-magicolor,NULL,R020-magicolor] comment:[R020-magicolor] flags:[0x80] name:[\\mini\LaserJet2200DN] description:[\\cups\LaserJet2200DN,LaserJet2200DN,HP LaserJet in R411] comment:[HP LaserJet in R411] The LaserJet now works perfectly although it ignored the wrong paper for the print job and just printed. Unfortunately the Magicolor is too intelligent... How are settings in device mode influenced? Could naming the driver the same as it's printer cause problems? Kay -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba cannot find group in ADS
Kay Obermueller wrote: Hello everybody, I have a Samba 3.0.7-Debian setup and joined a W2k ADS-domain. A User is put in SambaUsers as his primary primary group. I can create files from XP client that belong to user in SambaUsers The user is successfully authenticated by samba and can access his profile. I want him to be able to access the share p on samba. Without valid users set for the share this is possible. If I try to limit access to SambaUsers, this group isn't found by samba in the domain. Shall I have a closer look on winbind? Who can help me have a good sunday? :) Kay testparm: # Global parameters [global] unix charset = UTF8 display charset = UTF8 workgroup = LIHH realm = LIHH.LOC server string = %h server (Samba %v) security = ADS password server = liba.lihh.loc log level = 3 passdb:5 auth:10 winbind:5 syslog = 0 log file = /var/log/samba/log.%m max log size = 1000 domain master = No dns proxy = No wins server = 10.1.1.3 ldap ssl = no panic action = /usr/share/samba/panic-action %d idmap uid = 1-2 idmap gid = 1-2 template primary group = sambausers template shell = /bin/bash winbind separator = + winbind use default domain = Yes [homes] comment = Home Directories create mask = 0700 directory mask = 0700 browseable = No [p] comment = Documents path = /home/samba/p valid users = @LIHH\SambaUsers read only = No create mask = 0750 [profiles] comment = Documents path = /home/samba/profiles read only = No create mask = 0750 The groups on the DC: morgane:/etc/samba# wbinfo -g BUILTIN+System Operators BUILTIN+Replicators BUILTIN+Guests BUILTIN+Power Users BUILTIN+Print Operators BUILTIN+Administrators BUILTIN+Account Operators BUILTIN+Backup Operators BUILTIN+Users Domänencomputer Domänen-Gäste Zertifikatherausgeber Organisations-Admins Schema-Admins Domänencontroller Domänen-Benutzer Domänen-Admins Richtlinien-Ersteller-Besitzer DnsUpdateProxy SambaUsers Groupmap on samba machine: morgane:/etc/samba# net groupmap list System Operators (S-1-5-32-549) - -1 Replicators (S-1-5-32-552) - -1 Guests (S-1-5-32-546) - -1 Domain Guests (S-1-5-21-788693271-928550680-3704065133-514) - nobody Power Users (S-1-5-32-547) - -1 Print Operators (S-1-5-32-550) - -1 Administrators (S-1-5-32-544) - -1 Account Operators (S-1-5-32-548) - -1 Domänen-Benutzer (S-1-5-21-788693271-928550680-3704065133-1201) - users Domain Admins (S-1-5-21-788693271-928550680-3704065133-512) - root SambaUsers (S-1-5-21-788693271-928550680-3704065133-21065) - sambausers Backup Operators (S-1-5-32-551) - -1 Users (S-1-5-32-545) - -1 Domain Users (S-1-5-21-788693271-928550680-3704065133-513) - -1 The suspicious output of /var/log/samba/log.winbindd: [2004/11/14 04:28:05, 1] nsswitch/winbindd_group.c:winbindd_getgrnam(298) group LIHH\SambaUsers in domain LIHH does not exist [2004/11/14 04:28:06, 3] libads/ads_ldap.c:ads_sid_to_dn(222) ads sid_to_dn mapped CN=Pentium,CN=Computers,DC=lihh,DC=loc [2004/11/14 04:28:06, 1] nsswitch/winbindd_group.c:winbindd_getgrnam(298) group LIHH\SambaUsers in domain LIHH does not exist [2004/11/14 04:28:14, 1] nsswitch/winbindd_group.c:winbindd_getgrnam(298) group LIHH\SambaUsers in domain LIHH does not exist [2004/11/14 04:28:15, 1] nsswitch/winbindd_group.c:winbindd_getgrnam(298) group LIHH\SambaUsers in domain LIHH does not exist Then of course in /var/log/samba/log.ip_number I get: [2004/11/14 04:28:15, 2] smbd/service.c:make_connection_snum(314) user 'LIHH+User.Name' (from session setup) not permitted to access this share (p) [2004/11/14 04:28:15, 3] smbd/error.c:error_packet(129) error packet at smbd/reply.c(416) cmd=117 (SMBtconX) NT_STATUS_ACCESS_DENIED Hello everybody, for my problem of not finding SambaUsers I found something odd: grep 10032 /etc/group sambausers:x:10032: wbinfo -G 10032 S-1-5-32-552 net groupmap list Replicators (S-1-5-32-552) - -1 SambaUsers (S-1-5-21-788693271-928550680-3704065133-21065) - sambausers Somehow the unix group sambausers matches Replicators on windows instead of SambaUsers. Why is this? Or better how to correct this? Kay -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba cannot find group in ADS
Kay Obermueller wrote: Kay Obermueller wrote: Hello everybody, I have a Samba 3.0.7-Debian setup and joined a W2k ADS-domain. A User is put in SambaUsers as his primary primary group. I can create files from XP client that belong to user in SambaUsers The user is successfully authenticated by samba and can access his profile. I want him to be able to access the share p on samba. Without valid users set for the share this is possible. If I try to limit access to SambaUsers, this group isn't found by samba in the domain. Shall I have a closer look on winbind? Who can help me have a good sunday? :) Kay testparm: # Global parameters [global] unix charset = UTF8 display charset = UTF8 workgroup = LIHH realm = LIHH.LOC server string = %h server (Samba %v) security = ADS password server = liba.lihh.loc log level = 3 passdb:5 auth:10 winbind:5 syslog = 0 log file = /var/log/samba/log.%m max log size = 1000 domain master = No dns proxy = No wins server = 10.1.1.3 ldap ssl = no panic action = /usr/share/samba/panic-action %d idmap uid = 1-2 idmap gid = 1-2 template primary group = sambausers template shell = /bin/bash winbind separator = + winbind use default domain = Yes [homes] comment = Home Directories create mask = 0700 directory mask = 0700 browseable = No [p] comment = Documents path = /home/samba/p valid users = @LIHH\SambaUsers read only = No create mask = 0750 [profiles] comment = Documents path = /home/samba/profiles read only = No create mask = 0750 The groups on the DC: morgane:/etc/samba# wbinfo -g BUILTIN+System Operators BUILTIN+Replicators BUILTIN+Guests BUILTIN+Power Users BUILTIN+Print Operators BUILTIN+Administrators BUILTIN+Account Operators BUILTIN+Backup Operators BUILTIN+Users Domänencomputer Domänen-Gäste Zertifikatherausgeber Organisations-Admins Schema-Admins Domänencontroller Domänen-Benutzer Domänen-Admins Richtlinien-Ersteller-Besitzer DnsUpdateProxy SambaUsers Groupmap on samba machine: morgane:/etc/samba# net groupmap list System Operators (S-1-5-32-549) - -1 Replicators (S-1-5-32-552) - -1 Guests (S-1-5-32-546) - -1 Domain Guests (S-1-5-21-788693271-928550680-3704065133-514) - nobody Power Users (S-1-5-32-547) - -1 Print Operators (S-1-5-32-550) - -1 Administrators (S-1-5-32-544) - -1 Account Operators (S-1-5-32-548) - -1 Domänen-Benutzer (S-1-5-21-788693271-928550680-3704065133-1201) - users Domain Admins (S-1-5-21-788693271-928550680-3704065133-512) - root SambaUsers (S-1-5-21-788693271-928550680-3704065133-21065) - sambausers Backup Operators (S-1-5-32-551) - -1 Users (S-1-5-32-545) - -1 Domain Users (S-1-5-21-788693271-928550680-3704065133-513) - -1 The suspicious output of /var/log/samba/log.winbindd: [2004/11/14 04:28:05, 1] nsswitch/winbindd_group.c:winbindd_getgrnam(298) group LIHH\SambaUsers in domain LIHH does not exist [2004/11/14 04:28:06, 3] libads/ads_ldap.c:ads_sid_to_dn(222) ads sid_to_dn mapped CN=Pentium,CN=Computers,DC=lihh,DC=loc [2004/11/14 04:28:06, 1] nsswitch/winbindd_group.c:winbindd_getgrnam(298) group LIHH\SambaUsers in domain LIHH does not exist [2004/11/14 04:28:14, 1] nsswitch/winbindd_group.c:winbindd_getgrnam(298) group LIHH\SambaUsers in domain LIHH does not exist [2004/11/14 04:28:15, 1] nsswitch/winbindd_group.c:winbindd_getgrnam(298) group LIHH\SambaUsers in domain LIHH does not exist Then of course in /var/log/samba/log.ip_number I get: [2004/11/14 04:28:15, 2] smbd/service.c:make_connection_snum(314) user 'LIHH+User.Name' (from session setup) not permitted to access this share (p) [2004/11/14 04:28:15, 3] smbd/error.c:error_packet(129) error packet at smbd/reply.c(416) cmd=117 (SMBtconX) NT_STATUS_ACCESS_DENIED Hello everybody, for my problem of not finding SambaUsers I found something odd: grep 10032 /etc/group sambausers:x:10032: wbinfo -G 10032 S-1-5-32-552 net groupmap list Replicators (S-1-5-32-552) - -1 SambaUsers (S-1-5-21-788693271-928550680-3704065133-21065) - sambausers Somehow the unix group sambausers matches Replicators on windows instead of SambaUsers. Why is this? Or better how to correct this? Kay Hello again, I made some substantial progress in getting the groups thing to work. In some posting from this NG I found an expample with the syntax of valid users = @ADSDOMAIN\groupname. This doesn't work. Winbind then asks for \\ADSDOMAIN\ADSDOMAIN\groupname so winbind -i told me. It should be valid users = @groupname. Of course I already tried that before also... But then I tried winbind -n which means caching disabled and now it works! So what's wrong with the caching? Kay -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Samba cannot find group in ADS
Hello everybody, I have a Samba 3.0.7-Debian setup and joined a W2k ADS-domain. A User is put in SambaUsers as his primary primary group. I can create files from XP client that belong to user in SambaUsers The user is successfully authenticated by samba and can access his profile. I want him to be able to access the share p on samba. Without valid users set for the share this is possible. If I try to limit access to SambaUsers, this group isn't found by samba in the domain. Shall I have a closer look on winbind? Who can help me have a good sunday? :) Kay testparm: # Global parameters [global] unix charset = UTF8 display charset = UTF8 workgroup = LIHH realm = LIHH.LOC server string = %h server (Samba %v) security = ADS password server = liba.lihh.loc log level = 3 passdb:5 auth:10 winbind:5 syslog = 0 log file = /var/log/samba/log.%m max log size = 1000 domain master = No dns proxy = No wins server = 10.1.1.3 ldap ssl = no panic action = /usr/share/samba/panic-action %d idmap uid = 1-2 idmap gid = 1-2 template primary group = sambausers template shell = /bin/bash winbind separator = + winbind use default domain = Yes [homes] comment = Home Directories create mask = 0700 directory mask = 0700 browseable = No [p] comment = Documents path = /home/samba/p valid users = @LIHH\SambaUsers read only = No create mask = 0750 [profiles] comment = Documents path = /home/samba/profiles read only = No create mask = 0750 The groups on the DC: morgane:/etc/samba# wbinfo -g BUILTIN+System Operators BUILTIN+Replicators BUILTIN+Guests BUILTIN+Power Users BUILTIN+Print Operators BUILTIN+Administrators BUILTIN+Account Operators BUILTIN+Backup Operators BUILTIN+Users Domänencomputer Domänen-Gäste Zertifikatherausgeber Organisations-Admins Schema-Admins Domänencontroller Domänen-Benutzer Domänen-Admins Richtlinien-Ersteller-Besitzer DnsUpdateProxy SambaUsers Groupmap on samba machine: morgane:/etc/samba# net groupmap list System Operators (S-1-5-32-549) - -1 Replicators (S-1-5-32-552) - -1 Guests (S-1-5-32-546) - -1 Domain Guests (S-1-5-21-788693271-928550680-3704065133-514) - nobody Power Users (S-1-5-32-547) - -1 Print Operators (S-1-5-32-550) - -1 Administrators (S-1-5-32-544) - -1 Account Operators (S-1-5-32-548) - -1 Domänen-Benutzer (S-1-5-21-788693271-928550680-3704065133-1201) - users Domain Admins (S-1-5-21-788693271-928550680-3704065133-512) - root SambaUsers (S-1-5-21-788693271-928550680-3704065133-21065) - sambausers Backup Operators (S-1-5-32-551) - -1 Users (S-1-5-32-545) - -1 Domain Users (S-1-5-21-788693271-928550680-3704065133-513) - -1 The suspicious output of /var/log/samba/log.winbindd: [2004/11/14 04:28:05, 1] nsswitch/winbindd_group.c:winbindd_getgrnam(298) group LIHH\SambaUsers in domain LIHH does not exist [2004/11/14 04:28:06, 3] libads/ads_ldap.c:ads_sid_to_dn(222) ads sid_to_dn mapped CN=Pentium,CN=Computers,DC=lihh,DC=loc [2004/11/14 04:28:06, 1] nsswitch/winbindd_group.c:winbindd_getgrnam(298) group LIHH\SambaUsers in domain LIHH does not exist [2004/11/14 04:28:14, 1] nsswitch/winbindd_group.c:winbindd_getgrnam(298) group LIHH\SambaUsers in domain LIHH does not exist [2004/11/14 04:28:15, 1] nsswitch/winbindd_group.c:winbindd_getgrnam(298) group LIHH\SambaUsers in domain LIHH does not exist Then of course in /var/log/samba/log.ip_number I get: [2004/11/14 04:28:15, 2] smbd/service.c:make_connection_snum(314) user 'LIHH+User.Name' (from session setup) not permitted to access this share (p) [2004/11/14 04:28:15, 3] smbd/error.c:error_packet(129) error packet at smbd/reply.c(416) cmd=117 (SMBtconX) NT_STATUS_ACCESS_DENIED -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Access to share is denied for groups on samba 3 - ADS
Hello everybody, I have a Samba 3.0.7-Debian setup and joined an ADS-domain. I want to share a directory, but only an explicitly set valid user can access the share. It should be accessible to sambausers, but that doesn't work. I can also logon as ADS-user on the samba box and get a shell. In smb.conf: [p] comment = Documents path = /home/samba/p read only = No valid users = @ADSDOMAIN\sambausers # valid users = @LIHH\SambaUsers (doesn't work either) # valid users = ADSDOMAIN+username (this works) create mask = 0750 browsable = Yes I the log file /var/log/samba/log.xpclient I always get: user 'ADSDOMAIN+username' (from session setup) not permitted to access this share (p) [2004/11/06 01:17:29, 3] smbd/error.c:error_packet(129) error packet at smbd/reply.c(416) cmd=117 (SMBtconX) NT_STATUS_ACCESS_DENIED net groupmap list: SambaUsers (S-1-5-21-788693271-928550680-3704065133-21065) - sambausers What ist still missing? Thank you in advance. Kay -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
