Re: [Samba] samba printing problems
On Mon, Jan 12, 2009 at 06:30:33PM -0500, Lois Bennett wrote: > After struggling with this for a couple of days it's time to ask for help. > We have two samba servers one is on Solaris 8 running Version 2.2.8a > and one on Solaris 10 running Version 3.0.28 > > I am having a problem with samba printing from the Solaris 10 samba > server. I can print from the machine itself using lpr directly. I > can print from a windows machine using lpr printing to that server but > I can't get it to print using samba printing. The files seem to just > disappear. There is nothing queued. Perhaps the default print command isn't appropriate for Solaris 10? Check out the 'print command' setting in the smb.conf man page. It looks like the individual pieces are working correctly, they just aren't talking to each other. Dan -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] samba printing problems
Hi After struggling with this for a couple of days it's time to ask for help. We have two samba servers one is on Solaris 8 running Version 2.2.8a and one on Solaris 10 running Version 3.0.28 I am having a problem with samba printing from the Solaris 10 samba server. I can print from the machine itself using lpr directly. I can print from a windows machine using lpr printing to that server but I can't get it to print using samba printing. The files seem to just disappear. There is nothing queued. This is the top of my smb.conf [global] debug level = 3 #syslog = 10 #debug level = 1 syslog = 0 workgroup = PHS_WRKSTN comment = Channing Epi SMB Server printing = bsd printcap name = /etc/printcap.smb load printers = yes #log file = /var/samba/log/log.%m log file = /var/samba/log/%U.%m.log max log size = 10 preserve case = yes short preserve case = yes lock directory = /var/samba/locks locking = yes share modes = yes wins server = username map = /etc/sfw/smb.map hosts allow = ALL dead time = 0 wide links = no follow symlinks = no #smb passwd file = /var/samba/private/smbpasswd smb passwd file = /usr/local/smb/smbpasswd #update encrypted = yes #for this to work 'encrypt passwords = no' encrypt passwords = yes socket options = TCP_NODELAY IPTOS_LOWDELAY SO_KEEPALIVE SO_RCVBUF=8192 SO_SNDBUF=8192 time server = yes #null passwords = yes mangling method = hash2 hide dot files = yes #os level = 33 [ipc$] hosts allow = 13.174.18.,17.23.139.,10.,155.52.,127.0.0.1,10.240.5 hosts deny = ALL path = /tmp [printers] comment = Channing Lab Printers path = /var/samba/spool browseable = no printable = yes guest ok = no writable = no create mask = 0700 ... many pages worth of disk shares... Am I missing something obvious. I don't know too much about samba or Windows.I tried this: root # /ilocal/bin/smbclient //sambahost/glsr1 -U salbb Password: Domain=[NFSSRV2] OS=[Unix] Server=[Samba 3.0.28] smb: \> lcd /udd/salbb smb: \> print .login putting file .login as .login (10.4 kb/s) (average 10.4 kb/s) smb: \> queue smb: \> exit I have stopped the smbd completely and restarted it. Any suggestions will be very welcome. Thanks. Peace, Lois -- Lois Bennett, MSEE Senior System Administrator Channing Laboratory Brigham & Women's Hospital A Teaching Affiliate of Harvard Medical School and Harvard School of Public Health -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] printing problems
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Lutieri G. wrote: > This refers to an MS-RPC handle not a file descriptor. The > 1024 limit is hard coded in smbd ot prevent DoS attacks. > You'll need to determine which pipe this is actually > affected and which client is opening up so many handles > and why. > >> is there any way to do it?! A level 10 debug log will give you the detail to know which open call was refused. And breaking the logs out by client name (log file = /var/log/samba/log.%m) will show you which client is causing the problem. cheers, jerry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGVXtZIR7qMdg1EfYRAp8sAKCScWfYi604i1m67yjGQFdfX6JjZwCglJhB SUygMq9v6inmndaUs2sZvUM= =Cku6 -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] printing problems
2007/5/23, Gerald (Jerry) Carter <[EMAIL PROTECTED]>: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Lutieri G. wrote: > I'm using samba Version 3.0.24-1.fc5 with cups 1.2.8. I've 23 printers > installed and my clients are w2k and WinXP. > > This mornig i got in logs: > > [2007/05/23 10:35:16, 0] rpc_server/srv_lsa_hnd.c:create_policy_hnd(111) > create_policy_hnd: ERROR: too many handles (1025) on this pipe. > > After restart the samba service it works fine. This refers to an MS-RPC handle not a file descriptor. The 1024 limit is hard coded in smbd ot prevent DoS attacks. You'll need to determine which pipe this is actually affected and which client is opening up so many handles and why. is there any way to do it?! cheers, jerry = Samba--- http://www.samba.org Centeris --- http://www.centeris.com "What man is a man who does not make the world better?" --Balian -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGVFpYIR7qMdg1EfYRAmP+AKC9XCsI5nlSb9xoE9g1az/pAwKKJQCg15p3 iPGHOZCdW8+J0sKluWThFhE= =8eH+ -END PGP SIGNATURE- -- Att. Lutieri G. B. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] printing problems
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Lutieri G. wrote: > I'm using samba Version 3.0.24-1.fc5 with cups 1.2.8. I've 23 printers > installed and my clients are w2k and WinXP. > > This mornig i got in logs: > > [2007/05/23 10:35:16, 0] rpc_server/srv_lsa_hnd.c:create_policy_hnd(111) > create_policy_hnd: ERROR: too many handles (1025) on this pipe. > > After restart the samba service it works fine. This refers to an MS-RPC handle not a file descriptor. The 1024 limit is hard coded in smbd ot prevent DoS attacks. You'll need to determine which pipe this is actually affected and which client is opening up so many handles and why. cheers, jerry = Samba--- http://www.samba.org Centeris --- http://www.centeris.com "What man is a man who does not make the world better?" --Balian -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGVFpYIR7qMdg1EfYRAmP+AKC9XCsI5nlSb9xoE9g1az/pAwKKJQCg15p3 iPGHOZCdW8+J0sKluWThFhE= =8eH+ -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] printing problems
I'm using samba Version 3.0.24-1.fc5 with cups 1.2.8. I've 23 printers installed and my clients are w2k and WinXP. This mornig i got in logs: [2007/05/23 10:35:16, 0] rpc_server/srv_lsa_hnd.c:create_policy_hnd(111) create_policy_hnd: ERROR: too many handles (1025) on this pipe. After restart the samba service it works fine. # ulimit -n 1024 i don't find solution in samba archives. any suggestion? -- Att. Lutieri G. B. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: RE [Samba] Printing problems with samba 3.0.23c and NT4
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [EMAIL PROTECTED] wrote: > Hi, > > I have the same problem on a NT4 SP3. > > I must made a workaround (using direct print, without > pass by samba), but the problem still present. Just out of curiousity, why are you still running SP3 ? I'll try to test this later this week. If you haven't filed a bug report on it, please do so. Thanks. cheers, jerry = Samba--- http://www.samba.org Centeris --- http://www.centeris.com "What man is a man who does not make the world better?" --Balian -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFDd+yIR7qMdg1EfYRArDfAJ9xWB6qIxSxCNj0sCbpv1lfAY6UFgCfbXNV tyC2gmlytE0oHMlJhnovLRA= =ZFYZ -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
RE [Samba] Printing problems with samba 3.0.23c and NT4
Hi, I have the same problem on a NT4 SP3. I must made a workaround (using direct print, without pass by samba), but the problem still present. --- Stéphane PURNELLE [EMAIL PROTECTED] Service Informatique Corman S.A. Tel : 00 32 087/342467 [EMAIL PROTECTED] a écrit sur 13/09/2006 10:36:01 : > Hi everyone! > > I have upgrade my fileserver from samba2-smbpasswd to samba3.0.23c > with LDAP-PDC. > Now i can't print to the printers on that server with NT4. "net use > ..." is functional, but if I print to that printer, I get the > error - free translated from german message - "The syntax of the > filename, directory name or the disc-label is wrong." > > WinXP hasn't that problem. > The share is defined in this way: > > [global] > ... > printing = BSD > ... > [pspdf] > path = /tmp > printable = yes > print command = /usr/local/bin/samba2pdf %s %U > use client driver = yes > > I have played with "use client driver", with no success. > > Is the printing-support for NT4 broken? > > Thanks a lot in advance > > Andreas Pohl > [EMAIL PROTECTED] > -- > INTERMET Ueckermünde > D-17373 Ueckermünde, Eggesiner Str. 11 > Tel.: +49 (0) 39771 2120, Fax: +49 (0) 39771 21210 > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Printing problems with samba 3.0.23c and NT4
Hi everyone! I have upgrade my fileserver from samba2-smbpasswd to samba3.0.23c with LDAP-PDC. Now i can't print to the printers on that server with NT4. "net use ..." is functional, but if I print to that printer, I get the error - free translated from german message - "The syntax of the filename, directory name or the disc-label is wrong." WinXP hasn't that problem. The share is defined in this way: [global] ... printing = BSD ... [pspdf] path = /tmp printable = yes print command = /usr/local/bin/samba2pdf %s %U use client driver = yes I have played with "use client driver", with no success. Is the printing-support for NT4 broken? Thanks a lot in advance Andreas Pohl [EMAIL PROTECTED] -- INTERMET Ueckermünde D-17373 Ueckermünde, Eggesiner Str. 11 Tel.: +49 (0) 39771 2120, Fax: +49 (0) 39771 21210 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Printing problems with samba 3.0.23c and NT4
Hi everyone! I have upgrade my fileserver from samba2-smbpasswd to samba3.0.23c with LDAP-PDC. Now i can't print to the printers on that server with NT4. "net use ..." is functional, but if I print to that printer, I get the error - free translated from german message - "The syntax of the filename, directory name or the disc-label is wrong." WinXP hasn't that problem. The share is defined in this way: [global] ... printing = BSD ... [pspdf] path = /tmp printable = yes print command = /usr/local/bin/samba2pdf %s %U use client driver = yes I have played with "use client driver", with no success. Is the printing-support for NT4 broken? Thanks a lot in advance Andreas Pohl [EMAIL PROTECTED] -- INTERMET Ueckermünde D-17373 Ueckermünde, Eggesiner Str. 11 Tel.: +49 (0) 39771 2120, Fax: +49 (0) 39771 21210 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] printing problems upgrading samba from 2.2.4 to 3.0.14
Sorry .. The problem has been solved .. The Configuration that I posted was OK, but I did not remember to connect the new printer share: A new raw printer created under cups. I used the old printer share, with a driver loaded into cups, so, when MSDOS printed something, exit was unformatted . When you need raw printing, it's necessary to create a rew printer in cups, without any driver. I had created it, but I was not using it . Sorry . P.D.: I don't find anything about cups options=raw in Samba3-HOWTO but in man pages there is a good example. I don't use this parameter and things seem to work OK. - Original Message - From: "John H Terpstra" <[EMAIL PROTECTED]> To: ; <[EMAIL PROTECTED]> Sent: Saturday, August 27, 2005 4:15 PM Subject: Re: [Samba] printing problems upgrading samba from 2.2.4 to 3.0.14 On Saturday 27 August 2005 05:55, [EMAIL PROTECTED] wrote: I'm trying to upgrade samba from 2.2.4 to 3.0.14 version and I would like to use the same smb.conf that I had. But something looks wrong in printing system , there are a lot of new options and I don't know why my old parameters don't work .. The changes are documented in a chapter called "Upgrading Samba" in the book "The Official Samba3 HOWTO". Upgrade issues are discussed in the book "Samba-3 By Example", chapter 8. See http://www.samba.org/samba/docs/Samba3-HOWTO.pdf and http://www.samba.org/samba/docs/Samba3-ByExample.pdf I use samba through Windows XP/98/2000 and a MS-DOS program that sends print works to a linux machine with samba. With version 2.2.4 all seemed OK and worked fine. With version 3.0.14 printers don't work. I need raw printing. When Samba-3 has been compiled with the CUPS libraries, printing goes direct via the CUPS library API. To enable raw printing add the parameter "cups options = raw". For example, this line (print command = lpr-cups -P %p -o raw %s -r) doesn't work in new version. Do I replace this with printing=cups and cups options=raw ? I did it and printing system doesn't work OK .. I write here my old options : [Global] printcap name = lpstat [printers] comment = All Printers path = /var/spool/samba create mask = 0700 guest ok = Yes printable = Yes use client driver = Yes print command = lpr-cups -P %p -o raw %s -r lpq command = lpstat -o %p lprm command = cancel %p-%j browseable = No Look at the worked example smb.conf files in the book "Samba-3 By Example" - it might help you. This config doesn't work anyway. Cups doesn't receive works. Now I write the new options I'm trying to use with 3.0.14 version: [Global] printcap name = cups printing = cups printcap = cups [printers] comment = All Printers path = /var/spool/samba create mask = 0700 guest ok = Yes printable = Yes use client driver = Yes ;printing = cups lpq command = lpstat.cups -o %p lprm command = cancel %p-%j browseable = No And edit mime.types and mime.convs in cups config for application/octet- Printing works with this config, but some of them are printed unformatted, with fonts bigger than old config . I send the work via (i.e.) cat work.txt > lp0 and cups prints it OK . Works sended via Word, Excel, etc. are OK > too. There is something wrong with some works sended via MS-DOS programs (like edit program) but I don't know what is the problem . Any suggestions ?? Read the CUPS chapters in the book "The Official Samba3 HOWTO and Reference Guide." Cheers, John T. -- John H Terpstra Samba-Team Member Phone: +1 (650) 580-8668 Author: The Official Samba-3 HOWTO & Reference Guide, 2 Ed., ISBN: 0131882228 Samba-3 by Example, 2 Ed., ISBN: 0131882221X Hardening Linux, ISBN: 0072254971 Other books in production. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] printing problems upgrading samba from 2.2.4 to 3.0.14
On Saturday 27 August 2005 05:55, [EMAIL PROTECTED] wrote: > I'm trying to upgrade samba from 2.2.4 to 3.0.14 version and I would like > to use the same smb.conf that I had. But something looks wrong in printing > system , there are a lot of new options and I don't know why my old > parameters don't work .. The changes are documented in a chapter called "Upgrading Samba" in the book "The Official Samba3 HOWTO". Upgrade issues are discussed in the book "Samba-3 By Example", chapter 8. See http://www.samba.org/samba/docs/Samba3-HOWTO.pdf and http://www.samba.org/samba/docs/Samba3-ByExample.pdf > I use samba through Windows XP/98/2000 and a MS-DOS program that sends > print works to a linux machine with samba. With version 2.2.4 all seemed OK > and worked fine. With version 3.0.14 printers don't work. I need raw > printing. When Samba-3 has been compiled with the CUPS libraries, printing goes direct via the CUPS library API. To enable raw printing add the parameter "cups options = raw". > For example, this line (print command = lpr-cups -P %p -o raw %s -r) > doesn't work in new version. Do I replace this with printing=cups and cups > options=raw ? I did it and printing system doesn't work OK .. > > I write here my old options : > > [Global] > printcap name = lpstat > > [printers] > comment = All Printers > path = /var/spool/samba > create mask = 0700 > guest ok = Yes > printable = Yes > use client driver = Yes > print command = lpr-cups -P %p -o raw %s -r > lpq command = lpstat -o %p > lprm command = cancel %p-%j > browseable = No Look at the worked example smb.conf files in the book "Samba-3 By Example" - it might help you. > This config doesn't work anyway. Cups doesn't receive works. > > Now I write the new options I'm trying to use with 3.0.14 version: > > [Global] > printcap name = cups >printing = cups >printcap = cups > > [printers] > comment = All Printers > path = /var/spool/samba > create mask = 0700 > guest ok = Yes > printable = Yes > use client driver = Yes > ;printing = cups > lpq command = lpstat.cups -o %p > lprm command = cancel %p-%j > browseable = No > > And edit mime.types and mime.convs in cups config for > application/octet- > > Printing works with this config, but some of them are printed unformatted, > with fonts bigger than old config . I send the work via (i.e.) cat work.txt > > > lp0 and cups prints it OK . Works sended via Word, Excel, etc. are OK > > too. > > There is something wrong with some works sended via MS-DOS programs (like > edit program) but I don't know what is the problem . > > Any suggestions ?? Read the CUPS chapters in the book "The Official Samba3 HOWTO and Reference Guide." Cheers, John T. -- John H Terpstra Samba-Team Member Phone: +1 (650) 580-8668 Author: The Official Samba-3 HOWTO & Reference Guide, 2 Ed., ISBN: 0131882228 Samba-3 by Example, 2 Ed., ISBN: 0131882221X Hardening Linux, ISBN: 0072254971 Other books in production. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] printing problems upgrading samba from 2.2.4 to 3.0.14
Ok. Hi everybody. It's my first posting here. If I make something wrong, please notice me . And excuse me for my evil english (I will improve :-) ) . I'm trying to upgrade samba from 2.2.4 to 3.0.14 version and I would like to use the same smb.conf that I had. But something looks wrong in printing system , there are a lot of new options and I don't know why my old parameters don't work .. I use samba through Windows XP/98/2000 and a MS-DOS program that sends print works to a linux machine with samba. With version 2.2.4 all seemed OK and worked fine. With version 3.0.14 printers don't work. I need raw printing. For example, this line (print command = lpr-cups -P %p -o raw %s -r) doesn't work in new version. Do I replace this with printing=cups and cups options=raw ? I did it and printing system doesn't work OK .. I write here my old options : [Global] printcap name = lpstat [printers] comment = All Printers path = /var/spool/samba create mask = 0700 guest ok = Yes printable = Yes use client driver = Yes print command = lpr-cups -P %p -o raw %s -r lpq command = lpstat -o %p lprm command = cancel %p-%j browseable = No This config doesn't work anyway. Cups doesn't receive works. Now I write the new options I'm trying to use with 3.0.14 version: [Global] printcap name = cups printing = cups printcap = cups [printers] comment = All Printers path = /var/spool/samba create mask = 0700 guest ok = Yes printable = Yes use client driver = Yes ;printing = cups lpq command = lpstat.cups -o %p lprm command = cancel %p-%j browseable = No And edit mime.types and mime.convs in cups config for application/octet- Printing works with this config, but some of them are printed unformatted, with fonts bigger than old config . I send the work via (i.e.) cat work.txt > lp0 and cups prints it OK . Works sended via Word, Excel, etc. are OK too. There is something wrong with some works sended via MS-DOS programs (like edit program) but I don't know what is the problem . Any suggestions ?? -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Samba printing problems
I have a server running linux with an hp 5740 running on it Cups seems to deal with this printer just fine. I used the web interface to add the printer with out any problems and it works perfectly. The problem I have is with samba. When I add a 5740 to my windows xp system nothing prints. it seems like the lp command used to queue up the print job are not correctly putting the job in queue. What lp command do i use to submit the job to cups. Chip -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Printing problems
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Josh Kelley wrote: | I'm seeing some tdb errors, although there doesn't appear | to be much of a correlation between them and the | "too many handles" errors: | | [2005/02/01 12:50:57, 0] smbd/connection.c:register_message_flags(220) | register_message_flags: tdb_fetch failed That should have been fixed in 3.0.11. | (We're using per-host logging. I'm only checking for | tdb errors in the logs of hosts that were having | "too many handles" errors; if I should be | checking somewhere else, please let me know.) | | We're happily running Samba 3.0.11 now, and I'm | hoping that that will fix the "too many handles" | errors. I'll post again if I continue to have problems. | Thanks for your help. Thanks. let me know if you find any bugs. cheers, jerry = Alleviating the pain of Windows(tm) --- http://www.samba.org GnuPG Key- http://www.plainjoe.org/gpg_public.asc "I never saved anything for the swim back." Ethan Hawk in Gattaca -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCB9pxIR7qMdg1EfYRArskAKCkmuAn8kAVx0ChZ1Jqyn5Nl7GwCgCg5HcC Nlu6qq3S8McbRXZBeH7KYis= =pCOC -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Printing problems
Gerald (Jerry) Carter wrote: >Another oddity: We'd been getting hundreds or thousands of these error >messages each day, then our server crashed yesterday morning for >as-yet-undetermined reasons. Since the reboot, I've been seeing neither >the "old print jobs aren't cleared" bug nor the "too many handles" >messages. hmm...bad tdb somewhere ? ANy error messages about that ? I'm seeing some tdb errors, although there doesn't appear to be much of a correlation between them and the "too many handles" errors: [2005/02/01 12:50:57, 0] smbd/connection.c:register_message_flags(220) register_message_flags: tdb_fetch failed (We're using per-host logging. I'm only checking for tdb errors in the logs of hosts that were having "too many handles" errors; if I should be checking somewhere else, please let me know.) We're happily running Samba 3.0.11 now, and I'm hoping that that will fix the "too many handles" errors. I'll post again if I continue to have problems. Thanks for your help. Josh Kelley -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Printing problems
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 2 Feb 2005, Josh Kelley wrote: > A couple of questions, keeping in mind that I know little about the SMB > protocol or Samba's internals: If I'm reading the source code and the > log messages correctly, these are policy handles (policy handles on > pipes?). Are those the same thing as printer handles? The limit on > policy handles in 3.0.9 is apparently 1024, not 256. Yes a policy handle is basically the same thing as a printer handle. It's a different limit for printer handles: rpc_server/srv_pipe_hnd.c:#define MAX_OPEN_SPOOLSS_PIPES 256 > Another oddity: We'd been getting hundreds or thousands of these error > messages each day, then our server crashed yesterday morning for > as-yet-undetermined reasons. Since the reboot, I've been seeing neither > the "old print jobs aren't cleared" bug nor the "too many handles" > messages. hmm...bad tdb somewhere ? ANy error messages about that ? cheers, jerry = Alleviating the pain of Windows(tm) --- http://www.samba.org GnuPG Key- http://www.plainjoe.org/gpg_public.asc "I never saved anything for the swim back." Ethan Hawk in Gattaca -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/ iD8DBQFCAPwzIR7qMdg1EfYRAhdkAJ0WD+YfGJm5ThKS7PCONFn/4ZB96ACfXXaw +7SzruguxsXZNyCTwNUwka0= =gnTa -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Printing problems
Gerald (Jerry) Carter wrote: Josh Kelley wrote: | Second, we're seeing lots of the following messages in | our log files: | | [2005/01/27 13:31:34, 0] rpc_server/srv_lsa_hnd.c:create_policy_hnd(111) | create_policy_hnd: ERROR: too many handles (1025) on this pipe. | | I'm getting reports from users that they're intermittently | unable to print. Windows reports, "Unable to create a print | job"; this seems to correspond with the "too many handles" | errors, but I haven't gotten details consistently enough | to know for sure. Any suggestions? Are you using an XP client? There's a limit on the number of open printer handles that smbd will allow to prevent a client from eating up too much memory. it's set to 256 currently. I would look at a network sniff to see what the client is doing opening all those printer handles. We are using XP clients. I'll try running a network sniff; thanks for the suggestion. (The problem is happening intermittently on a number of our lab computers, which makes that a bit harder.) A couple of questions, keeping in mind that I know little about the SMB protocol or Samba's internals: If I'm reading the source code and the log messages correctly, these are policy handles (policy handles on pipes?). Are those the same thing as printer handles? The limit on policy handles in 3.0.9 is apparently 1024, not 256. Another oddity: We'd been getting hundreds or thousands of these error messages each day, then our server crashed yesterday morning for as-yet-undetermined reasons. Since the reboot, I've been seeing neither the "old print jobs aren't cleared" bug nor the "too many handles" messages. Josh Kelley -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Printing problems
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Josh Kelley wrote: | Second, we're seeing lots of the following messages in | our log files: | | [2005/01/27 13:31:34, 0] rpc_server/srv_lsa_hnd.c:create_policy_hnd(111) | create_policy_hnd: ERROR: too many handles (1025) on this pipe. | | I'm getting reports from users that they're intermittently | unable to print. Windows reports, "Unable to create a print | job"; this seems to correspond with the "too many handles" | errors, but I haven't gotten details consistently enough | to know for sure. Any suggestions? Are you using an XP client? There's a limit on the number of open printer handles that smbd will allow to prevent a client from eating up too much memory. it's set to 256 currently. I would look at a network sniff to see what the client is doing opening all those printer handles. cheers, jerry -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCABAeIR7qMdg1EfYRArv2AJ9e9K5eo8LgYlcn9WH4XAnOx3LPswCdEPTw yq4EeiI7PYCa0rBwb5+3yqQ= =l64G -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] printing Problems in Samba 3.0.10
On Fri, 28 Jan 2005 10:55:30 +0100, Christoph Klein <[EMAIL PROTECTED]> wrote: > Hi all, > we are using Samba for a year in our departement. It replaced a > dedicated win2k-server for printer and file sharing. We are quite happy > with it, but we have still some problems. Does anyone of you know > solutions to this: > 1. We are using HP Laserjet 4300 in our departement. Driver ( origial PS > drivers from HP website) installation was successfull and basic functionality > works, but some features like collate and n-up are missing on the options > panels of the driver. We tested these drivers on a Windows server before, and > there they hadd these options. I've had the same problems with a HP Color Laserjet 5500. HP's drivers use EMF to provide the n-up (and probably collate) functionality. Now, EMF runs on the server side and Samba doesn't support it. Our solution passed by using Adobe's PS drivers. When properly configured they give you the exact same functionality, altough you loose all of HP's eye candy in the print gui. > 2. From time to time our samba server forgets all options of the > printer: The Driver name, additional installed components (duplex unit, > second tray) and the long, friendly printer name. > 3. Since today enumprinter returns for a single printer two printers: one > with the friendly name, the other with the share name. If i open the > properties dialog, they both show the same dialog for thr printer with the > logn name. In smb.conf there is only a signle entry defined for this printer. I don't know about 2) but about 3): if I recall correctly you have an option in smb.conf to force Windows to use the samba printer name, as the printer name (Windows automatically uses the print driver name instead of the printer name, IIRC). Search the mailing lists and you'll find more about this. HTH, manuel -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] printing Problems in Samba 3.0.10
Hi all, we are using Samba for a year in our departement. It replaced a dedicated win2k-server for printer and file sharing. We are quite happy with it, but we have still some problems. Does anyone of you know solutions to this: 1. We are using HP Laserjet 4300 in our departement. Driver ( origial PS drivers from HP website) installation was successfull and basic functionality works, but some features like collate and n-up are missing on the options panels of the driver. We tested these drivers on a Windows server before, and there they hadd these options. 2. From time to time our samba server forgets all options of the printer: The Driver name, additional installed components (duplex unit, second tray) and the long, friendly printer name. 3. Since today enumprinter returns for a single printer two printers: one with the friendly name, the other with the share name. If i open the properties dialog, they both show the same dialog for thr printer with the logn name. In smb.conf there is only a signle entry defined for this printer. Sample smb.conf is appended Thanks for your help Christoph [global] workgroup = CIP-POOL realm = WIWI.UNI-KARLSRUHE.DE netbios name = fwi-fortuna allow trusted domains = No winbind use default domain = yes winbind trusted domains only = yes server string = %h server (Samba %v) security = ADS username map = /etc/samba/usermap restrict anonymous = 2 load printers = No printcap name = cups dns proxy = No invalid users = root printer admin = smbop, christophk, @lpadmin printing = cups #APW Skripte enumports command=/usr/bin/enumports addprinter command=/usr/bin/addprinter deleteprinter command=/usr/bin/deleteprinter [printers] comment = All Printers path = /tmp force user = zbenutzer create mask = 0700 printable = Yes browseable = No [print$] comment = Printer Drivers path = /usr/share/samba/printers write list = smbop, christophk, @lpadmin force user = smbop browseable = No [hp43cps] path = /tmp printable = Yes printer name = fwi-hp4300c [PDF] path = /tmp printable = Yes printer name = PDFPrinter [hp43dpc] path = /tmp printable = Yes printer name = FWI-HP4300D [hp43apc] path = /tmp printable = Yes printer name = fwi-hp4300a [hp43aps] path = /tmp printable = Yes printer name = fwi-hp4300a [hp45pcl] path = /tmp printable = Yes printer name = fwi-cip-hp4500n [hp45ps] path = /tmp printable = Yes printer name = fwi-cip-hp4500n [hp46bpc] path = /tmp printable = Yes printer name = fwi-hp4600b [hp46bps] path = /tmp printable = Yes printer name = fwi-hp4600b [hp43cpc] path = /tmp printable = Yes printer name = fwi-hp4300c [hp46apc] path = /tmp printable = Yes printer name = fwi-hp4600a [hp46aps] path = /tmp printable = Yes printer name = fwi-hp4600a [hp43dps] path = /tmp printable = Yes printer name = FWI-HP4300D [hp43bps] path = /tmp printable = Yes printer name = fwi-hp4300b [hp43bpc] path = /tmp printable = Yes printer name = fwi-hp4300b -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Printing problems
I'm having several printing problems. Server is RHEL 3, running samba-3.0.9-1.3E.2 and cups-1.1.17-13.3.22. Clients are Win2K and WinXP. First, we're seeing the "failure to remove print jobs from queue list display" problem that others have reported. The document count for each printer also doesn't match the number of jobs in the queue list. I understand that there's a patch available for Samba 3.0.10 to fix the former problem; will it fix the latter problem as well? Will the patch apply to Red Hat's samba-3.0.9 (it looks like it will), or do I need to upgrade to 3.0.10? Second, we're seeing lots of the following messages in our log files: [2005/01/27 13:31:34, 0] rpc_server/srv_lsa_hnd.c:create_policy_hnd(111) create_policy_hnd: ERROR: too many handles (1025) on this pipe. I'm getting reports from users that they're intermittently unable to print. Windows reports, "Unable to create a print job"; this seems to correspond with the "too many handles" errors, but I haven't gotten details consistently enough to know for sure. Any suggestions? I appreciate any help that can be given. Josh Kelley -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Printing Problems With Samba Version 2.2.7a.
Hi, I currently have a serious printing problem with my Samba version 2.2.7a. After arriving at work this morning, I was informed that non of the network printers (defined in our smb.conf file) could handle print requests. I deleted all the printer definitions (ie. ntprinters.tdb and printing.tdb) I found in /var/samba/lock, and restarted smbd (via pkill -HUP smbd). But still had no joy. I then ran the 'truss' diagnostic tool on the Solaris lpsched print daemon and the output appeared to hang, after suggesting that a process it was trying to read (possibly from a memory module) was 'sleeping'. Any clues as to why I cannot currently print would be appreciated. Thank you, Kenneth Nwoye -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] printing problems with 3.0.1
i have the same problem did you find a fix for it. One day everything was working the next day . thanks, Tom Jones Director of Information Technology Savoy ISD (903) 965 - 4024 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Printing problems w/ win 2k
i haev samba running and a printer share, however when I go through the wziard to install a new printer everythign goes fine but when I try to access the printer the win box says Access denied, unable to connect Here is my printers shaer in my smb.conf [printers] use client driver = yes comment = All Printers path = /var/spool/samba browseable = no public = yes printable = yes writeable = no create mode = 0700 It's cups version cups-1.1.17-13.3.0.3 And samba version samba-2.2.7a-8.9.0 Thanx for any help -- Michael S. Dunsavage -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Printing problems
Hi All I getting the following in my messages log file every 2 minutes it would appear, Can anyone help ? Feb 13 15:42:06 rh9printsvr smbd[4620]: [2004/02/13 15:42:06, 0] smbd/service.c:make_connection(857) Feb 13 15:42:06 rh9printsvr smbd[4620]: nicksinvsr (172.28.20.23) couldn't find service rh9_pkt_it4600,winspool,ne06: -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] printing problems wih samba
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] Printing problems drive me crazy
Hi list, Last week i installed an Epson FX2180 printer in my samba PDC (Samba 2.2.8, RH 9) and shared it. Then, when i tried to print from a win98 client, something strange happened. firstly i tried form MS Word, and it printed fine. but when i tried to print from a dos application, i could not do it. The printer is mapped by the client in lpt1, but when i trie to print from DOS, (i.e. c:\>dir > lpt1) nothing happens. Any ideas? Thanks Sebastian - ¿Buscás un auto? Encontralo en Yahoo! Autos ¡Más de 4000 clasificados todos los días! Usados - 0 km - Vendé el tuyo -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] printing problems with 3.0.1
Hi Jerry et al, I recently installed the 3.0.1 release, since then I can not install any drivers as admin user :-( I'm running on Solaris 9 with ads (mybe I missed anything): [2003/12/18 13:56:58, 0] smbd/service.c:set_admin_user(321) lp logged in as admin user (root privileges) [2003/12/18 13:57:27, 0] smbd/connection.c:register_message_flags(220) register_message_flags: tdb_fetch failed [2003/12/18 13:57:30, 1] smbd/service.c:make_connection_snum(705) adc1 (131.169.69.134) connect to service print$ initially as user nobody (uid=60001, gid=60001) (pid 17088) [2003/12/18 13:57:37, 0] smbd/connection.c:register_message_flags(220) register_message_flags: tdb_fetch failed [2003/12/18 13:57:37, 0] smbd/connection.c:register_message_flags(220) register_message_flags: tdb_fetch failed [2003/12/18 13:58:07, 0] smbd/connection.c:register_message_flags(220) ...skipping... === [2003/12/19 12:34:40, 0] lib/util.c:smb_panic(1400) PANIC: internal error [2003/12/19 12:35:45, 0] smbd/service.c:set_admin_user(321) lp logged in as admin user (root privileges) [2003/12/19 12:35:45, 1] smbd/service.c:make_connection_snum(705) zitpcx3669 (131.169.214.120) connect to service print$ initially as user lp (uid=0, gid=8) (pid 12402) [2003/12/19 12:35:49, 0] smbd/nttrans.c:call_nt_transact_ioctl(1990) call_nt_transact_ioctl(0x90100): Currently not implemented. [2003/12/19 12:35:51, 1] smbd/service.c:make_connection_snum(705) zitpcx3669 (131.169.214.120) connect to service print$ initially as user nobody (uid=60001, gid=60001) (pid 12402) [2003/12/19 12:35:59, 1] smbd/service.c:close_cnum(887) zitpcx3669 (131.169.214.120) closed connection to service print$ [2003/12/19 12:36:11, 1] smbd/service.c:make_connection_snum(705) zitpcx3669 (131.169.214.120) connect to service print$ initially as user nobody (uid=60001, gid=60001) (pid 12402) [2003/12/19 12:36:13, 0] smbd/service.c:set_admin_user(321) lp logged in as admin user (root privileges) [2003/12/19 12:36:13, 1] smbd/service.c:make_connection_snum(705) zitpcx3669 (131.169.214.120) connect to service print$ initially as user lp (uid=0, gid=8) (pid 12402) [2003/12/19 12:36:13, 1] smbd/service.c:close_cnum(887) zitpcx3669 (131.169.214.120) closed connection to service print$ [2003/12/19 12:36:13, 0] smbd/service.c:set_admin_user(321) lp logged in as admin user (root privileges) [2003/12/19 12:36:13, 1] smbd/service.c:make_connection_snum(705) zitpcx3669 (131.169.214.120) connect to service print$ initially as user lp (uid=0, gid=8) (pid 12402) [2003/12/19 12:36:13, 1] smbd/service.c:close_cnum(887) zitpcx3669 (131.169.214.120) closed connection to service print$ [2003/12/19 12:36:19, 1] smbd/service.c:close_cnum(887) zitpcx3669 (131.169.214.120) closed connection to service print$ [2003/12/19 12:37:18, 0] smbd/server.c:open_sockets_smbd(377) open_sockets_smbd: accept: Software caused connection abort [2003/12/19 12:38:19, 1] smbd/service.c:close_cnum(887) zitpcx3669 (131.169.214.120) closed connection to service print$ [2003/12/19 12:38:55, 0] lib/fault.c:fault_report(36) === [2003/12/19 12:38:55, 0] lib/fault.c:fault_report(37) INTERNAL ERROR: Signal 11 in pid 16595 (3.0.1) Please read the appendix Bugs of the Samba HOWTO collection [2003/12/19 12:38:55, 0] lib/fault.c:fault_report(39) === [2003/12/19 12:38:55, 0] lib/util.c:smb_panic(1400) PANIC: internal error best regards ~christoph -- /* Christoph Beyer | Office: Building 2b / 23 *\ * DESY|Phone: 040-8998-2317* * - IT - | Fax: 040-8998-4060* \* 22603 Hamburg | http://www.desy.de */ -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Printing Problems (Updated)
I have been struggling with samba and printing. My original post is at http://lists.samba.org/archive/samba/msg72613.html. I since then, I built a 2nd box, but this time it is a samba 3.0.0 box. The same thing happens on the 3.0.0 box. The update is that this occurs on the lexmark printer using the Lexmark Z22/32 drivers. If I use a HP driver or a different driver, the job goes to the queue, but prints garbage. This is expected though. Is there a reason why the job does not spool with the lexmark driver? I deteted all the tdb file except the secrets.tdb and restarted the server. On a few occasions, I got the printer to print with the lexmark driver, but most of the time it failed. I downloaded the driver from lexmark's site. Printing a test page gives "Test page failed to print. Would you like to view the print troubleshooter for assistance? Unable to create a print job." I have disabled bidirectional support on the printer but it still does not spool. Copying a file directly to the printer share works. Am I missing something? What can I do to get it working. The printer wrked with the driver once, but I can't seem to get it to work again. Please help! Bob. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] printing problems.
hello all. i apologize if im reposting this problem, but i could not find any solution in the archives ;) . i have upgraded my samba server from 2.0.7 to 2.2.8a, on a SunOs 2.7 . im having the following problem: some users cannot access the printer shares. when i open the start->settings->printers, i get a "printer not found on server, unable to connect" . (clients are win2k) when another user logs in to the same machine (using terminal services) she _can_ access these shares. can someone please help me? im lost. thanks. p.s. please cc me, im not registered to the list. thanks again. here is the relevant smb.conf snippet: [global] workgroup = SAMBA_DOMAIN security = SERVER password server = sapphire use rhosts = Yes log file = /usr/local/samba/var/log.%m max log size = 50 #disable spoolss does not solve the problem... disable spoolss = Yes domain logons = Yes wins server = 132.72.40.44 print command = lp -c -d %p %s; rm %s lpq command = lpq -P%p lprm command = lprm -P%p %j [printers] comment = All Printers path = /tmp read only = No create mask = 0700 guest ok = Yes max print jobs = 10 printable = Yes browseable = No -- nir. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Printing problems with Samba 3.0
I have installed latest Samba 3.0 RPM's and now I can print from WindowsPC to the Linux printer but I can't print anymore from Linux machine to the Windows printer (that it was properly working on previous release). Version of Samba is 3.0.0rc2-2 Any clue??? TNX Antonio -- Written with Mozilla 1.4 on Linux RedHat 8.0 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Printing problems Win2K SP4 on 3.0.x and 2.x
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 28 Aug 2003, Van Sickler, Jim wrote: > If you want to use the spoolss support incorporated > since 2.2.7, you'll have to read up on the Samba > How-To Collection changes. The changes aren't trivial. > http://samba.org/~jht/NT4migration/Samba-HOWTO-Collection.pdf the MS-RPC printing support was initially added in 2.2.0 (about 3 years ago) jerry -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/ iD8DBQE/TkIkIR7qMdg1EfYRAikuAJ4kFLBZru9Uxe4v5E9hwpsCOOdvTgCfQpUM Mm2rUO8pVtRyjvnvQsJRtKo= =qn8R -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] Printing problems Win2K SP4 on 3.0.x and 2.x
Paul, If you were using a Samba version prior to 2.2.7 (I think), then you need to put the following in your [Global] section: disable spoolss = yes and add the following to the [Printers] section and/or each printer entry: use client driver = yes This will support the printers as previously set up, and give you some time to investigate the new features. If you want to use the spoolss support incorporated since 2.2.7, you'll have to read up on the Samba How-To Collection changes. The changes aren't trivial. http://samba.org/~jht/NT4migration/Samba-HOWTO-Collection.pdf You'll probably have to: 1. Remove all Samba-served printers from the clients. 2. Re-enable the spoolss (disable spoolss = no) 3. Set up/install print drivers for the printers that will allow you to (not all will, and you'll have to keep the "use client driver = yes" for those. AdobePS and Lexmark are two that I've had to do that with. HPs work ok, FWIR. 4. Install the printers on the clients again. If anyone has more correct info, please respond; I'd rather Paul be given the right info than have to unlearn/undo bogus advice. Jim > -Original Message- > From: Paul Richards [mailto:[EMAIL PROTECTED] > Sent: Wednesday, August 27, 2003 10:28 AM > To: [EMAIL PROTECTED] > Subject: [Samba] Printing problems Win2K SP4 on 3.0.x and 2.x > > > I'm afraid I am stumped, and need some help or pointers. > > Ever since I've "upgraded" my Win2k boxes to SP4, I've been > unable to print > to Samba-shared printers (on Solaris and Freebsd). Originally I was > running > the current 2.2.x, and figured trying to diagnose the problem > would provide > an impetus for trying 3.0, which I have from beta3 through > RC1. That bit > of > history is to indicate that sharing *did* work prior to SP4. > > >From the Win2k perspective, it cannot open the printer. I > can remove and > install > it, and the wizard completes successfully, but the printer > status window > shows in > the title bar "xxx on xxx failed to open, retrying...". > Sometimes it times > out and > then the general Printers window will show in the Status field that > "printer no longer > exists on server" or "opening", but never "ready". I can open the > properties window, > and see the appropriate properties (can't change anything), > but if I try to > print > a test page explorer.exe dies. > > >From the Samba server perspective, it looks fine. I can use > smbclient to > connect to > the printer, and spool a file to it. As mentioned above, the > Win2k drivers > were > successfully added and registered (since Win2k picks them > up). There are > errors in > the smbd logs that appear any time a Win2KSP4 box attempts to > open the > printer: > > [2003/08/26 16:00:48, 0] smbd/ipc.c:reply_trans(569) > reply_trans: invalid trans parameters > [2003/08/26 16:00:48, 3] smbd/error.c:error_packet(113) > error packet at smbd/ipc.c(574) cmd=37 (SMBtrans) > NT_STATUS_INVALID_PARAMETER > > (I've not copied the higher loglevel data yet to save space). > > If someone can help, I'd appreciate it. I have much more > detailed error > logs from > the server, and if needed can post exerpts from my smb.conf file. > > -Paul > > -- > 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
[Samba] Printing problems Win2K SP4 on 3.0.x and 2.x
I'm afraid I am stumped, and need some help or pointers. Ever since I've "upgraded" my Win2k boxes to SP4, I've been unable to print to Samba-shared printers (on Solaris and Freebsd). Originally I was running the current 2.2.x, and figured trying to diagnose the problem would provide an impetus for trying 3.0, which I have from beta3 through RC1. That bit of history is to indicate that sharing *did* work prior to SP4. From the Win2k perspective, it cannot open the printer. I can remove and install it, and the wizard completes successfully, but the printer status window shows in the title bar "xxx on xxx failed to open, retrying...". Sometimes it times out and then the general Printers window will show in the Status field that "printer no longer exists on server" or "opening", but never "ready". I can open the properties window, and see the appropriate properties (can't change anything), but if I try to print a test page explorer.exe dies. From the Samba server perspective, it looks fine. I can use smbclient to connect to the printer, and spool a file to it. As mentioned above, the Win2k drivers were successfully added and registered (since Win2k picks them up). There are errors in the smbd logs that appear any time a Win2KSP4 box attempts to open the printer: [2003/08/26 16:00:48, 0] smbd/ipc.c:reply_trans(569) reply_trans: invalid trans parameters [2003/08/26 16:00:48, 3] smbd/error.c:error_packet(113) error packet at smbd/ipc.c(574) cmd=37 (SMBtrans) NT_STATUS_INVALID_PARAMETER (I've not copied the higher loglevel data yet to save space). If someone can help, I'd appreciate it. I have much more detailed error logs from the server, and if needed can post exerpts from my smb.conf file. -Paul -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] printing problems
Hello, cups does *not* need any "print command or so" - lines in the smb.conf. All you need is "printing = cups" and "printcap name=cups". The rest is internal! Joel describes all other steps do track down the problem. Perhaps tell us the versions of samba and cups you're using and make shure, that your smbd is configured and compiled for cups support (is "ldd `which smbd`" showing libcups.so.2?). BTW: cups logs are usually named /var/log/error_log. Cheers. On Saturday 25 January 2003 02:35, Joel Hammer wrote: > Disappearing print jobs are often a driver issue. > I don't use cups, so: > Is your print command correct? lpr-cups? > Does the job get transferred to your /var/spool/samba directory? > Does the job get removed? I don't see a "rm %s" command in your print > command. If the job gets transferred but not printed, can you print it out > with the same command you use in your printing share? > The samba logs might be useful. > What do your printing logs show? > Does you guest user have the rights to use your printing software? BTW, > I don't see a guest user defined in your smb.conf. > > > Joel > > /n Fri, Jan 24, 2003 at 05:29:54PM +1100, Colin Jenkins wrote: > > not sure what Iv'e messed up here, but I did have my mandrake 9 server > > sharing it's printer to my windows boxes with samba. I reinstalled linus > > on the server, and replaced winxp with mandrake 9 on one workstation. the > > linux workstation and server each have a printer connected and both > > machines can use each others printers. I have been trying for a week to > > get the windows boxes to use the printers to no avail. The printers are > > found and installed, but the print jobs disappearno errors. any > > ideas? > > oh yeah, below is part of my smb.conf > > > > #== Global Settings = > > [global] > > workgroup = CURRICULUM > > netbios name = hal > > load printers = yes > > security = server > > server string = Samba Server %v > > passwd chat = *New*UNIX*password* %n\n *ReType*new*UNIX*password* %n\n > > printing = cups > > default = home > > password server = 192.168.0.1 > > update encrypted = no > > encrypt passwords = no > > passwd program = /usr/bin/passwd %u > > domain logons = no > > wins server = 192.168.0.1 > > local master = yes > > preferred master = No > > domain master = No > > socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 > > > > > > > > # Share Definitions === > > > > [printers] > > comment = All Printers > > path = /var/spool/samba > > read only = No > > create mask = 0700 > > guest ok = yes > > hosts allow = 192.168. > > printable = Yes > > printing = cups > > use client driver = yes > > print command = lpr-cups -P %p %s # using cups own drivers (use generic > > PostScript on clients). lpq command = lpstat -o %p > > lprm command = cancel %p-%j > > browseable = yes > > -- > > To unsubscribe from this list go to the following URL and read the > > instructions: http://lists.samba.org/mailman/listinfo/samba -- Martin Zielinski [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] printing problems
Disappearing print jobs are often a driver issue. I don't use cups, so: Is your print command correct? lpr-cups? Does the job get transferred to your /var/spool/samba directory? Does the job get removed? I don't see a "rm %s" command in your print command. If the job gets transferred but not printed, can you print it out with the same command you use in your printing share? The samba logs might be useful. What do your printing logs show? Does you guest user have the rights to use your printing software? BTW, I don't see a guest user defined in your smb.conf. Joel /n Fri, Jan 24, 2003 at 05:29:54PM +1100, Colin Jenkins wrote: > not sure what Iv'e messed up here, but I did have my mandrake 9 server sharing it's >printer to my windows boxes with samba. > I reinstalled linus on the server, and replaced winxp with mandrake 9 on one >workstation. > the linux workstation and server each have a printer connected and both machines can >use each others printers. > I have been trying for a week to get the windows boxes to use the printers to no >avail. > The printers are found and installed, but the print jobs disappearno errors. > any ideas? > oh yeah, below is part of my smb.conf > > #== Global Settings = > [global] > workgroup = CURRICULUM > netbios name = hal > load printers = yes > security = server > server string = Samba Server %v > passwd chat = *New*UNIX*password* %n\n *ReType*new*UNIX*password* %n\n > printing = cups > default = home > password server = 192.168.0.1 > update encrypted = no > encrypt passwords = no > passwd program = /usr/bin/passwd %u > domain logons = no > wins server = 192.168.0.1 > local master = yes > preferred master = No > domain master = No > socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 > > > > # Share Definitions === > > [printers] > comment = All Printers > path = /var/spool/samba > read only = No > create mask = 0700 > guest ok = yes > hosts allow = 192.168. > printable = Yes > printing = cups > use client driver = yes > print command = lpr-cups -P %p %s # using cups own drivers (use generic >PostScript on clients). > lpq command = lpstat -o %p > lprm command = cancel %p-%j > browseable = yes > -- > 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
[Samba] printing problems
not sure what Iv'e messed up here, but I did have my mandrake 9 server sharing it's printer to my windows boxes with samba. I reinstalled linus on the server, and replaced winxp with mandrake 9 on one workstation. the linux workstation and server each have a printer connected and both machines can use each others printers. I have been trying for a week to get the windows boxes to use the printers to no avail. The printers are found and installed, but the print jobs disappearno errors. any ideas? oh yeah, below is part of my smb.conf #== Global Settings = [global] workgroup = CURRICULUM netbios name = hal load printers = yes security = server server string = Samba Server %v passwd chat = *New*UNIX*password* %n\n *ReType*new*UNIX*password* %n\n printing = cups default = home password server = 192.168.0.1 update encrypted = no encrypt passwords = no passwd program = /usr/bin/passwd %u domain logons = no wins server = 192.168.0.1 local master = yes preferred master = No domain master = No socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 # Share Definitions === [printers] comment = All Printers path = /var/spool/samba read only = No create mask = 0700 guest ok = yes hosts allow = 192.168. printable = Yes printing = cups use client driver = yes print command = lpr-cups -P %p %s # using cups own drivers (use generic PostScript on clients). lpq command = lpstat -o %p lprm command = cancel %p-%j browseable = yes -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Printing problems
On Mon, 2002-12-09 at 16:02, Joel Hammer wrote: > I know nothing about cups. > > Here is what I would do. > > I would change the print command in my smb.conf to something like echo "have > printed this thing %s" > /tmp/junk > > The file should be saved on your hard drive somewhere, in the spool directory > you made for it with the name %s. > > Try cat'ing the file to /dev/lpX, and see if it prints properly. This will > bypass the cups printing software. > > You might also try to figure out what cups is doing with this file after it > lands on your hard drive. > > Joel Still nothing - nada. Zero. Zilch. It's really getting to be an annoying thing - and almost wanting to just get a frigging jet-direct box - easier to deal with and it's not attached to anyone so there's less mess, less fuss. I just can't believe how stupid this is getting - all just to print something. Driving me nuts. -- Mon Dec 9 20:50:01 EST 2002 8:50pm up 1 day, 35 min, 5 users, load average: 0.10, 0.16, 1.01 .o0 linux user:267497 0o. |____ | kühn media australia | / \ /| |'-. | http://kma.0catch.com | .\__/ || | | | | _ / `._ \|_|_.-' | stephen kühn | | / \__.`=._) (_ | email: [EMAIL PROTECTED] | |/ ._/ |"| | email: [EMAIL PROTECTED] | |'. `\ | | |icq: 5483808 | ;"""/ / | | | | smk ) /_/| |.---.| | mobile: 0410-728-389 | ' `-`' " " | Berkeley, New South Wales, AU Coralament*Best Grötens*Liebe Grüße*Best Regards*Elkorajn Salutojn "From there to here, from here to there, funny things are everywhere." -- Dr. Seuss -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Printing problems
I know nothing about cups. Here is what I would do. I would change the print command in my smb.conf to something like echo "have printed this thing %s" > /tmp/junk The file should be saved on your hard drive somewhere, in the spool directory you made for it with the name %s. Try cat'ing the file to /dev/lpX, and see if it prints properly. This will bypass the cups printing software. You might also try to figure out what cups is doing with this file after it lands on your hard drive. Joel On Mon, Dec 09, 2002 at 03:39:08PM +1100, Stephen Kuhn wrote: > On Mon, 2002-12-09 at 15:15, Joel Hammer wrote: > > Just some random thoughts: > > > > Do you know what commmand is actually being sent at the end of each line? Is > > is really a newpage command? > > > Yeppers, shore is... > > > Is there a DIP switch on the printer that may affect this behavior? > > > It's a WinPrinter - no such thing as a DIP on it... > > > Does this happen when you attach the printer directly to a windows client? > > > Nope. If I discon the prn from this box and stick it on a Win box, it's > happy. > > > Can you print successfully from the linux server to the printer? > > > If I print directly from linux, it's happy. Prints directly from Win, > it's happy. Print through SAMBA, it freaks out. > > > Joel > > -- > Mon Dec 9 15:35:00 EST 2002 > 3:35pm up 19:20, 5 users, load average: 0.00, 0.00, 0.07 > >.o0 linux user:267497 0o. > > |____ | kühn media australia > | / \ /| |'-. | http://kma.0catch.com > | .\__/ || | | | > | _ / `._ \|_|_.-' | stephen kühn > | | / \__.`=._) (_ | email: [EMAIL PROTECTED] > | |/ ._/ |"| | email: [EMAIL PROTECTED] > | |'. `\ | | |icq: 5483808 > | ;"""/ / | | | > | smk ) /_/| |.---.| | mobile: 0410-728-389 > | ' `-`' " " | Berkeley, New South Wales, AU > > Coralament*Best Grötens*Liebe Grüße*Best Regards*Elkorajn Salutojn > > Gumperson's Law: > The probability of a given event occurring is inversely > proportional to its desirability. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Printing problems
On Mon, 2002-12-09 at 15:15, Joel Hammer wrote: > Just some random thoughts: > > Do you know what commmand is actually being sent at the end of each line? Is > is really a newpage command? > Yeppers, shore is... > Is there a DIP switch on the printer that may affect this behavior? > It's a WinPrinter - no such thing as a DIP on it... > Does this happen when you attach the printer directly to a windows client? > Nope. If I discon the prn from this box and stick it on a Win box, it's happy. > Can you print successfully from the linux server to the printer? > If I print directly from linux, it's happy. Prints directly from Win, it's happy. Print through SAMBA, it freaks out. > Joel -- Mon Dec 9 15:35:00 EST 2002 3:35pm up 19:20, 5 users, load average: 0.00, 0.00, 0.07 .o0 linux user:267497 0o. |____ | kühn media australia | / \ /| |'-. | http://kma.0catch.com | .\__/ || | | | | _ / `._ \|_|_.-' | stephen kühn | | / \__.`=._) (_ | email: [EMAIL PROTECTED] | |/ ._/ |"| | email: [EMAIL PROTECTED] | |'. `\ | | |icq: 5483808 | ;"""/ / | | | | smk ) /_/| |.---.| | mobile: 0410-728-389 | ' `-`' " " | Berkeley, New South Wales, AU Coralament*Best Grötens*Liebe Grüße*Best Regards*Elkorajn Salutojn Gumperson's Law: The probability of a given event occurring is inversely proportional to its desirability. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Printing problems
Just some random thoughts: Do you know what commmand is actually being sent at the end of each line? Is is really a newpage command? Is there a DIP switch on the printer that may affect this behavior? Does this happen when you attach the printer directly to a windows client? Can you print successfully from the linux server to the printer? Joel On Mon, Dec 09, 2002 at 03:04:54PM +1100, Stephen Kuhn wrote: > I'm using Samba 2.2.7, RH 7.3, CUPS printing to a Canon BJC-265SP, > accessing the "shared" printer via either regular network connection > from a WinXP workstation or via VMWare WinXP; I've "shared" the printer > via Samba, but when printing, instead of EOL's, the printer is receiving > EOP's - (for each line printed to the printer, a new sheet gets put in > instead of an end-of-line)...hence, printing is not good. > > Any suggestions? > > TIA, > Stephen > > -- > Mon Dec 9 15:00:00 EST 2002 > 3:00pm up 18:45, 5 users, load average: 0.40, 0.33, 0.47 > >.o0 linux user:267497 0o. > > |____ | kühn media australia > | / \ /| |'-. | http://kma.0catch.com > | .\__/ || | | | > | _ / `._ \|_|_.-' | stephen kühn > | | / \__.`=._) (_ | email: [EMAIL PROTECTED] > | |/ ._/ |"| | email: [EMAIL PROTECTED] > | |'. `\ | | |icq: 5483808 > | ;"""/ / | | | > | smk ) /_/| |.---.| | mobile: 0410-728-389 > | ' `-`' " " | Berkeley, New South Wales, AU > > Coralament*Best Grötens*Liebe Grüße*Best Regards*Elkorajn Salutojn > >Gypsy robot: You want to die? >Bender: No, I wanna live! There's still too many things I don't own. > -- > 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
[Samba] Printing problems
I'm using Samba 2.2.7, RH 7.3, CUPS printing to a Canon BJC-265SP, accessing the "shared" printer via either regular network connection from a WinXP workstation or via VMWare WinXP; I've "shared" the printer via Samba, but when printing, instead of EOL's, the printer is receiving EOP's - (for each line printed to the printer, a new sheet gets put in instead of an end-of-line)...hence, printing is not good. Any suggestions? TIA, Stephen -- Mon Dec 9 15:00:00 EST 2002 3:00pm up 18:45, 5 users, load average: 0.40, 0.33, 0.47 .o0 linux user:267497 0o. |____ | kühn media australia | / \ /| |'-. | http://kma.0catch.com | .\__/ || | | | | _ / `._ \|_|_.-' | stephen kühn | | / \__.`=._) (_ | email: [EMAIL PROTECTED] | |/ ._/ |"| | email: [EMAIL PROTECTED] | |'. `\ | | |icq: 5483808 | ;"""/ / | | | | smk ) /_/| |.---.| | mobile: 0410-728-389 | ' `-`' " " | Berkeley, New South Wales, AU Coralament*Best Grötens*Liebe Grüße*Best Regards*Elkorajn Salutojn Gypsy robot: You want to die? Bender: No, I wanna live! There's still too many things I don't own. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] printing problems
I have moved my epson stylus color 800 to my redhat 7.2 server and I am printing fine. Except for one daunting problem. I am unable to print more than one copy. I have originally installed it using bsd and the stcolor driver stp froze the machine. anyway I moved to cups and again I can print fine and locally on the server I can print as many copies as I want. I cannot still print more than one copy from my windows boxes xp,2000,me,98. I am stumped can anyone help. Please reply direct to [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Printing problems with NT/Samba
Hi, This is a message requesting help for the following problem: Printing Word 97 documents, stored on a Samba server, on an NT4 system to an LPD print queue fails under certain well-defined conditions, creating an empty file called 'Ne:' (e.g. 'Ne120:'). The problem appears to be easily reproducable, as long as you have more than 99 print queues on your NT system. Background: Running Samba 2.2.6 on Slackware 8.0 with a 2.4.19 linux kernel. The Microsoft operating system attempting to print is NT4 Terminal Server Edition. Approximately 400 remote LPD network print queues are installed on NT4. Looking back at the samba mailing list archives, it appears to be a continuation of the problems with Samba 2.0.x discussed in the references I've appended at the end of this email. Which is why I sent this message to this list. If you feel I should have sent this message to another list, please let me know. Detailed description of problem: (in the following, the document involved is a simple 'hello world' document, prepared using Word 97. The 'logical port names' mentioned are those defined in the registry, at location HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Devices) Scenario (a): Double-clicking on a Word document served by Samba (loads file into Word 97), then attempting to print to a queue with a logical port name greater than Ne99: (e.g. Ne100:) results in an empty file being created in that directory with the same name as the port, while Word hangs. Scenario (b): Double-clicking on a Word document served by Samba (loads file into Word 97), then attempting to print to a queue with a logical port name lower than Ne100: (e.g. Ne50:) results in a normal print job. Scenario (c): Double-clicking on a Word 97 shortcut from the desktop and then using the File->Open dialog to open the same file served by Samba, then attempting to print to a queue with a logical port name greater than Ne99: results in a normal print job. I presume that Word 97 attempts to create a file of the same name as the port being printed to, in the current working directory, and printing only proceeds if it cannot create it. In scenarios (a) and (b), the working directory is served by Samba. In scenario (c), the working directory is served from NTFS. Could it be that Samba appears to realise that, say, 'Ne12:' is an invalid/special filename but not for, say, 'Ne123:'? Although the workaround mentioned in the references at the bottom of this email (adding a 'veto files' directive to smb.conf) still appears to work with 2.2.x, I'm sending this message because the original problem appears to be half-fixed. That is, in 2.2.x, print queues associated with the ports 'Ne01:' through to 'Ne99:' work correctly, but those associated with 'Ne100:' and above do not. I've attempted to look in the Samba sources for evidence of the half-fix, but I admit defeat. In case anyone wants a look, I've got multiple annotated level 10 debug listings for scenarios (a) and (b) and my smb.conf at: http://www.homepages.ucl.ac.uk/~ccaamad/samba.logs.tar.gz To my naive eyes, it looks like Samba is performing the following operations in response to me hitting the print button: Scenario (a): SMBnttrans -> SMBnttrans -> SMBntcreateX -> SMBclose -> SMBnttrans -> SMBnttrans -> SMBntcreateX -> SMBtrans2 -> SMBfindclose -> SMBtrans2 ->SMBntcreateX -> SMBntcreateX -> ... Scenario (b): SMBnttrans -> SMBtrans2 Does this mean anything to anyone? Any helpful pointers on what I can try next to get to the bottom of this? Thanks for reading this rather long email, Mark -- -- Mark DixonEmail: [EMAIL PROTECTED] Systems Integration Tel (int): 34371 Information Systems Tel (ext): 020 7679 4371 University College London, UK -- Related samba mailing list messages: From: "Jay D. Anderson" <[EMAIL PROTECTED]> Date: Thu, 19 Jul 2001 08:39:17 -0500 Message-ID: <[EMAIL PROTECTED]> ( http://marc.theaimsgroup.com/?l=samba&m=99555029423188&w=2 ) From: Adrian Barker <[EMAIL PROTECTED]> Date: Thu, 02 Nov 2000 15:47:22 + Message-Id: <[EMAIL PROTECTED]> ( http://marc.theaimsgroup.com/?l=samba&m=97474174027152&w=2 ) From: "Tulipant Gergely" <[EMAIL PROTECTED]> Date: Mon, 20 Nov 2000 17:39:47 +0100 Message-ID: <3A1961E3.5709.1316996@localhost> ( http://marc.theaimsgroup.com/?l=samba&m=97474174027152&w=2 ) -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Printing problems.
I have a situation where users authenticate to a samba domain on Windows 2000 clients, but are unable to print to printers that are attached to Windows 2000 PC's (also part of the domain) and being shared. If I login as a user who has sysadmin priviliges there is no problem. If I login as a normal user to a PC, and this printer has a default printer setup, which is in effect a share from another PC, the normal user does not pick up this (i.e. if you view start --> settings --> printers, the machines default printer is not present). If I add the printer manually I can see the printer, but when I try printing although the job appears to be accepted nothing actually prints out. Thanks for any help, CIM. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Printing problems with Samba 2.2.3a
Replace -P %p in the print command with the absolute path to the printer. Possible bug in Samba. --- Eric Keeley <[EMAIL PROTECTED]> skrev: > Hi, > > I've been using Samba 2.0.5 successfully for a long > time and am now trying > to configure 2.2.3a under Debian GNU/Linux 3.0. > I've succeeded with the > exception of one printer share. What makes this > frustrating is that the > share is mostly functional, but I haven't been able > to find my problem > described anywhere else. > > We have two HP printers, a LaserJet 4000N and a > LaserJet 5N, which I'd like > to share using the new SPOOLSS printer > functionality. Following the > instructions in the Printing How-to, I was able to > upload drivers for both > printers to the Samba server from an NT4 (SP6a) > Workstation. Printing to > the 4000N now works flawlessly. My problems are > with the 5N. When I try > to print a test page with "Print Test Page" button, > NT4 WS (SP6a) responds > with > > "Test page failed to print. Would you like to view > the print trouble > shooter for assistance? The data area passed to a > system call is too small." > > Also, several of the settings on the "Device" tab > are > unavailable. Strangely, I am able to print to this > printer with my other > application programs with no apparent problem. > > In an attempt to fix this problem, I uninstalled its > driver according MS > Knowledge Base article > http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q135406&; > and > deleted its driver files in print$/W32X86/2. When I > subsequently attempted > to upload the driver, I received a copy error. > Apparently, this is > because NT4 was attempting to copy the files to > $print/W32X86 instead of > print$/W32X86/2. > > Here are my questions: > > 1. Does anyone know what caused the original > problem with the failed > printing of the test page and the unavailable > options in the device tab? > > 2. What's the right way to remove printer drivers > after they've been uploaded? > > 3. How does one give NT4 WS amnesia about a print > driver? For example, > even after I deleted the files and registry settings > for the HP5N as > specified in Q13506, its driver was still listed as > an option on the > General tab. Are there other registry settings that > need to be altered? > > Here are the share definitions for print$ and the > LaserJet 5N: > > [print$] > path = /usr/local/windows/printers > read only = yes > write list = @respgms > browseable = no > > [hp5n] > printer name = hp5npcl > printable = yes > printing = BSD > print command = /usr/bin/lpr -P%p %s > browseable = yes > path = /tmp > > > Thanks for any help, > > Eric > > > -- > To unsubscribe from this list go to the following > URL and read the > instructions: http://lists.samba.org/mailman/listinfo/samba __ Se den nye Yahoo! Mail på http://no.yahoo.com/ Nytt design, enklere å bruke, alltid tilgang til Adressebok, Kalender og Notisbok -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Printing problems with Samba 2.2.3a
Hi, I've been using Samba 2.0.5 successfully for a long time and am now trying to configure 2.2.3a under Debian GNU/Linux 3.0. I've succeeded with the exception of one printer share. What makes this frustrating is that the share is mostly functional, but I haven't been able to find my problem described anywhere else. We have two HP printers, a LaserJet 4000N and a LaserJet 5N, which I'd like to share using the new SPOOLSS printer functionality. Following the instructions in the Printing How-to, I was able to upload drivers for both printers to the Samba server from an NT4 (SP6a) Workstation. Printing to the 4000N now works flawlessly. My problems are with the 5N. When I try to print a test page with "Print Test Page" button, NT4 WS (SP6a) responds with "Test page failed to print. Would you like to view the print trouble shooter for assistance? The data area passed to a system call is too small." Also, several of the settings on the "Device" tab are unavailable. Strangely, I am able to print to this printer with my other application programs with no apparent problem. In an attempt to fix this problem, I uninstalled its driver according MS Knowledge Base article http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q135406&; and deleted its driver files in print$/W32X86/2. When I subsequently attempted to upload the driver, I received a copy error. Apparently, this is because NT4 was attempting to copy the files to $print/W32X86 instead of print$/W32X86/2. Here are my questions: 1. Does anyone know what caused the original problem with the failed printing of the test page and the unavailable options in the device tab? 2. What's the right way to remove printer drivers after they've been uploaded? 3. How does one give NT4 WS amnesia about a print driver? For example, even after I deleted the files and registry settings for the HP5N as specified in Q13506, its driver was still listed as an option on the General tab. Are there other registry settings that need to be altered? Here are the share definitions for print$ and the LaserJet 5N: [print$] path = /usr/local/windows/printers read only = yes write list = @respgms browseable = no [hp5n] printer name = hp5npcl printable = yes printing = BSD print command = /usr/bin/lpr -P%p %s browseable = yes path = /tmp Thanks for any help, Eric -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Printing problems
Post: 1. Your printing system (lprng, etc.) 2. Your smb.conf 3. Your printer 4. Your /etc/printcap 5. The print driver you are using for your printer. 6. Your flavor of unix/linux. 7. The client OS. This information may help. Joel On Sun, Jun 16, 2002 at 03:11:25PM -0400, Joe Carmon wrote: > When printing locally the printer works fine, but when I try to print from > a client computer the following message prints out. > > Unable to open the initial device, quitting. > > Can any body help with this problem. > > > > -- > 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
[Samba] Printing problems
When printing locally the printer works fine, but when I try to print from a client computer the following message prints out. Unable to open the initial device, quitting. Can any body help with this problem. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Printing problems
This showed up on a Windows XP machine with 2.2.4 -- I'm reverting back to a 2.2.4-pre version that was running fine (at least I never saw this problem before I upgraded the other day). [2002/06/06 18:30:12, 0] rpc_client/cli_pipe.c:rpc_api_pipe(359) cli_pipe: return critical error. Error was NT_STATUS_INVALID_PIPE_STATE [2002/06/06 18:30:12, 0] rpc_server/srv_spoolss_nt.c:srv_spoolss_replycloseprinter(177) srv_spoolss_replycloseprinter: reply_close_printer failed [DOS code 0x001f]. [2002/06/06 18:30:12, 0] rpc_client/cli_pipe.c:rpc_api_pipe(359) cli_pipe: return critical error. Error was NT_STATUS_INVALID_PIPE_STATE [2002/06/06 18:30:12, 0] rpc_server/srv_spoolss_nt.c:srv_spoolss_replycloseprinter(177) srv_spoolss_replycloseprinter: reply_close_printer failed [DOS code 0x001f]. [2002/06/06 18:30:12, 0] rpc_client/cli_pipe.c:rpc_api_pipe(359) cli_pipe: return critical error. Error was NT_STATUS_INVALID_PIPE_STATE [2002/06/06 18:30:12, 0] rpc_server/srv_spoolss_nt.c:srv_spoolss_replycloseprinter(177) srv_spoolss_replycloseprinter: reply_close_printer failed [DOS code 0x001f]. [2002/06/06 18:30:12, 0] rpc_client/cli_pipe.c:rpc_api_pipe(359) cli_pipe: return critical error. Error was NT_STATUS_INVALID_PIPE_STATE [2002/06/06 18:30:12, 0] rpc_server/srv_spoolss_nt.c:srv_spoolss_replycloseprinter(177) srv_spoolss_replycloseprinter: reply_close_printer failed [DOS code 0x001f]. Michael D. Black [EMAIL PROTECTED] http://www.csihq.com/ http://www.csihq.com/~mike 321-676-2923, x203 Melbourne FL -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Printing Problems from ACT with samba
On Thu, 9 May 2002, Shaun Schembri wrote: > Hello everybody, > > I have a Windows 2000 SP2 on which I am running act and users use the > Terminal Server Client to access it. My problem is that when I try to > print from ACT I get the following error in the samba log file > > [2002/05/09 11:16:01, 0] > rpc_server/srv_spoolss.c:api_spoolss_open_printer_ex(42) > spoolss_io_q_open_printer_ex: unable to unmarshall > SPOOL_Q_OPEN_PRINTER_EX. > [2002/05/09 11:16:01, 0] rpc_server/srv_pipe.c:api_rpcTNP(1200) > api_rpcTNP: api_spoolss_rpc: SPOOLSS_OPENPRINTEREX failed. > > I am running samba 2.2.4 on a suse 7.2 machine. > > I have tried different drivers but still the same problem arises Arrggh!!! I thought we had this fixed! Send me a level 10 debug log of the client connection and the failure so I can fix it. Thanks. cheers, jerry - Hewlett-Packard http://www.hp.com SAMBA Team http://www.samba.org --http://www.plainjoe.org "Sam's Teach Yourself Samba in 24 Hours" 2ed. ISBN 0-672-32269-2 --"I never saved anything for the swim back." Ethan Hawk in Gattaca-- -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Printing Problems
Hi, need help! I have installed dual samba (both with the newest cvs) now I would like to print on the HEAD server (domain member). If I try to connect to the printer I get an errormessage :"The connection could not be established. There is not enough memory." What I am doing wrong or what is going wrong ??? Sascha -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
