Re: [Samba] samba+cups printing. drivers on clients.
On Thu, 2009-09-03 at 09:39 +0400, Sergey Karapetyan wrote: Any help? May be samba or windows clients can forcefully serve\takes drivers always then printer installing? ? Automatic printer driver installation works very well. The procedure is covered in the Samba documentation. http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/classicalprinting.html -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] samba+cups printing. drivers on clients.
Hello Guys! Need help myprintserver: CentOS 5.3; Samba 3.0.33-3.7.el5; Cups 1.3.7 (LPD / socket) RAW printing mode; Windows clients: 2000 SP1-4; XP SP1-2; *has no administrative rights I have already installed printer from myprintserver on clients: name: printer_01 model: HP LJ 3050 (drivers automaticly downloaded then installing printer on windows clients at first time.) works fine. Sometimes printers need replace and replace drivers: I replace printer_01 and now it Kyocera 4020DN And i set correct driver to printer_01 on the myprintserver: rpcclient -U'user%password' -csetdriver printer_01 4020DN myprintserver Now all _new_ windows clients will get correct driver; problem: 1)Old clients who has printer_01 will use old driver (HP). Update not occur. If i remove printer_01 on windows client, driver not removes. and if i try connect \\myprintserver\printer_01 windows client will use HP driver! How can i completely remove printer+driver on windows client(without administrative rights) or another way to solve problem? 2)Some clients need Administrative Rights to first install printer driver? Or will be exception then try printer options page? -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] samba+cups printing. drivers on clients.
Any help? May be samba or windows clients can forcefully serve\takes drivers always then printer installing? -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] CUPS Printing Problem
Hi, I configured samba as PDC on a Fedora Core 3 system. It works well and allows domain logon as well as I am able to use smbclient program without any problem. Now I am trying to configure a SMB Printer for this setup. The printer is located on a Win98 machine. I am configuring this using http://localhost:631. After configuring it I get a error with the following message. Unable to connect to SAMBA host, will retry in 60 seconds...ERROR: Connection failed with error NT_STATUS_UNSUCCESSFUL Nothing gets printed. Can anyone suggest how to correct this mistake. Thanking you in anticipation Regards T.Ullas ### Home Page: http://www.geocities.com/browsingpark Admin Page : http://ullas.modblog.com PHP Page : http://ullast.blogspot.com ### -- ___ Sign-up for Ads Free at Mail.com http://promo.mail.com/adsfreejump.htm -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] CUPS-Printing
Dear SMB-Users, I have a problem with my cups-printing queues. All my printers accessed from windows are raw cups-queues. Printing works fine. When accessing the netconfiguration on http://cupsserver:631/jobs I see the finished print-jobs sent from samba. But the finished jobs cannot be restartet. The jobs sent by linux-clients can be restarted. What do I have to do in order to restart windows-sent jobs as well? Thanks for any comments cheers Stephan -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] CUPS printing postscript code not my document
Hi Neil, try the following in Your smb.conf [GLOBAL] # This option tells cups that the data has already been rasterized cups options = raw This is an new option in samba 3.0.6 It tells CUPS to leave Your printdata untouched. I hope it helps. You can find an very useful documentation for Samba and printing on http://samba.vernstok.nl I prefer the PDF-version best regards Olaf -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] CUPS printing postscript code not my document
Hello: I have a machine running Fedora Core 2 with an HP Color LaserJet 2550L printer connected via a USB cable. Local printing from the fedora machine is just fine. It uses CUPS. I am trying to set this printer up using Samba, but I keep getting postscript code when I try to print from Windows. Here is my smb.conf file: [global] log file = /var/log/samba/%m.log load printers = yes idmap gid = 16777216-33554431 socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 encrypt passwords = yes winbind use default domain = no template shell = /bin/false dns proxy = no netbios name = dsl printing = cups server string = Samba Server idmap uid = 16777216-33554431 os level = 20 printcap name = /etc/printcap security = user max log size = 50 [HP] postscript = yes printer = HP printable = yes path = /var/spool/samba comment = HP Color LaserJet 2550L valid users = @samba I created an account for myself in the samba group on the server. I went to my windows machine (running XP Pro). I added a network printer with the address \\192.168.1.1\HP and it seemed to go fine. When it asked for the driver, I pointed it to the HP 2550 postscript drivers I downloaded from HP's site. Any ideas why this is not working? Thanks, Neil -- Neil Aggarwal, JAMM Consulting, (972)612-6056, www.JAMMConsulting.com FREE! Valuable info on how your business can reduce operating costs by 17% or more in 6 months or less! http://newsletter.JAMMConsulting.com -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] CUPS Printing to PostScript Printer
Richardson, Anthony wrote: I'm having trouble printing to a HP LaserJet 6MP Postscript printer. I'm using CUPS and normal UNIX printing works fine. I've tried to configure SAMBA for point and click printing. That all seemed to go okay except that what is printed is: = [EMAIL PROTECTED] JOB @PJL SET RESOLUTION = 600 @PJL SET ECONOMODE = OFF @PJL ENTER LANGUAGE = POSTSCRIPT = followed by all of the raw Postscript commands. I think it is the -12345X at the beginning of the output that is confusing the printer. Two suggestions come to mind : 1) Edit the ppd file and remove the entries that cause this code to be sent or (better) 2) configure the printer without auto-detect of language I've had similar problems with some other makes of printer so I normally just configure all printers as Postscript only - then some f***ing clueless software vendor comes along and only supports PCL :-( Simon -- Simon Hobson MA MIEE, Technology Specialist Colony Gift Corporation Limited Lindal in Furness, Ulverston, Cumbria, LA12 0LD Tel 01229 461100, Fax 01229 461101 Registered in England No. 1499611 Regd. Office : 100 New Bridge Street, London, EC4V 6JA. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] CUPS Printing to PostScript Printer
I'm having trouble printing to a HP LaserJet 6MP Postscript printer. I'm using CUPS and normal UNIX printing works fine. I've tried to configure SAMBA for point and click printing. That all seemed to go okay except that what is printed is: = [EMAIL PROTECTED] JOB @PJL SET RESOLUTION = 600 @PJL SET ECONOMODE = OFF @PJL ENTER LANGUAGE = POSTSCRIPT = followed by all of the raw Postscript commands. I think it is the -12345X at the beginning of the output that is confusing the printer. I'm using Fedora Core 2, CUPS 1.1.20, and SAMBA 3.0.3. My smb.conf file has = printcap name = cups load printers = yes # It should not be necessary to spell out the print system type unless # yours is non-standard. Currently supported print systems include: # bsd, sysv, plp, lprng, aix, hpux, qnx printing = cups = SAMBA is compiled against the CUPS API. I've tried both the CUPS RAW and Postscript queues. I've uncommented the appropriate lines in the CUPS config files for raw output (mime.types and mime.convs) Can anyone provide any help? Thanks, Tony Richardson -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] samba+cups printing a banner
Vit vmf11 at hotmail.com Mon May 17 19:46:17 GMT 2004 i set up a print server using samba and cups and it seems to be working fine but in my environment it is vital for each printjob to have a banner with netbios name on it. eg i have 700 public computers and 4 printers so i need each computer to print a banner with the hostname to distinguish who prints what. i tried to set it up on the client side but it doesnt seem to be working. any help would be greatly appreciated. 10x You should use the CUPS PostScript drivers for Win NT/2K/XP on your clients (Win 95/98/ME are not supported). They are the only ones to support CUPS banners. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] samba+cups printing a banner
i set up a print server using samba and cups and it seems to be
working
fine but in my environment it is vital for each printjob to have a
banner
with netbios name on it.
eg i have 700 public computers and 4 printers so i need each computer
to
print a banner with the hostname to distinguish who prints what. i
tried
to set it up on the client side but it doesnt seem to be working.
any help would be greatly appreciated. 10x
If you're already running winbindd, the easiest way is to probably add
wins to the hosts line of your nsswitch.conf, and rely on
{job-originating-host-name} in your cups banner. At the very least you
will have the client's ip address, but with WINS in your nsswitch.conf
you should be able to resolve these.
Alternately you might be able to specify a print command in smb.conf
that passes %m as a print option or something, but I couldn't tell you
if cups would accept something like this for sure...
GL,
~ Daniel
---
This message is the property of Time Inc. or its affiliates. It may be
legally privileged and/or confidential and is intended only for the use
of the addressee(s). No addressee should forward, print, copy, or
otherwise reproduce this message in any manner that would allow it to be
viewed by any individual not originally listed as a recipient. If the
reader of this message is not the intended recipient, you are hereby
notified that any unauthorized disclosure, dissemination, distribution,
copying or the taking of any action in reliance on the information
herein is strictly prohibited. If you have received this communication
in error, please immediately notify the sender and delete this message.
Thank you.
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] samba+cups printing a banner
i set up a print server using samba and cups and it seems to be working fine but in my environment it is vital for each printjob to have a banner with netbios name on it. eg i have 700 public computers and 4 printers so i need each computer to print a banner with the hostname to distinguish who prints what. i tried to set it up on the client side but it doesnt seem to be working. any help would be greatly appreciated. 10x -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] CUPS printing from Windows
[Samba] CUPS printing from Windows Alan Becker beckera at softrends.com Tue Feb 17 05:03:19 GMT 2004 I have replaced a WinNT4 PDC with a Samba server. [] Problem: Windows clients (using downloaded drivers from print$) don't seem to have full or proper control of printing. Example 1: An excel user has to click on Print to fit in Page setup in order for the page to be scaled properly. Otherwise it prints on multiple pages in very large type. This can also happen in a Windows-only environment. Example 2: Another Excel user attempts to set Landscape orientation. The setting is accepted. no error is generated, but the page continues to print in portrait orientation. Are your printer drivers installed locally or via Point'n'Print? Are you using the native Windows drivers from the vendor or are you using the CUPS or Adobe PostScript drivers (and let CUPS convert the PS for you)? To begin with, this unit is based on RedHat 9 with all current updates (kernel 2.4.20-28.9, Samba 2.2.7a-8.9.0, Cups 1.1.17-13.3.0.3). After discovering that CUPS was the only printing system that RH9 installed, I went to the documentation and read the HOWTO chapters 18 (Classical printing support) and 19 (CUPS printing support). I then did the following: (1) Create the print queues using the RH/Gnome Printing control applet (2) Test printing from Linkx (ok) (3) Obtain the Windows drivers from the NT4 PDC (copied the whole c:\winnt\...\w32x86 structure to a scratch area. (4) Obtain the detailed descriptions of each installed driver using the rpcclient utility from the Samba server, querying the old NT4 server (temporarily attached) with the getdriver queue_name function. Route the query results to a file. Repeat for all queues. (5) Write a script to parse the output of (4) and automate steps 4-10 of Manual Driver Installation in 15 Steps from Chapter 19. (6) Run the script for each print queue. Drivers appear to be added without problem. OK -- this seems to indicate that you are using the native drivers for Windows provided by the vendor, just as you did on your NT print server (7) Join a WinNT workstation to the Samba domain ??? (8) As Administrator, connect to the laser print queue. Succeeds, no error message. (9) Bring up Excel, attempt to print Landscape as noted above. This fails. What do you mean... fails?? -- Does printing fail altogether? -- Or is it just not printing in landscape mode? If it is the latter, and if you are using a PostScript driver on the Windows clients, check out the Release Notes for CUPS: http://www.cups.org/relnotes.php I seem to remember that there was a landscape/portrait bugfix in the latest 1.1.20 release... Also, printing from Excel is sucking. Are you sure you had the correct settings. Questions:: (A) The failure to command the printer properly suggests a problem with the uploaded drivers. Not necessarily. These things happen in Windows-only places also Are there any other common explanations for this type of behavior?? Yes -- user error, driver bug Did it for sure work (using the same driver settings) with the previous NT print server? (B) I attempted to set the dot-matrix queues to the Generic printer/Raw device. In this mode, I printed a short text file (in Linux), and copied a test file to the network queue (under Windows). In either case, the file was printed, but the paper was not advanced to the next page. Why should it? If you send ASCII text, with no page advance command at the end, the printer wouldn't know that you want the page advance In other words, this queue is so raw that it doesn't even recognise the end of a print job, It does what you tell it. You don't tell it that there is a page advance needed. You should send an appropriate Escape code to the dot matrix printer. so multiple print jobs can be printed on the same page. Is there any middle ground, where inter-job pagination occurs, but no other filtering is enabled?? Yes. For a first insight see the CUPS documentation about writing filters.(*) (If it is too much work for you, you could go to the new printing consultant's page at http://www.linuxprinting.org/consultants.html where you can buy some support. (If our company does it, 10% go to Linuxprinting.org as sponsorship money). (*) You need a filter for the dot-matrix which just adds the page advance command to any ASCII text file. It can also be done via an interface script. See man lpadmin and the -i paramter TIA for your attention. A. Becker Cheers, Kurt -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] CUPS printing from Windows
I have replaced a WinNT4 PDC with a Samba server. I'm not experiencing problems with file sharing/locking at all, but printing is another issue. In this network, there are several dot-matrix printers that are ONLY printed to using a DOS application, and a laser (HP 2300, PCL and PS) that is primarily used for Windows printing. Problem: Windows clients (using downloaded drivers from print$) don't seem to have full or proper control of printing. Example 1: An excel user has to click on Print to fit in Page setup in order for the page to be scaled properly. Otherwise it prints on multiple pages in very large type. Example 2: Another Excel user attempts to set Landscape orientation. The setting is accepted. no error is generated, but the page continues to print in portrait orientation. To begin with, this unit is based on RedHat 9 with all current updates (kernel 2.4.20-28.9, Samba 2.2.7a-8.9.0, Cups 1.1.17-13.3.0.3). After discovering that CUPS was the only printing system that RH9 installed, I went to the documentation and read the HOWTO chapters 18 (Classical printing support) and 19 (CUPS printing support). I then did the following: (1) Create the print queues using the RH/Gnome Printing control applet (2) Test printing from Linkx (ok) (3) Obtain the Windows drivers from the NT4 PDC (copied the whole c:\winnt\...\w32x86 structure to a scratch area. (4) Obtain the detailed descriptions of each installed driver using the rpcclient utility from the Samba server, querying the old NT4 server (temporarily attached) with the getdriver queue_name function. Route the query results to a file. Repeat for all queues. (5) Write a script to parse the output of (4) and automate steps 4-10 of Manual Driver Installation in 15 Steps from Chapter 19. (6) Run the script for each print queue. Drivers appear to be added without problem. (7) Join a WinNT workstation to the Samba domain (8) As Administrator, connect to the laser print queue. Succeeds, no error message. (9) Bring up Excel, attempt to print Landscape as noted above. This fails. Questions:: (A) The failure to command the printer properly suggests a problem with the uploaded drivers. Are there any other common explanations for this type of behavior?? (B) I attempted to set the dot-matrix queues to the Generic printer/Raw device. In this mode, I printed a short text file (in Linux), and copied a test file to the network queue (under Windows). In either case, the file was printed, but the paper was not advanced to the next page. In other words, this queue is so raw that it doesn't even recognise the end of a print job, so multiple print jobs can be printed on the same page. Is there any middle ground, where inter-job pagination occurs, but no other filtering is enabled?? TIA for your attention. A. Becker -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] CUPS printing on Fedora with 3.0.2 RPMs
I have upgraded my Fedora Core 1 file server from the distribution supplied 3.0.0 RPMS to the Fedora/Samba 3.0.2 RPMS I found on the Samba Web Site. After doing this, printers are not be recognized or shared. When I restarted the server this message showed up in /var/log/samba/log.smbd: [2004/02/09 18:00:04, 0] printing/pcap.c:pcap_printer_fn(361) Unable to open printcap file cups for read! My /etc/samba/smb.conf file has this in the [global] section: printing = cups printcap name = cups load printers = yes And it has this for a [printers] section: [printers] path = /var/spool/samba guest ok = yes printable = yes use client driver = yes My /etc/printcap file is mode 644 and contains: # This file was automatically generated by cupsd(8) from the # /etc/cups/printers.conf file. All changes to this file # will be lost. lpcube1|Cubeland community printer:rm=fs.arcamax.com:rp=lpcube1: lpship1|lpship1:rm=fs.arcamax.com:rp=lpship1: This was all working before the upgrade. Ideas? -- Bryan White, ArcaMax Inc. Who approaches the Bridge of Death Must answer me these questions three Ere the other side he see. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] CUPS printing on Fedora with 3.0.2 RPMs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Bryan White wrote: | I have upgraded my Fedora Core 1 file server from | the distribution supplied 3.0.0 RPMS to the Fedora/Samba 3.0.2 | RPMS I found on the Samba Web Site. | This was all working before the upgrade. I goofed the RPMS. my build machine didn't have the cups-devel packag on it. You can rebuild the SRPM or wait until I get new ones uploaded later today. cheers, jerry - -- Hewlett-Packard- http://www.hp.com SAMBA Team -- http://www.samba.org GnuPG Key http://www.plainjoe.org/gpg_public.asc If we're adding to the noise, turn off this song --Switchfoot (2003) -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD4DBQFAKQlDIR7qMdg1EfYRAvqnAKDi8nLKFtoMw+x+D8ZAZZqLfWD5IQCYvrp3 k+7T+08FkxWZQ9tQt/Auxw== =TVFr -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] CUPS printing on Fedora with 3.0.2 RPMs
Hello Bryan. I used the same RPMs, and had the same error initially. If you change your printcap name = /etc/printcap I think you will find that error go away. TTyL From: Bryan White [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: [Samba] CUPS printing on Fedora with 3.0.2 RPMs Date: Tue, 10 Feb 2004 08:58:34 -0500 I have upgraded my Fedora Core 1 file server from the distribution supplied 3.0.0 RPMS to the Fedora/Samba 3.0.2 RPMS I found on the Samba Web Site. After doing this, printers are not be recognized or shared. When I restarted the server this message showed up in /var/log/samba/log.smbd: [2004/02/09 18:00:04, 0] printing/pcap.c:pcap_printer_fn(361) Unable to open printcap file cups for read! My /etc/samba/smb.conf file has this in the [global] section: printing = cups printcap name = cups load printers = yes And it has this for a [printers] section: [printers] path = /var/spool/samba guest ok = yes printable = yes use client driver = yes My /etc/printcap file is mode 644 and contains: # This file was automatically generated by cupsd(8) from the # /etc/cups/printers.conf file. All changes to this file # will be lost. lpcube1|Cubeland community printer:rm=fs.arcamax.com:rp=lpcube1: lpship1|lpship1:rm=fs.arcamax.com:rp=lpship1: This was all working before the upgrade. Ideas? -- Bryan White, ArcaMax Inc. Who approaches the Bridge of Death Must answer me these questions three Ere the other side he see. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba _ Check out the great features of the new MSN 9 Dial-up, with the MSN Dial-up Accelerator. http://click.atdmt.com/AVE/go/onm00200361ave/direct/01/ -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] cups printing
hi i have some trouble with samba and cups. i have a printerserver (debian), cups prints in raw mode. if i print something in winxp i get a paper with the letters bdb followed by the pages i wanted to print. after that i get an empty page too. is there anybody who can help me? greetings jens extract of smb.conf: smb.conf## # If you want to automatically load your printer list rather # than setting them up individually then you'll need this load printers = yes # You may wish to override the location of the printcap file printcap name = /etc/printcap # 'printing = cups' works nicely printing = cups guest account = nobody # invalid users = root [printers] comment = All Printers browseable = yes path = /var/spool/cups printable = yes public = yes writable = yes create mask = 0777 directory mask = 0777 guest ok = yes use client driver = yes # -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] CUPS printing with Samba.
We're running Cups and Samba on a SUSE Linux 8.2 server with Windows 98, NT and 2000 clients. We are experiencing intermittant problems whereby printers on the client PC's are setting themselves to offline when print jobs are sent to them. The problem is I'm finding it difficult to diagnose the cause of this as it isn't happening consistently in that we'll have 25 client pc's in a room set to print to the same network printer and only 4 or 5 of them will set the printer to offline while the other 20 will print fine. All our printers are HP 2100, 2200 and 4050's. I have checked the error log in CUPS and there are none that seem to pertain to the problem. In the Samba logs though there are a series of errors stating :- ERROR: NULL dest in safe_strcpy I don't know if this is related to the problem but would appreciate any help with this problem Cheers Brett -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Cups printing on Samba 3.0.1 from Win2000 SP4
I have a samba based domain controller with a CUPS printer working fine. When I try to connect to a samba printer from Win2000 I get the following in the samba log: 2003/11/04 20:38:02, 0] printing/print_cups.c:cups_queue_get(889) Unable to get jobs for ipp://localhost/printers/goucho - client-error-not-found [2003/11/04 20:38:02, 0] smbd/service.c:set_admin_user(321) root logged in as admin user (root privileges) Any clues are appreciated... Here are the relevant parts of my smb.conf: [global] workgroup = TESTDOM netbios name = blue security = user server string = Samba Server printcap name = /etc/printcap load printers = yes log file = /var/log/samba.log log level = 2 max log size = 5 add machine script = /usr/sbin/useradd -n -g machines -c Machine -d /dev/null -s /bin/false %u add user script = /usr/sbin/useradd %u socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 local master = Yes os level = 65 domain master = yes preferred master = yes domain logons = yes admin users = root csc policy = disable logon script = logon.bat logon path = \\%L\profiles\%U logon drive = H: printer admin = root printing = cups printcap name = cups [printers] comment = All Printers path = /var/spool/samba browseable = yes # Set public = yes to allow user 'guest account' to print guest ok = yes writable = yes public = yes printable = yes printer admin = root, douglas # hosts allow = 0.0.0.0 [goucho] comment = Printer with Restricted Access path = /var/spool/samba_my_printer printer admin = root, douglas browseable = yes printable = yes writeable = yes guest ok = yes username map = /etc/maps -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Cups printing, domain group error, getting closer...
After realizing my CUPS printername in /etc/cups/cupsd.conf must be the same as my samba printer sharename (I don't think it says that anywhere in any HOWTO, correct me if I'm wrong though) I am now getting to the printer resource but... Using Samba 3.0.1 and attempting to connect to a samba cups printer with Win2000 I am getting the following samba error: Returning domain sid for domain TESTDOM - S-1-5-21-4236639219-957987792-2344320348 [2003/11/04 21:48:54, 2] rpc_server/srv_samr_nt.c:_samr_lookup_domain(2537) Returning domain sid for domain TESTDOM - S-1-5-21-4236639219-957987792-2344320348 [2003/11/04 21:48:54, 0] rpc_server/srv_util.c:get_domain_user_groups(371) get_domain_user_groups: primary gid of user [douglas] is not a Domain group ! get_domain_user_groups: You should fix it, NT doesn't like that The DC is a samba machine and I am running winbind on it. Do I need to create a domain group through samba or something? Thanks DSP SMB.conf: [global] workgroup = TESTDOM netbios name = blue security = user server string = Samba Server winbind separator = + idmap uid = 1-2 winbind gid = 1-2 winbind enum users = yes winbind enum groups = yes printcap name = /etc/printcap load printers = yes log file = /var/log/samba.log log level = 2 max log size = 5 add machine script = /usr/sbin/useradd -n -g machines -c Machine -d /dev/null -s /bin/false %u add user script = /usr/sbin/useradd %u socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 local master = Yes os level = 65 domain master = yes preferred master = yes domain logons = yes admin users = root csc policy = disable logon script = logon.bat logon path = \\%L\profiles\%U logon drive = H: printer admin = root printing = cups printcap name = cups username map = /etc/maps [netlogon] comment = Network Logon Service path = /home/netlogon guest ok = yes writable = no create mask = 0600 directory mask = 0700 ; share modes = no # Un-comment the following to provide a specific roving profile share # the default is to use the user's home directory [profiles] path = /home/profiles browseable = no guest ok = no create mask = 0600 directory mask = 0700 writable = yes [printers] comment = All Printers path = /var/spool/samba browseable = yes # Set public = yes to allow user 'guest account' to print guest ok = yes writable = yes public = yes printable = yes printer admin = root, douglas [hp7xxx] comment = Printer with Restricted Access path = /var/spool/samba_my_printer printer admin = root, douglas browseable = yes printable = yes writeable = yes guest ok = yes -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] cups printing questions
hi, i have a red hat linux 9.0 machine as file and printer server. on this machine i have samba 2.2.8a cups 1.1.19 for printing esp ghostscript 7.07.1 ghostscript-fonts-std 6.0 hpijs 1.5 it took me two weeks of work for setting up everything. now the printers works fine from cups by ppd files and ghostscript. printer driver autodownload works too with adobe postscript driver. so everything works fine except one thing. (and i have an other question too) when i try to print multiple pages from a windows client (for example from microsoft word) it only prints one page. in page_log i found the following entry: HP2100M ematos 94 [21/Oct/2003:15:27:21 +0200] 1 2 - localhost so it sais that 2 coipes have been printed but no. only one. but when i set to print 2 copies in the printer drivers option tab than 2 copies are printed. but why it do not works from the print panel only from driver details? and the other question: for every print jobs the following lines appears in the error_log file; -- error_log -- D [21/Oct/2003:08:18:43 +0200] [Job 11] perl: warning: Setting locale failed. D [21/Oct/2003:08:18:43 +0200] [Job 11] perl: warning: Please check that your locale settings: D [21/Oct/2003:08:18:43 +0200] [Job 11] LANGUAGE = (unset), D [21/Oct/2003:08:18:43 +0200] [Job 11] LC_ALL = (unset), D [21/Oct/2003:08:18:43 +0200] [Job 11] LANG = en D [21/Oct/2003:08:18:43 +0200] [Job 11] are supported and installed on your system. -- error_log -- what does this lines mean? how can i fix it? thanks a lot; attila mesterhazy -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] CUPS/Printing
RH Linux 9 on AMD k6-2 500 Using HP deskjet 930c on USB Samba version: 2.2.7a cups version: 1.1.18 Hello - I have had a good look on this newsgroup - and what I've picked up I think is allowing me to ask these questions more intelligently. I've also had a good look at the CUPS documentation aswell as the Samba documentation. 1. Am I correct is assuming that CUPS only likes postscript, and to print to a non postscript printer you have to use filters? 2. I have set up my HP deskjet 930c on RedHat 9 with cups. It prints just fine. However I cannot use the share from Windows machines using a 930c driver. I get this error in the cups error log: E [14/Aug/2003:00:20:24 +0100] print_job: Unsupported format 'application/octet-stream'! I [14/Aug/2003:00:20:24 +0100] Hint: Do you have the raw file printing rules enabled? So, is enabling raw printing a good idea, and if so - how do I do it (for ALL jobs) Using a lower driver such as deskjet 560c or digital turboserver 20 (a postscript driver) works fine (but for obvious reasons this is not ideal). Selecting print directly to the printer(raw) in windows gives the same error (I didnt expect that to work) 3. I've read a lot about people enabling autodownload of drivers and the many problems they are having. I'm afraid I don't properly understand the concept. Are these just normal Windows drivers? If so what would be the point for me as the 930c drivers don't work. OR Are there special CUPS windows drivers that know how to send something that is 930c ish but not an octet stream. I've read references to installing special drivers in windows but I haven't understood what is going on. Apologies if these questions sound stupid - I have included below the top bit of my deskjet.ppd file that I think Red Hat has generated. This (apparently) provides lots of info on the ppd in use and printer languages and so on. Any help would be very very much appreciated matt -- *FormatVersion: 4.3 *FileVersion: 1.1 *LanguageVersion: English *LanguageEncoding: ISOLatin1 *PCFileName:HPIJS.PPD *Manufacturer: HEWLETT-PACKARD *Product: DESKJET 930C *cupsVersion: 1.0 *cupsManualCopies: True *cupsModelNumber: 2 *cupsFilter:application/vnd.cups-postscript 0 cupsomatic *ModelName: HP DeskJet 930C, Foomatic + hpijs *NickName: HP DeskJet 930C, Foomatic + hpijs *ShortNickName: HP DeskJet 930C *PSVersion: (3010.000) 550 *PSVersion: (3010.000) 651 *PSVersion: (3010.000) 652 *PSVersion: (3010.000) 653 *PSVersion: (3010.000) 704 *PSVersion: (3010.000) 705 *LanguageLevel: 3 *ColorDevice: True *DefaultColorSpace: RGB *FileSystem:False *Throughput:1 *LandscapeOrientation: Plus90 *VariablePaperSize: False *TTRasterizer: Type42 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.510 / Virus Database: 307 - Release Date: 14/08/2003 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Samba/CUPS Printing from Windows
I've got a Samba server that is acting as a member server in a Windows NT Domain. I enabled CUPS printing yesterday and have shared the 4 printers to the domain. I then added the printers onto a Windows 2000 client, and can print just fine to any of them. But I have two problems (read annoyances): 1). When I look at any of the printers from Windows (i.e. Control Panel/Printers) I can see the Samba supplied network printers, but when I click on any of them I see a Status of Access denied, unable to connect. on the left hand side of the printers window. 2). Because of No. 1 (I think) when I double-click on a network printer, I can't see any of the jobs in the queue for that printer as I should. Anyone ran into these issues before? I have included the smb.conf below for inspection. I'm running Red Hat 8.0, Samba 2.2.7, CUPS 1.1.17. [global] workgroup = NESBITT_LEX netbios name = valykyrie server string = Linux Backup/Print Server log file = /var/log/samba/%m.log max log size = 50 security = domain password server = file-server1 print-server encrypt passwords = yes smb passwd file = /etc/samba/smbpasswd unix password sync = Yes passwd program = /usr/bin/passwd %u passwd chat = *New*password* %n\n *Retype*new*password* %n\n \ *passwd:*all*authentication*tokens*updated*successfully* pam password change = yes obey pam restrictions = yes socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 local master = no os level = 0 domain master = no preferred master = no domain logons = no wins server = 10.200.8.3 dns proxy = no winbind separator = + winbind uid = 1-2 winbind gid = 1-2 winbind cache time = 10 winbind enum users = yes winbind enum groups = yes winbind use default domain = yes template shell = /bin/bash template homedir = /home/%U printing = cups printcap name = cups load printers = yes #=== Share Definitions = [printers] comment = All Printers path = /var/spool/samba public = yes guest ok = yes writeable = no printable = yes [homes] comment = Home Directories browseable = no writable = yes valid users = %S create mode = 0664 directory mode = 0775 [backup] comment = Backup Files from Last Night path = /backup browsable = yes writeable = yes valid users = names deleted for security reasons create mode = 0777 directory mode = 0777 [cdburn] comment = Files to be written to CD path = /cdburn browsable = yes writeable = yes -- Kevin L. Collins, MCSE Systems Manager Nesbitt Engineering, Inc. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Cups printing works but status is always Access Denied
I have a RedHat 9 installation running XFS.
Cups 1.1.17-13 is installed
I have compiled and installed Samba 2.2.8a and everything appears to be
working apart from a minor printing problem.
After I have installed a printer on my Win2K workstation I can print via
samba to the cups printer using the windows PCL print driver and it works
fine.
However the printer status is always 'Access denied, unable to connect'.
I get the following entries in the log file for my machine :-
[2003/06/10 12:28:24, 0] printing/print_cups.c:cups_printername_ok(388)
Unable to get printer status for
::{2227a280-3aea-1069-a2de-08002b30309d} - client-error-not-found
[2003/06/10 12:28:24, 0] smbd/service.c:make_connection(252)
gb-desktop (192.168.1.250) couldn't find service
::{2227a280-3aea-1069-a2de-08002b30309d}
My samba configuration :-
[global]
workgroup = ASCOT
netbios name = DIBBLER
server string = SAMBA-LDAP PDC Server
encrypt passwords = Yes
passwd program = /usr/local/sbin/smbldap-passwd.pl -o %u
passwd chat = *new*password* %n\n *new*password* %n\n *successfully*
unix password sync = Yes
log file = /var/log/samba/%m.log
log level = 5 ; remember to lower the log level in real life :-)
max log size = 0
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
domain logons = Yes
os level = 80
preferred master = False
domain master = True
dns proxy = No
wins support = Yes
; SAMBA-LDAP declarations
ldap suffix = dc=ASCOT.WEBSCREEN-TECHNOLOGY,dc=COM
ldap admin dn = cn=Manager,dc=ASCOT.WEBSCREEN-TECHNOLOGY,dc=COM
ldap port = 389
ldap server = 127.0.0.1
ldap ssl = No
load printers = yes
printing = cups
printcap name = cups
; Deactivate opportunistic locks (wised)
; opLocks = False
; encoding to french
; character set = iso8859-1
; using smbldap-tools to add machines
add user script = /usr/local/sbin/smbldap-useradd.pl -w %u
; users and groups allowed to be 'Domain Admins'
domain admin group = @Domain Admins
[homes]
comment = Home Directories
valid users = %S
read only = No
create mask = 0664
directory mask = 0775
browseable = No
[netlogon]
comment = Network Logon Service
path = /usr/local/samba/netlogon
guest ok = Yes
[profiles]
path = /data/profiles
writeable = yes
browseable = no
create mode = 0644
directory mode = 0755
guest ok = yes
[samba]
path=/data/samba
writable= yes
force create mode = 660
force directory mode= 770
create mode = 660
directory mode = 770
mangle case = yes
case sensitive = no
default case= lower
preserve case = yes
short preserve case = no
valid users = @users
force group = users
[printers]
comment = All Printers
path = /var/spool/samba
printable = Yes
browseable = No
public = yes
guest ok = yes
writable = no
printer admin = root
--
Gareth Blades
Webscreen Technology
Index House
St Georges Lane
Ascot, Berkshire
SL5 7EU, UK
Tel +44 (0) 1344 636339
http://www.webscreen-technology.com
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Cups printing works but status is always AccessDenied
Sounds like you need the use client driver = yes hack in smb.conf, or preferably, look into setting up print$ and automatic driver download. man smb.conf for use client driver explains what appears to be your problem in some detail. Good luck, ~ Daniel After I have installed a printer on my Win2K workstation I can print via samba to the cups printer using the windows PCL print driver and it works fine. However the printer status is always 'Access denied, unable to connect'. --- This message is the property of Time Inc. or its affiliates. It may be legally privileged and/or confidential and is intended only for the use of the addressee(s). No addressee should forward, print, copy, or otherwise reproduce this message in any manner that would allow it to be viewed by any individual not originally listed as a recipient. If the reader of this message is not the intended recipient, you are hereby notified that any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is strictly prohibited. If you have received this communication in error, please immediately notify the sender and delete this message. Thank you. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
re: [Samba] Cups printing works but status is always Access Denied
I use Cups here and the install has been with out fail. Some oddities with XP but I
figure that is cause I am not forking the doe out, no worries thou, it all works
fabulously well. I have Caldera 3.1.1 with CUPS 1.1.19. Also with the smb
My suggestion is to use these settings:
[global]
printer admin = karl
printing = cups
printcap name = lpstat (this is the proper one per some cups document I read)
load printers = yes
[printers]
comment = All Printers
path = /var/spool/samba
guest ok = yes
browseable = no
public = yes
writable = no
printable = yes
printer admin = (user or @group name)
If you would like to add drivers put this in:
[print$]
comment = Printer Drivers
path = /etc/samba.d/drivers (path were driver will be located)
guest ok = no
write list = (user or @group name)
writable = no
browsable = yes
Review this for the right directories to setup and the cool cups utility to add
drivers. A little time is required and so smooth when done.
http://us2.samba.org/samba/docs/man/Samba-HOWTO-Collection.html#CUPS
Hope that assists you.
Karl-
I have a RedHat 9 installation running XFS.
Cups 1.1.17-13 is installed
I have compiled and installed Samba 2.2.8a and everything appears to be
working apart from a minor printing problem.
After I have installed a printer on my Win2K workstation I can print via
samba to the cups printer using the windows PCL print driver and it works
fine.
However the printer status is always 'Access denied, unable to connect'.
I get the following entries in the log file for my machine :-
[2003/06/10 12:28:24, 0] printing/print_cups.c:cups_printername_ok(388)
Unable to get printer status for
::{2227a280-3aea-1069-a2de-08002b30309d} - client-error-not-found
[2003/06/10 12:28:24, 0] smbd/service.c:make_connection(252)
gb-desktop (192.168.1.250) couldn't find service
::{2227a280-3aea-1069-a2de-08002b30309d}
My samba configuration :-
[global]
workgroup = ASCOT
netbios name = DIBBLER
server string = SAMBA-LDAP PDC Server
encrypt passwords = Yes
passwd program = /usr/local/sbin/smbldap-passwd.pl -o %u
passwd chat = *new*password* %n\n *new*password* %n\n *successfully*
unix password sync = Yes
log file = /var/log/samba/%m.log
log level = 5 ; remember to lower the log level in real life :-)
max log size = 0
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
domain logons = Yes
os level = 80
preferred master = False
domain master = True
dns proxy = No
wins support = Yes
; SAMBA-LDAP declarations
ldap suffix = dc=ASCOT.WEBSCREEN-TECHNOLOGY,dc=COM
ldap admin dn = cn=Manager,dc=ASCOT.WEBSCREEN-TECHNOLOGY,dc=COM
ldap port = 389
ldap server = 127.0.0.1
ldap ssl = No
load printers = yes
printing = cups
printcap name = cups
; Deactivate opportunistic locks (wised)
; opLocks = False
; encoding to french
; character set = iso8859-1
; using smbldap-tools to add machines
add user script = /usr/local/sbin/smbldap-useradd.pl -w %u
; users and groups allowed to be 'Domain Admins'
domain admin group = @Domain Admins
[homes]
comment = Home Directories
valid users = %S
read only = No
create mask = 0664
directory mask = 0775
browseable = No
[netlogon]
comment = Network Logon Service
path = /usr/local/samba/netlogon
guest ok = Yes
[profiles]
path = /data/profiles
writeable = yes
browseable = no
create mode = 0644
directory mode = 0755
guest ok = yes
[samba]
path=/data/samba
writable= yes
force create mode = 660
force directory mode= 770
create mode = 660
directory mode = 770
mangle case = yes
case sensitive = no
default case= lower
preserve case = yes
short preserve case = no
valid users = @users
force group = users
[printers]
comment = All Printers
path = /var/spool/samba
printable = Yes
browseable = No
public = yes
guest ok = yes
writable = no
printer admin = root
--
Gareth Blades
Webscreen Technology
Index House
St Georges Lane
Ascot, Berkshire
SL5 7EU, UK
Tel +44 (0) 1344 636339
http://www.webscreen-technology.com
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] cups printing and user names from trusted domains
On Sat, 2003-03-08 at 06:51, Andrew Bartlett wrote: On Sat, 2003-03-08 at 04:12, Wolfgang Ratzka wrote: -BEGIN PGP SIGNED MESSAGE- Im currently running some tests for a samba/CUPS based print server. The print server is a member of an NT domain and uses winbind to import NT domain users. Users accessing the print server will be not from the same domain but from trusted domains. Everything basically seems to work, once you use sufficiently new versions of cups and samba. (I'm on Debian woody, so I needed to get the 2.2.7a debs from samba.org, and cupsys-* 1.1.18-2 from Debian unstable to get a version of cupsaddsmb that actually works.) One remaining problem is that the print jobs show up in the CUPS queue as owned by user instead of domain\user. Moreover, print jobs submitted by domain1\user1 can be deleted by another user domain2\user1 who has the same user name in a different trusted domain. Am I doing something wrong? I remember vaguely, that during the first stage of my experiments (maybe with an older version of the cupsys packages), some printjobs showed up with a qualified name domain\user. I'll see what I can do to make them show up as the unix username used for login. This will be in HEAD, and will mean that they use the name in the form 'domain\username' if you used winbind or 'username' if you didn't. (Effectively). I've looked into this, and it looks like our CUPS printing is quite broken in this respect. The first thing I noticed is the lack of error handling we don't pass the error back to the client when the printing fails. However, when looking at the code in relation to your problem, I noticed that we send completely the wrong username to CUPS. For both the print job's submission, and later attempts to cancel or pause a job, we send the *original* 'smb_name'. This is the unqualified username of the user that originally sent the job, before any mapping. The correct thing to send would be the unix name - possibly directly from current_user, but I need to check on this. Jerry - can you put your eye to this? From inside the print subsystem, what is the correct way to get the current unix username? Andrew Bartlett -- Andrew Bartlett [EMAIL PROTECTED] Manager, Authentication Subsystems, Samba Team [EMAIL PROTECTED] Student Network Administrator, Hawker College [EMAIL PROTECTED] http://samba.org http://build.samba.org http://hawkerc.net signature.asc Description: This is a digitally signed message part -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] cups printing and user names from trusted domains
Andrew Bartlett wrote on Samba-Digest: [Samba] cups printing and user names from trusted domains Andrew Bartlett abartlet at samba.org Sat Mar 8 21:46:01 GMT 2003 On Sat, 2003-03-08 at 06:51, Andrew Bartlett wrote: On Sat, 2003-03-08 at 04:12, Wolfgang Ratzka wrote: -BEGIN PGP SIGNED MESSAGE- Im currently running some tests for a samba/CUPS based print server. The print server is a member of an NT domain and uses winbind to import NT domain users. Users accessing the print server will be not from the same domain but from trusted domains. Everything basically seems to work, once you use sufficiently new versions of cups and samba. (I'm on Debian woody, so I needed to get the 2.2.7a debs from samba.org, and cupsys-* 1.1.18-2 from Debian unstable to get a version of cupsaddsmb that actually works.) One remaining problem is that the print jobs show up in the CUPS queue as owned by user instead of domain\user. Moreover, print jobs submitted by domain1\user1 can be deleted by another user domain2\user1 who has the same user name in a different trusted domain. Am I doing something wrong? I remember vaguely, that during the first stage of my experiments (maybe with an older version of the cupsys packages), some printjobs showed up with a qualified name domain\user. I'll see what I can do to make them show up as the unix username used for login. This will be in HEAD, and will mean that they use the name in the form 'domain\username' if you used winbind or 'username' if you didn't. (Effectively). I've looked into this, and it looks like our CUPS printing is quite broken in this respect. The first thing I noticed is the lack of error handling we don't pass the error back to the client when the printing fails. However, when looking at the code in relation to your problem, I noticed that we send completely the wrong username to CUPS. For both the print job's submission, and later attempts to cancel or pause a job, we send the *original* 'smb_name'. This is the unqualified username of the user that originally sent the job, before any mapping. The correct thing to send would be the unix name - possibly directly from current_user, but I need to check on this. Hmmm... I'm not so sure this is what most people would desire. CUPS logs the names in question, for example in its page_log for accounting purposes. If we serve Windows clients, and if we now and then want to evaluated the page_log and create statistics and reports from it -- is it the Unix name or the Windows user name we want to appear there? Jerry - can you put your eye to this? From inside the print subsystem, what is the correct way to get the current unix username? Andrew Bartlett Cheers, Kurt -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] cups printing and user names from trusted domains
On Sat, 2003-03-08 at 06:51, Andrew Bartlett wrote: On Sat, 2003-03-08 at 04:12, Wolfgang Ratzka wrote: -BEGIN PGP SIGNED MESSAGE- Im currently running some tests for a samba/CUPS based print server. The print server is a member of an NT domain and uses winbind to import NT domain users. Users accessing the print server will be not from the same domain but from trusted domains. Everything basically seems to work, once you use sufficiently new versions of cups and samba. (I'm on Debian woody, so I needed to get the 2.2.7a debs from samba.org, and cupsys-* 1.1.18-2 from Debian unstable to get a version of cupsaddsmb that actually works.) One remaining problem is that the print jobs show up in the CUPS queue as owned by user instead of domain\user. Moreover, print jobs submitted by domain1\user1 can be deleted by another user domain2\user1 who has the same user name in a different trusted domain. Am I doing something wrong? I remember vaguely, that during the first stage of my experiments (maybe with an older version of the cupsys packages), some printjobs showed up with a qualified name domain\user. I'll see what I can do to make them show up as the unix username used for login. This will be in HEAD, and will mean that they use the name in the form 'domain\username' if you used winbind or 'username' if you didn't. (Effectively). I've looked into this, and it looks like our CUPS printing is quite broken in this respect. The first thing I noticed is the lack of error handling we don't pass the error back to the client when the printing fails. However, when looking at the code in relation to your problem, I noticed that we send completely the wrong username to CUPS. For both the print job's submission, and later attempts to cancel or pause a job, we send the *original* 'smb_name'. This is the unqualified username of the user that originally sent the job, before any mapping. The correct thing to send would be the unix name - possibly directly from current_user, but I need to check on this. Jerry - can you put your eye to this? From inside the print subsystem, what is the correct way to get the current unix username? Andrew Bartlett -- Andrew Bartlett [EMAIL PROTECTED] Manager, Authentication Subsystems, Samba Team [EMAIL PROTECTED] Student Network Administrator, Hawker College [EMAIL PROTECTED] http://samba.org http://build.samba.org http://hawkerc.net signature.asc Description: This is a digitally signed message part
[Samba] cups printing and user names from trusted domains
-BEGIN PGP SIGNED MESSAGE- Im currently running some tests for a samba/CUPS based print server. The print server is a member of an NT domain and uses winbind to import NT domain users. Users accessing the print server will be not from the same domain but from trusted domains. Everything basically seems to work, once you use sufficiently new versions of cups and samba. (I'm on Debian woody, so I needed to get the 2.2.7a debs from samba.org, and cupsys-* 1.1.18-2 from Debian unstable to get a version of cupsaddsmb that actually works.) One remaining problem is that the print jobs show up in the CUPS queue as owned by user instead of domain\user. Moreover, print jobs submitted by domain1\user1 can be deleted by another user domain2\user1 who has the same user name in a different trusted domain. Am I doing something wrong? I remember vaguely, that during the first stage of my experiments (maybe with an older version of the cupsys packages), some printjobs showed up with a qualified name domain\user. Kind regards, Wolfgang Ratzka - smb.conf--- [global] ~ workgroup = MYDOMAIN ~ server string = %h print server running samba %v ~ load printers = yes ~ printcap name = cups ~ printing = cups ~ printer admin = @MYDOMAIN\Druck-Admins ~ admin users = @MYDOMAIN\Druck-Admins ~ guest account = nobody ~ log file = /var/log/samba/log.%m ~ max log size = 1000 ~ syslog = 0 ~ security = domain ~ password server = * ~ encrypt passwords = true ~ socket options = TCP_NODELAY ~ wins server = edited out ~ dns proxy = no ~ passwd program = /usr/bin/passwd %u ~ passwd chat = *Enter\snew\sUNIX\spassword:* %n\n *Retype\snew\sUNIX\spassword:* %n\n . ~ obey pam restrictions = yes ~ winbind uid = 1-6 ~ winbind gid = 1-6 ~ character set = ISO8859-1 ~ client code page = 850 [printers] ~ comment = All Printers ~ browseable = yes ~ path = /tmp ~ printable = yes ~ public = no ~ writable = no ~ create mode = 0700 ~ printer admin = @MYDOMAIN\Druck-Admins [print$] ~ comment = Printer Drivers ~ path = /var/lib/samba/drivers ~ browseable = yes ~ guest ok = no ~ read only = yes ~ write list = @MYDOMAIN\Druck-Admins ~ create mask = 0755 ~ directory mask = 0755 - -- Wolfgang Ratzka Phone: +49 6421 2823531 FAX: +49 6421 2826994 Uni Marburg, HRZ, Hans-Meerwein-Str., D-35032 Marburg, Germany ~ http://www.uni-marburg.de/hrz/mitarbeiter/ratzka.html -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQEVAwUBPmjTFRwiO5rz0xULAQHiZwf9HH6OcbQHGF9kUnveS+JEDIauoBYQeBb0 bMgOe60CnKzhKt0+aRHVdBaK2hzQ+x66NdtmW3nPmmSvChqCzeY/plMcFPnxFN02 PA8h1ycD9dfAjVoMLr/+XZkTvpEKz5tXlZFg5WuSreBMYfA+MNZ11VXvLk2W6Y9N O9ReJFbZNJzvKrjOKNUODzsfMIljzBzvRGDgKotrnXZM5ytlIkofWKnfKmmYU58i sdBZRrSBjn/x5CHDOdC2i8Tv/uRTFW1CDJCxb1ow6DKSue2rrrjTKhQZlyLqVBEO yQD+X/LqAsrnXkC8GhWOBeHZb28f4CcgGMAmmf/N6lmbgMjRua3SSg== =NLPa -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] cups printing and user names from trusted domains
On Sat, 2003-03-08 at 04:12, Wolfgang Ratzka wrote: -BEGIN PGP SIGNED MESSAGE- Im currently running some tests for a samba/CUPS based print server. The print server is a member of an NT domain and uses winbind to import NT domain users. Users accessing the print server will be not from the same domain but from trusted domains. Everything basically seems to work, once you use sufficiently new versions of cups and samba. (I'm on Debian woody, so I needed to get the 2.2.7a debs from samba.org, and cupsys-* 1.1.18-2 from Debian unstable to get a version of cupsaddsmb that actually works.) One remaining problem is that the print jobs show up in the CUPS queue as owned by user instead of domain\user. Moreover, print jobs submitted by domain1\user1 can be deleted by another user domain2\user1 who has the same user name in a different trusted domain. Am I doing something wrong? I remember vaguely, that during the first stage of my experiments (maybe with an older version of the cupsys packages), some printjobs showed up with a qualified name domain\user. I'll see what I can do to make them show up as the unix username used for login. This will be in HEAD, and will mean that they use the name in the form 'domain\username' if you used winbind or 'username' if you didn't. (Effectively). Andrew Bartlett -- Andrew Bartlett [EMAIL PROTECTED] Manager, Authentication Subsystems, Samba Team [EMAIL PROTECTED] Student Network Administrator, Hawker College [EMAIL PROTECTED] http://samba.org http://build.samba.org http://hawkerc.net signature.asc Description: This is a digitally signed message part -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Samba/CUPS printing again
Hello...again...Y'all are getting sick of me, aren't ya? ;) Anyway, I am having quite the dilemna about printing. I'm using samba 2.2.7a aong with cups-1.1.5. I know this is an old version of cups, but this is a production server and I don't want to fool with it yet. Anyway, we have 2 printers: HP laser Jet 4 Plus and an Office Jet R80. each are running off a jet direct. One is located in address x.x.x.32, the other in x.x.x.38. We can print to the laserjet without a problem. However, we are completely unable to print to the office jet. I can print a test page from teh CUPS web GUI and from the bash prompt from the server box itself. However, when anything is sent from windows, it never prints. There's no record of it ever reaching the que. I'm not sure where to look for info. it's acting like the windows machine are not sending the print files to the Cups que. It never hits the page_log as a job. When I look at the properties of the printer, the samba printer port is not checked. When I check it and hit apply, it tells Printer settings could not be saved. Access denied My network username is part of the root group, and I've set the printer admin and domain admin to include it, so I should have the rights to do whatever I want. Does anyone have any ideas how I can fix this? as a side not, does anyone happen to have an enumports script that I can use? I'm not a script writer, so I would have any idea where to start. Thanks in advance...again ;) Darin Bawden, Technical Support Spectrum Software, Inc (615) 333-1900 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Samba/CUPS printing again
Darin Bawden wrote on Samba-Digest: [Samba] Samba/CUPS printing again Darin Bawden [EMAIL PROTECTED] Fri Jan 10 00:42:19 2003 Hello...again...Y'all are getting sick of me, aren't ya? ;) Anyway, I am having quite the dilemna about printing. I'm using samba 2.2.7a aong with cups-1.1.5. First off: this is a very old CUPS. It was released in Autumn 2000. I know this is an old version of cups, but this is a production server and I don't want to fool with it yet. But you do -- running such an old version of CUPS with the most recent version of Samba ;-) Anyway, we have 2 printers: HP laser Jet 4 Plus and an Office Jet R80. each are running off a jet direct. One is located in address x.x.x.32, the other in x.x.x.38. We can print to the laserjet without a problem. Which driver do you use here? Is it locally installed on the clients? However, we are completely unable to print to the office jet. Which driver do you use? Which Win OS versions are the clients? Do they use the HP driver? Is CUPS spooling the files as raw? What does the CUPS error_log say? Did you set LogLevel debug in CUPS and restart cupsd to get a more verbose output? I can print a test page from teh CUPS web GUI and from the bash prompt from the server box itself. The testpage is PostScript and therefor is nearly guaranteed to get rendered and printed OK. However, when anything is sent from windows, it never prints. What the Windows driver sends is unknown. In CUPS-speak, it is of MIME type application/octet-stream. And this MIME type is disabled by default. See if you have in *both* files, /etc/cups/mime.types|convs, on the last line the # removed. Then try again. If the problem persists, see in the error_log for hints (not the page_log) There's no record of it ever reaching the que. Windows clients print into the receiving queue of Samba (probably /var/spool/samba/). See if anything arrives here. If not, it is a pure Samba problem at this stage. If yes, investigate why it doesn't get passed to the CUPS queue (probably /var/spool/cups/), or why it doesn't get processed there. I'm not sure where to look for info. There is a a lot of docu at http://localhost:631/documentation.html; man -k cups should also list all relevant man pages. The Release Notes at http://www.linuxprinting.org/ contain 2 arguments on every single line why you should upgrade (there might be half an argument per section why you could stay were you are... ;-) it's acting like the windows machine are not sending the print files to the Cups que. Verify this by looking in the Samba log first. Also, did you know you can change the Samba debug level on the fly by giving smbcontrol smbd debuglevel your choice from 0 to 100 ?? (My advice: try 3 first, or you'll be drowned in messages) Also: which printing releted settings are you using in smb.conf? It never hits the page_log as a job. When I look at the properties of the printer, the samba printer port is not checked. When I check it and hit apply, it tells Printer settings could not be saved. Access denied My network username is part of the root group, and I've set the printer admin and domain admin to include it, so I should have the rights to do whatever I want. Yes you should But have you verified that this is what Samba sees you as? Try smbstatus to see which credentials XP really presents to Samba. Does anyone have any ideas how I can fix this? as a side not, does anyone happen to have an enumports script that I can use? I'm not a script writer, so I would have any idea where to start. Thanks in advance...again ;) Darin Bawden, Technical Support Spectrum Software, Inc (615) 333-1900 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] CUPS printing problem under Samba 2.2.7
Hi, I've just downloaded and installed samba 2.2.7 with these options; ./configure \ --prefix=/usr \ --libdir=/etc \ --with-lockdir=/var/lock/samba \ --with-privatedir=/etc/samba \ --with-pam \ --with-winbind \ --with-swatdir=/usr/share/swat \ --with-pam \ --with-mmap \ --enable-cups \ --with-logfilebase=/var/log/samba \ --with-smbmount \ --sysconfdir=/etc/samba \ --with-piddir=/var/run/samba As you can see, I turned on cups support in samba configuration. I have the cups libraries also; # rpm -qa|grep cups cups-1.1.15-10 cups-libs-1.1.15-10 # ldconfig -v|grep cups libcups.so.2 - libcups.so.2 libcupsimage.so.2 - libcupsimage.so. But after make, and make install I don't see cups among the supported libraries in smbd; # ldd /usr/sbin/smbd libdl.so.2 = /lib/libdl.so.2 (0x4001f000) libnsl.so.1 = /lib/libnsl.so.1 (0x40023000) libpam.so.0 = /lib/libpam.so.0 (0x40038000) libpopt.so.0 = /usr/lib/libpopt.so.0 (0x4004) libc.so.6 = /lib/i686/libc.so.6 (0x4200) /lib/ld-linux.so.2 = /lib/ld-linux.so.2 (0x4000) I don't know what should I do. I think this is the reason why I don't see the printers under samba server from our clients... Could you help me please, what am I missed? Thank in advance! Regards; Istvan _ The new MSN 8: advanced junk mail protection and 2 months FREE* http://join.msn.com/?page=features/junkmail -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] CUPS printing problem under Samba 2.2.7
Istvan, You need to install the package cups-devel for your Linux distro. Then you can build samba with cups support. - John T. On Sun, 1 Dec 2002, YYyyy XXxxx wrote: Hi, I've just downloaded and installed samba 2.2.7 with these options; # rpm -qa|grep cups cups-1.1.15-10 cups-libs-1.1.15-10 # ldconfig -v|grep cups libcups.so.2 - libcups.so.2 libcupsimage.so.2 - libcupsimage.so. But after make, and make install I don't see cups among the supported libraries in smbd; # ldd /usr/sbin/smbd libdl.so.2 = /lib/libdl.so.2 (0x4001f000) libnsl.so.1 = /lib/libnsl.so.1 (0x40023000) libpam.so.0 = /lib/libpam.so.0 (0x40038000) libpopt.so.0 = /usr/lib/libpopt.so.0 (0x4004) libc.so.6 = /lib/i686/libc.so.6 (0x4200) /lib/ld-linux.so.2 = /lib/ld-linux.so.2 (0x4000) I don't know what should I do. I think this is the reason why I don't see the printers under samba server from our clients... Could you help me please, what am I missed? - John T. -- John H Terpstra Email: [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] CUPS printing
Someone calling himself linuxpower adviced on this list: Message: 2 Date: Thu, 14 Nov 2002 07:30:18 +0100 (CET) From: =?iso-8859-1?q?linux=20power?= [EMAIL PROTECTED] Subject: Re: [Samba] CUPS printing To: [EMAIL PROTECTED] --0-1567453496-1037255418=:2514 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Replace -P %p in the print command line with the absolute path to the printer. Bug in samba. Hi, linuxpower, I have read your repeated advice on this list to use the absolute path to the printer inside the print command. On other occasions you talked about an absolute path to a printing device. I suppose, you mean the same thing with both your variants of your wording. Would you please be so kind to explain to me what you mean by these? Would you please give an example for an absolute path to the printer, for an absolute path to a printing device plus an example for the print command, as you imagine does work in the cases you advice to use it? Sorry, I can't make my mind up about this one. (I wouldn't mind about this -- but your advices leads to e-mails, directed to *my* mailbox, of people asking what the *~#?$§ this means...) Your talking in the context of CUPS about path to a device, makes it very likely to be mixed up with the clearly defined technical term device URI which CUPS uses. On one occasion, you have even given the specific advice Fix it by replacing -P %p with the absolute path to the printing device found in lpstat -v and on another one (Fri Oct 4 06:55:24 2002) you wrote There is a bug in samba which cannot resolve -P %p in the print command.Replace -P %p with the absolute path to the printer. Excuse me -- this advice is pure nonsense (while a bug in Samba might be there). Here are the reasons: lpstat -v on a CUPS based printing system gives something that is named a device URI in all relevant documentation. If it is the parallel:/dev/lp0 device-URI, one *could* assume to take the /dev/lp0 part as a path, even an absolute path. But what about device-URIs like lpd://10.160.51.131/PORT1 socket://hp-printer:9100 ipp://kde-cups-server/printers/infotec4105 ?? Would you also call //10.160.51.131/PORT1 or //hp-printer:9100 or //kde-cups-server/printers/infotec4105 an absolute path? CUPS does encode in the device-URI the protocol to be used for the communication with the printer plus something you might call absolute path to the device. You can't replace inside the Samba print command (in smbd.conf) the -P %p part by one of the quoted device URIs... Your creation and usage of the term of absolute path I found nowhere clearly defined -- it seems to only lead to utter confusion and urban legends... - About your conceived bug in Samba -- please consider this: There is also a hint in the smb.conf man page: ...*if* the setting is printing = cups and printcap = cups and ...*if* Samba is compiled against libcups, ...and *if* there is an entry in cupsd.conf to get CUPS to create a printcap file [Printcap /etc/printcap], then *any* print command setting in smb.conf will be *ignored*, as samba is then using a direct access to the CUPS API for printing This means: if the two simple settings printing = cups and printcap = cups don't work, you probably don't have a smbd which is compiled against libcups. To check, simply run as root ldd `which smbd` (on Linux, dunno about ldd on other Samba platforms). - Now for the original question Mark Belfanti [EMAIL PROTECTED] wrote: For printing from windows with windopws driver using cups you may need to reconfigure to have sups act as a raw print queue. See Chapter 7 of Samaba-HowTo-Collection. Regards, Mark On Thu, 2002-11-14 at 13:25, Darin Bawden wrote: Good evening everyone, Kist a quick-type question I hope. I've just switched my Linux server to use Cups instead of LPRng. I can print all day to our HP LaserJet 4 Plus. Hi, Mark, CUPS ships a well-working Laserjet driver. Install it (as root) with lpadmin -p laserjet4plus -v parallel:/dev/lp0 -E -m laserjet.ppd (The -m switch will retrieve the laserjet.ppd from the standard repository for not-yet-installed-PPDs, which CUPS keeps at /usr/share/cups/model/. Alter- natively, you may use -P /absolute/filesystem/path/to/where/there/is/PPD/your.ppd) You didn't state if the print system is working on the Linux side of things. Even if it does -- to print from Windows, invelves some more steps But let me first point out some more general things about printer drivers for Linux/Unix (yes, and for Mac OS X now!), be it you use CUPS or one of the venerable (I'd even call them ancient and rusty now...) printing systems. You -- and everybody else, for that matter -- should always also consult the database on linuxprinting.org for all recommendations about which driver is best used for which printer: http://www.linuxprinting.org
[Samba] cups printing and samba.
Hello, Are there any issues with using cups and samba together to export unix printers to windows clients? My situation i've got a fbsd print server with three printers attached to it, i'd like to export two of them, the system has cups on it for it's printing needs. Thanks. Dave. GET INTERNET ACCESS FROM JUNO! Juno offers FREE or PREMIUM Internet access for less! Join Juno today! For your FREE software, visit: http://dl.www.juno.com/get/web/. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
