[Samba] Printing defaults and registry.tdb
Hi all, I'm still having problems with certain print drivers with samba displaying the defaults/preferences differently (==wrongly) from a samba share comapred with a windows share (driver in question is HP universal 32bit, but i also trouble with a load of other drivers such as all Ricoh PCL6 I've tried). I'm now pretty sure its to do with how the settings are saved in registry.tdb - comparing the tdb entries with the matching entries on a windows print server there are differences. Is there any documentation on how stuff is stored in registry.tdb? I really need to get this working. I assume its a bug in there somewhere and I'd really like to fix it, so any help would be great. Do I need to get onto the samba-technical list for this? cheers Jim -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Printing from Samba4
On 27/09/12 22:25, Florian Scholz wrote: try http://wiki.samba.org/index.php/Samba4/HOWTO#Step_13:_Setup_a_Printer_share 2012/9/27 steve st...@steve-ss.com mailto:st...@steve-ss.com Hi I have a printer connected to a Samba4 AD machine. I set it up using CUPS. It works fine. Is there a howto as to what I need to add to smb.conf to be able to print from windows boxes connected to the domain? Hi Thanks for the link. I can see the printer (HP Deskjet F2200) in Printers and Faxes without doing anything. I can send files to it too but nothing prints. The files I send appear in the print queue and disappear as if they have been spooled. I think the problem is tha I can't install a windows driver for it: Everything is OK until step 4 Click File - Server Properties Here, everything is greyed out So I can't do step 5: On the Drivers Tab, Click 'Add...', then 'Next' because 'Add. . .' is greyed out. It's as if the Domain Administrator does not have permission to do anything from a client. Any ideas where I can check? Cheers, Steve -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Printing from Samba4
Hi I have a printer connected to a Samba4 AD machine. I set it up using CUPS. It works fine. Is there a howto as to what I need to add to smb.conf to be able to print from windows boxes connected to the domain? Thanks Steve -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] printing issue after update to 3.6.1
Hello, we've updated to 3.6.1 yesterday, and since encounter problems with printing for some users. There's a descriptive error in the log.smbd, but I can't see what to do about it really (the rest of the, admittedly fairly ancient system, is the same base system as the previous 3.5.5 - only a couple of security updates were patched in during downtime). The message in log.smbd is: adminpc-rmarx (158.64.1.188) connect to service SuperJam PCL6 initially as user Administrator (uid=1003, gid=100) (pid 15885) [2012/01/25 13:14:01.334500, 2] rpc_client/cli_winreg_spoolss.c:898(winreg_create_printer) winreg_create_printer: Skipping, SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\Printers\SuperJam PCL6 already exists [2012/01/25 13:14:01.575723, 0] printing/print_cups.c:940(cups_job_submit) cups_job_submit: failed to parse jobid from name /usr/local/samba/var/spool/samba/smbprn..CXRIP3 [2012/01/25 13:14:11.775067, 1] smbd/service.c:1291(close_cnum) adminpc-rmarx (158.64.1.188) closed connection to service SuperJam PCL6 And indeed, looking into the spool directory, the file names which used to encode the jobid now don't any more. For illustration, a few old spooled jobs in the right format as well: [... snip lots more of the same ...] -rw--- 1 rmarx users 0 Jan 25 15:29 smbprn..zfgbGg -rw--- 1 rmarx users 0 Jan 25 14:41 smbprn..zjVnMg -rw--- 1 rmarx users 0 Jan 25 08:46 smbprn..zpuUmw -rw--- 1 rmarx users 0 Jan 25 15:25 smbprn..zqdI3C -rw--- 1 rmarx users 0 Jan 25 15:09 smbprn..zqu3kj -rw--- 1 rmarx users 0 Jan 25 14:46 smbprn..zx3GuR -rw--- 1 rmarx users 0 Jan 25 15:28 smbprn..zxNUxy -rw--- 1 tduhautpas users 1657499 Apr 21 2008 smbprn.0676.rcl7r5 -rw--- 1 tduhautpas users 3441093 Apr 21 2008 smbprn.0678.eJYB0d -rw--- 1 tduhautpas users 1587952 Apr 21 2008 smbprn.0679.0TbJsK -rw--- 1 tduhautpas users 581632 May 25 2009 smbprn.1277.TEBFAb -rw--- 1 abarthel users6774 Nov 15 2007 smbprn.2633.psJWJh -rw--- 1 lbattani users 53156 Dec 14 2007 smbprn.3546.e7BsgC -rw--- 1 yschaafusers8179 Oct 17 2008 smbprn.6035.9IfNcf So, for some reasons, jobid gets lost. Strangely enough, the file size is also zero. I'm sort of lost what would cause this. The thing I could imagine is our fairly ancient cups on the system (1.2.7) and that maybe 3.6.1 doesn't support some legacy CUPS API stuff that 3.5.5 still did. That's the only straw I'm holding onto. Can anyone help out here? Greetings, Stefan Winter -- Stefan WINTER Ingenieur de Recherche Fondation RESTENA - Réseau Téléinformatique de l'Education Nationale et de la Recherche 6, rue Richard Coudenhove-Kalergi L-1359 Luxembourg Tel: +352 424409 1 Fax: +352 422473 signature.asc Description: OpenPGP digital signature -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] printing issue after update to 3.6.1
Hi Stefan, On Wed, 25 Jan 2012 15:44:31 +0100 Stefan Winter stefan.win...@restena.lu wrote: ... So, for some reasons, jobid gets lost. Strangely enough, the file size is also zero. I'm sort of lost what would cause this. The thing I could imagine is our fairly ancient cups on the system (1.2.7) and that maybe 3.6.1 doesn't support some legacy CUPS API stuff that 3.5.5 still did. That's the only straw I'm holding onto. Can anyone help out here? The spoolss print job file open code-path has changed recently, looking at print_spool_open() it looks like the job file is created without taking the print jobid into account. Please raise a bug with your logs attached. Cheers, David -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] printing issue after update to 3.6.1
Hi, thanks for the quick reply - I just opened bug 8719. https://bugzilla.samba.org/show_bug.cgi?id=8719 Greetings, Stefan Winter On 25.01.2012 17:59, David Disseldorp wrote: Hi Stefan, On Wed, 25 Jan 2012 15:44:31 +0100 Stefan Winter stefan.win...@restena.lu wrote: ... So, for some reasons, jobid gets lost. Strangely enough, the file size is also zero. I'm sort of lost what would cause this. The thing I could imagine is our fairly ancient cups on the system (1.2.7) and that maybe 3.6.1 doesn't support some legacy CUPS API stuff that 3.5.5 still did. That's the only straw I'm holding onto. Can anyone help out here? The spoolss print job file open code-path has changed recently, looking at print_spool_open() it looks like the job file is created without taking the print jobid into account. Please raise a bug with your logs attached. Cheers, David -- Stefan WINTER Ingenieur de Recherche Fondation RESTENA - Réseau Téléinformatique de l'Education Nationale et de la Recherche 6, rue Richard Coudenhove-Kalergi L-1359 Luxembourg Tel: +352 424409 1 Fax: +352 422473 signature.asc Description: OpenPGP digital signature -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba Printing api_rpcTNP: \spoolss: SPOOLSS_OPENPRINTEREX failed
Last week i backported weezys 3.5.11 samba package to lenny and I still go these random errors. I went back to lenny version 3.2.5 and since then printing works fine. Guess that sorts out network related issues. Will monitor printing for an few more days and then try an samba version which supports win7 clients. achim~ -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba Printing api_rpcTNP: \spoolss: SPOOLSS_OPENPRINTEREX failed
Same problem here, with the crystal report software too. I tried UTF-8 and UTF8, it makes no difference. Am 16.09.2011 12:02:32, schrieb Achim Gottinger: After an day without issues i just received an phone call about an printing issue and i found a few illegal multibyte sequence errors in the log file again. Unfortunately i can not reproduce the situation where this error occured an second try to print that document out of the archive worked but since it's an crystal report form generated out of an database from our business software something may be different when printing from the archive. Hope i'll get an reproducible situation so i can grab an wireshark trace and more detailed samba log info's. achim~ Am 15.09.2011 17:01, schrieb Achim Gottinger: Update: Checked logs of all my debian print servers and none had these error messages today, i guess i had forgotten to restart samba on that server whom still showed the error. I had also found that erroro message on a few other servers with an missing unix charset line whom i all moodified and restarted. (There is still a chance that they did not print anything which triggered that error.) Here is an bug report for that problem, that's where i found that unix charset fix. https://bugzilla.samba.org/show_bug.cgi?id=8082 Checked the default if that variable is not explicity declared in smb.conf with terstparam -v and it is unix charset = UTF-8 display charset = LOCALE Seems debian has an problem with UTF-8 but not with UTF8. =-O These are my locale settings #locale LANG=de_DE.UTF-8 LC_CTYPE=de_DE.UTF-8 LC_NUMERIC=de_DE.UTF-8 LC_TIME=de_DE.UTF-8 LC_COLLATE=de_DE.UTF-8 LC_MONETARY=de_DE.UTF-8 LC_MESSAGES=de_DE.UTF-8 LC_PAPER=de_DE.UTF-8 LC_NAME=de_DE.UTF-8 LC_ADDRESS=de_DE.UTF-8 LC_TELEPHONE=de_DE.UTF-8 LC_MEASUREMENT=de_DE.UTF-8 LC_IDENTIFICATION=de_DE.UTF-8 LC_ALL= https://bugzilla.samba.org/show_bug.cgi?id=8082 Am 15.09.2011 01:04, schrieb Achim Gottinger: It is odd here also, on one server (debian lenny with samba 3.5.6 from backports) using dos charset = 850 unix charset = UTF8 fixed that issue on an other server (same osand versions) i also had to add the unix charset line and it worked for an document which did not work without and generated an error log entry like yours. looking at the log file i still see a few of those SPOOLSS error messages. Users did not report problems but i have to ask em if they have had issues with printing this week. If the error occures there is no print job generated at the cups server at all and errors like those above appear in log.smbd [2011/09/14 16:09:28.780842, 0] lib/charcnv.c:650(convert_string_talloc) Conversion error: Illegal multibyte sequence(@DD^W^THDD^X^T^A^D) [2011/09/14 16:09:28.780969, 0] rpc_server/srv_pipe.c:2439(api_rpcTNP) api_rpcTNP: \spoolss: SPOOLSS_OPENPRINTEREX failed. [2011/09/14 16:09:29.001633, 0] lib/charcnv.c:650(convert_string_talloc) Conversion error: Illegal multibyte sequence(@DD^W^THDD^X^T^A^D) [2011/09/14 16:09:29.001724, 0] rpc_server/srv_pipe.c:2439(api_rpcTNP) api_rpcTNP: \spoolss: SPOOLSS_OPENPRINTEREX failed. [2011/09/14 16:20:05.843419, 0] lib/charcnv.c:650(convert_string_talloc) Conversion error: Illegal multibyte sequence(88DF^H^NE09F^T^T`D9^K^T) [2011/09/14 16:20:05.843511, 0] rpc_server/srv_pipe.c:2439(api_rpcTNP) api_rpcTNP: \spoolss: SPOOLSS_OPENPRINTEREX failed. [2011/09/14 16:20:06.107415, 0] lib/charcnv.c:650(convert_string_talloc) Conversion error: Illegal multibyte sequence(88DF^H^NE09F^T^T`D9^K^T) [2011/09/14 16:20:06.107788, 0] rpc_server/srv_pipe.c:2439(api_rpcTNP) achim~ -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba Printing api_rpcTNP: \spoolss: SPOOLSS_OPENPRINTEREX failed
Am 26.09.2011 09:52, schrieb Claus Rosenberger: Same problem here, with the crystal report software too. I tried UTF-8 and UTF8, it makes no difference. Am 16.09.2011 12:02:32, schrieb Achim Gottinger: Was tricked by randomness here, it does not make a difference here also and i'm still getting those errors. At least i captured and uploaded detailed log's of that weird error to the bug report, hope an developer will take an look next week after this microsoft ad event is over. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] OS X LION issue with Samba printing
I am facing the same issue in our enterprise environment after upgrading to Lion. I tried re-adding the printer, but every time I send a document to it I get “Printer paused.” Resuming the printer results in it immediately being “paused” again. Hope there is a fix released in the near future. Steve -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba Printing api_rpcTNP: \spoolss: SPOOLSS_OPENPRINTEREX failed
After an day without issues i just received an phone call about an printing issue and i found a few illegal multibyte sequence errors in the log file again. Unfortunately i can not reproduce the situation where this error occured an second try to print that document out of the archive worked but since it's an crystal report form generated out of an database from our business software something may be different when printing from the archive. Hope i'll get an reproducible situation so i can grab an wireshark trace and more detailed samba log info's. achim~ Am 15.09.2011 17:01, schrieb Achim Gottinger: Update: Checked logs of all my debian print servers and none had these error messages today, i guess i had forgotten to restart samba on that server whom still showed the error. I had also found that erroro message on a few other servers with an missing unix charset line whom i all moodified and restarted. (There is still a chance that they did not print anything which triggered that error.) Here is an bug report for that problem, that's where i found that unix charset fix. https://bugzilla.samba.org/show_bug.cgi?id=8082 Checked the default if that variable is not explicity declared in smb.conf with terstparam -v and it is unix charset = UTF-8 display charset = LOCALE Seems debian has an problem with UTF-8 but not with UTF8. =-O These are my locale settings #locale LANG=de_DE.UTF-8 LC_CTYPE=de_DE.UTF-8 LC_NUMERIC=de_DE.UTF-8 LC_TIME=de_DE.UTF-8 LC_COLLATE=de_DE.UTF-8 LC_MONETARY=de_DE.UTF-8 LC_MESSAGES=de_DE.UTF-8 LC_PAPER=de_DE.UTF-8 LC_NAME=de_DE.UTF-8 LC_ADDRESS=de_DE.UTF-8 LC_TELEPHONE=de_DE.UTF-8 LC_MEASUREMENT=de_DE.UTF-8 LC_IDENTIFICATION=de_DE.UTF-8 LC_ALL= https://bugzilla.samba.org/show_bug.cgi?id=8082 Am 15.09.2011 01:04, schrieb Achim Gottinger: It is odd here also, on one server (debian lenny with samba 3.5.6 from backports) using dos charset = 850 unix charset = UTF8 fixed that issue on an other server (same osand versions) i also had to add the unix charset line and it worked for an document which did not work without and generated an error log entry like yours. looking at the log file i still see a few of those SPOOLSS error messages. Users did not report problems but i have to ask em if they have had issues with printing this week. If the error occures there is no print job generated at the cups server at all and errors like those above appear in log.smbd [2011/09/14 16:09:28.780842, 0] lib/charcnv.c:650(convert_string_talloc) Conversion error: Illegal multibyte sequence(@DD^W^THDD^X^T^A^D) [2011/09/14 16:09:28.780969, 0] rpc_server/srv_pipe.c:2439(api_rpcTNP) api_rpcTNP: \spoolss: SPOOLSS_OPENPRINTEREX failed. [2011/09/14 16:09:29.001633, 0] lib/charcnv.c:650(convert_string_talloc) Conversion error: Illegal multibyte sequence(@DD^W^THDD^X^T^A^D) [2011/09/14 16:09:29.001724, 0] rpc_server/srv_pipe.c:2439(api_rpcTNP) api_rpcTNP: \spoolss: SPOOLSS_OPENPRINTEREX failed. [2011/09/14 16:20:05.843419, 0] lib/charcnv.c:650(convert_string_talloc) Conversion error: Illegal multibyte sequence(88DF^H^NE09F^T^T`D9^K^T) [2011/09/14 16:20:05.843511, 0] rpc_server/srv_pipe.c:2439(api_rpcTNP) api_rpcTNP: \spoolss: SPOOLSS_OPENPRINTEREX failed. [2011/09/14 16:20:06.107415, 0] lib/charcnv.c:650(convert_string_talloc) Conversion error: Illegal multibyte sequence(88DF^H^NE09F^T^T`D9^K^T) [2011/09/14 16:20:06.107788, 0] rpc_server/srv_pipe.c:2439(api_rpcTNP) achim~ -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba Printing api_rpcTNP: \spoolss: SPOOLSS_OPENPRINTEREX failed
Update: Checked logs of all my debian print servers and none had these error messages today, i guess i had forgotten to restart samba on that server whom still showed the error. I had also found that erroro message on a few other servers with an missing unix charset line whom i all moodified and restarted. (There is still a chance that they did not print anything which triggered that error.) Here is an bug report for that problem, that's where i found that unix charset fix. https://bugzilla.samba.org/show_bug.cgi?id=8082 Checked the default if that variable is not explicity declared in smb.conf with terstparam -v and it is unix charset = UTF-8 display charset = LOCALE Seems debian has an problem with UTF-8 but not with UTF8. =-O These are my locale settings #locale LANG=de_DE.UTF-8 LC_CTYPE=de_DE.UTF-8 LC_NUMERIC=de_DE.UTF-8 LC_TIME=de_DE.UTF-8 LC_COLLATE=de_DE.UTF-8 LC_MONETARY=de_DE.UTF-8 LC_MESSAGES=de_DE.UTF-8 LC_PAPER=de_DE.UTF-8 LC_NAME=de_DE.UTF-8 LC_ADDRESS=de_DE.UTF-8 LC_TELEPHONE=de_DE.UTF-8 LC_MEASUREMENT=de_DE.UTF-8 LC_IDENTIFICATION=de_DE.UTF-8 LC_ALL= https://bugzilla.samba.org/show_bug.cgi?id=8082 Am 15.09.2011 01:04, schrieb Achim Gottinger: It is odd here also, on one server (debian lenny with samba 3.5.6 from backports) using dos charset = 850 unix charset = UTF8 fixed that issue on an other server (same osand versions) i also had to add the unix charset line and it worked for an document which did not work without and generated an error log entry like yours. looking at the log file i still see a few of those SPOOLSS error messages. Users did not report problems but i have to ask em if they have had issues with printing this week. If the error occures there is no print job generated at the cups server at all and errors like those above appear in log.smbd [2011/09/14 16:09:28.780842, 0] lib/charcnv.c:650(convert_string_talloc) Conversion error: Illegal multibyte sequence(@DD^W^THDD^X^T^A^D) [2011/09/14 16:09:28.780969, 0] rpc_server/srv_pipe.c:2439(api_rpcTNP) api_rpcTNP: \spoolss: SPOOLSS_OPENPRINTEREX failed. [2011/09/14 16:09:29.001633, 0] lib/charcnv.c:650(convert_string_talloc) Conversion error: Illegal multibyte sequence(@DD^W^THDD^X^T^A^D) [2011/09/14 16:09:29.001724, 0] rpc_server/srv_pipe.c:2439(api_rpcTNP) api_rpcTNP: \spoolss: SPOOLSS_OPENPRINTEREX failed. [2011/09/14 16:20:05.843419, 0] lib/charcnv.c:650(convert_string_talloc) Conversion error: Illegal multibyte sequence(88DF^H^NE09F^T^T`D9^K^T) [2011/09/14 16:20:05.843511, 0] rpc_server/srv_pipe.c:2439(api_rpcTNP) api_rpcTNP: \spoolss: SPOOLSS_OPENPRINTEREX failed. [2011/09/14 16:20:06.107415, 0] lib/charcnv.c:650(convert_string_talloc) Conversion error: Illegal multibyte sequence(88DF^H^NE09F^T^T`D9^K^T) [2011/09/14 16:20:06.107788, 0] rpc_server/srv_pipe.c:2439(api_rpcTNP) achim~ -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba Printing api_rpcTNP: \spoolss: SPOOLSS_OPENPRINTEREX failed
Thats really annoying because the printing with samba is not possible, just printing directly to cups is possible. The clients are working with UTF-8, the server is working with UTF-8, don't know why character conversion should be a problem here. More details: [2011/09/14 13:55:24.173846, 5] rpc_server/srv_pipe.c:2367(api_pipe_request) Requested \PIPE\\spoolss [2011/09/14 13:55:24.173878, 4] rpc_server/srv_pipe.c:2404(api_rpcTNP) api_rpcTNP: \spoolss op 0x45 - api_rpcTNP: rpc command: SPOOLSS_OPENPRINTEREX [2011/09/14 13:55:24.173912, 6] rpc_server/srv_pipe.c:2434(api_rpcTNP) api_rpc_cmds[69].fn == 0x7f844834b140 [2011/09/14 13:55:24.173953, 3] lib/charcnv.c:644(convert_string_talloc) convert_string_talloc: Conversion error: Illegal multibyte sequence(B3Û8A8A8AF89C^G) [2011/09/14 13:55:24.173986, 0] lib/charcnv.c:650(convert_string_talloc) Conversion error: Illegal multibyte sequence(B3Û8A8A8AF89C^G) [2011/09/14 13:55:24.174017, 1] ../librpc/ndr/ndr.c:395(ndr_pull_error) ndr_pull_error(5): Bad character conversion [2011/09/14 13:55:24.174064, 0] rpc_server/srv_pipe.c:2439(api_rpcTNP) api_rpcTNP: \spoolss: SPOOLSS_OPENPRINTEREX failed. [2011/09/14 13:55:24.174099, 3] rpc_server/srv_pipe_hnd.c:344(free_pipe_context) free_pipe_context: destroying talloc pool of size 0 [2011/09/14 13:55:24.174130, 3] rpc_server/srv_pipe_hnd.c:656(process_complete_pdu) process_complete_pdu: DCE/RPC fault sent on pipe \spoolss [2011/09/14 13:55:24.174161, 10] rpc_server/srv_pipe_hnd.c:180(set_incoming_fault) set_incoming_fault: Setting fault state on pipe \spoolss [2011/09/14 13:55:24.174193, 5] rpc_parse/parse_prs.c:89(prs_debug) 00 smb_io_rpc_hdr major : 05 0001 minor : 00 0002 pkt_type : 03 0003 flags : 23 0004 pack_type0: 10 0005 pack_type1: 00 0006 pack_type2: 00 0007 pack_type3: 00 0008 frag_len : 0020 000a auth_len : 000c call_id : 796c [2011/09/14 13:55:24.174346, 5] rpc_parse/parse_prs.c:89(prs_debug) 10 smb_io_rpc_hdr_resp resp 0010 alloc_hint: 0014 context_id: 0016 cancel_ct : 00 0017 reserved : 00 [2011/09/14 13:55:24.174431, 5] rpc_parse/parse_prs.c:89(prs_debug) 18 smb_io_rpc_hdr_fault fault 0018 status : DCERPC_FAULT_OP_RNG_ERROR 001c reserved: [2011/09/14 13:55:24.174487, 10] rpc_server/srv_pipe_hnd.c:776(write_to_internal_pipe) write_to_pipe: data_used = 2670 [2011/09/14 13:55:24.174538, 6] rpc_server/srv_pipe_hnd.c:813(read_from_internal_pipe) name: \spoolss len: 1024 [2011/09/14 13:55:24.174573, 10] rpc_server/srv_pipe_hnd.c:854(read_from_internal_pipe) read_from_pipe: \spoolss: current_pdu_len = 32, current_pdu_sent = 0 returning 32 bytes. Am 19.08.2011 11:49:27, schrieb Claus Rosenberger: After connecting the same printers directly to cups using the same drivers the printouts are available without any problems. So probably some conversion inside of samba will cancel the printjobs. Am 11.08.2011 11:32, schrieb Claus Rosenberger: Hello, after upgrading to samba 3.5.6 of Debian Squeeze some printouts will not printed. The same prinjob will printed after a couple of tries. I increased the loglevel and there are only a few messages which showing whtat could be the problem. The printjobs doesn't arrive at cups. [2011/08/10 11:32:12.700665, 0] lib/charcnv.c:650(convert_string_talloc) Conversion error: Illegal multibyte sequence(E8DE^A^H 8C^R ) [2011/08/10 11:32:12.700720, 1] ../librpc/ndr/ndr.c:395(ndr_pull_error) ndr_pull_error(5): Bad character conversion [2011/08/10 11:32:12.700756, 0] rpc_server/srv_pipe.c:2439(api_rpcTNP) api_rpcTNP: \spoolss: SPOOLSS_OPENPRINTEREX failed. [2011/08/10 11:32:13.901183, 0] lib/charcnv.c:650(convert_string_talloc) Conversion error: Illegal multibyte sequence(E8DE^A^H 8C^R ) [2011/08/10 11:32:13.924149, 1] ../librpc/ndr/ndr.c:395(ndr_pull_error) ndr_pull_error(5): Bad character conversion [2011/08/10 11:32:13.924206, 0] rpc_server/srv_pipe.c:2439(api_rpcTNP) api_rpcTNP: \spoolss: SPOOLSS_OPENPRINTEREX failed. The printer is a Konica Minolta bizhup 40P, which is installed on client with Point and Print and the newest ppd files from Konica Minolta. What could be the problem? Thank you Claus -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba Printing api_rpcTNP: \spoolss: SPOOLSS_OPENPRINTEREX failed
From the Windows side the samba connected printers show printer not connected if the problem appears, on all clients the same time. But Cups connected printers will be shown as Printer Ready. This situation is just a few minutes, now it was 45 minutes, but no more interesting things in the logfiles. Perhaps somebody knows whicn keywords to search for. Am 14.09.2011 14:03:37, schrieb Claus Rosenberger: Thats really annoying because the printing with samba is not possible, just printing directly to cups is possible. The clients are working with UTF-8, the server is working with UTF-8, don't know why character conversion should be a problem here. More details: [2011/09/14 13:55:24.173846, 5] rpc_server/srv_pipe.c:2367(api_pipe_request) Requested \PIPE\\spoolss [2011/09/14 13:55:24.173878, 4] rpc_server/srv_pipe.c:2404(api_rpcTNP) api_rpcTNP: \spoolss op 0x45 - api_rpcTNP: rpc command: SPOOLSS_OPENPRINTEREX [2011/09/14 13:55:24.173912, 6] rpc_server/srv_pipe.c:2434(api_rpcTNP) api_rpc_cmds[69].fn == 0x7f844834b140 [2011/09/14 13:55:24.173953, 3] lib/charcnv.c:644(convert_string_talloc) convert_string_talloc: Conversion error: Illegal multibyte sequence(B3Û8A8A8AF89C^G) [2011/09/14 13:55:24.173986, 0] lib/charcnv.c:650(convert_string_talloc) Conversion error: Illegal multibyte sequence(B3Û8A8A8AF89C^G) [2011/09/14 13:55:24.174017, 1] ../librpc/ndr/ndr.c:395(ndr_pull_error) ndr_pull_error(5): Bad character conversion [2011/09/14 13:55:24.174064, 0] rpc_server/srv_pipe.c:2439(api_rpcTNP) api_rpcTNP: \spoolss: SPOOLSS_OPENPRINTEREX failed. [2011/09/14 13:55:24.174099, 3] rpc_server/srv_pipe_hnd.c:344(free_pipe_context) free_pipe_context: destroying talloc pool of size 0 [2011/09/14 13:55:24.174130, 3] rpc_server/srv_pipe_hnd.c:656(process_complete_pdu) process_complete_pdu: DCE/RPC fault sent on pipe \spoolss [2011/09/14 13:55:24.174161, 10] rpc_server/srv_pipe_hnd.c:180(set_incoming_fault) set_incoming_fault: Setting fault state on pipe \spoolss [2011/09/14 13:55:24.174193, 5] rpc_parse/parse_prs.c:89(prs_debug) 00 smb_io_rpc_hdr major : 05 0001 minor : 00 0002 pkt_type : 03 0003 flags : 23 0004 pack_type0: 10 0005 pack_type1: 00 0006 pack_type2: 00 0007 pack_type3: 00 0008 frag_len : 0020 000a auth_len : 000c call_id : 796c [2011/09/14 13:55:24.174346, 5] rpc_parse/parse_prs.c:89(prs_debug) 10 smb_io_rpc_hdr_resp resp 0010 alloc_hint: 0014 context_id: 0016 cancel_ct : 00 0017 reserved : 00 [2011/09/14 13:55:24.174431, 5] rpc_parse/parse_prs.c:89(prs_debug) 18 smb_io_rpc_hdr_fault fault 0018 status : DCERPC_FAULT_OP_RNG_ERROR 001c reserved: [2011/09/14 13:55:24.174487, 10] rpc_server/srv_pipe_hnd.c:776(write_to_internal_pipe) write_to_pipe: data_used = 2670 [2011/09/14 13:55:24.174538, 6] rpc_server/srv_pipe_hnd.c:813(read_from_internal_pipe) name: \spoolss len: 1024 [2011/09/14 13:55:24.174573, 10] rpc_server/srv_pipe_hnd.c:854(read_from_internal_pipe) read_from_pipe: \spoolss: current_pdu_len = 32, current_pdu_sent = 0 returning 32 bytes. Am 19.08.2011 11:49:27, schrieb Claus Rosenberger: After connecting the same printers directly to cups using the same drivers the printouts are available without any problems. So probably some conversion inside of samba will cancel the printjobs. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba Printing api_rpcTNP: \spoolss: SPOOLSS_OPENPRINTEREX failed
It is odd here also, on one server (debian lenny with samba 3.5.6 from
backports) using
dos charset = 850
unix charset = UTF8
fixed that issue on an other server (same osand versions) i also had to
add the unix charset line and it worked for an document which did not
work without and generated an error log entry like yours. looking at the
log file i still see a few of those SPOOLSS error messages. Users did
not report problems but i have to ask em if they have had issues with
printing this week.
If the error occures there is no print job generated at the cups server
at all and errors like those above appear in log.smbd
[2011/09/14 16:09:28.780842, 0] lib/charcnv.c:650(convert_string_talloc)
Conversion error: Illegal multibyte sequence(@DD^W^THDD^X^T^A^D)
[2011/09/14 16:09:28.780969, 0] rpc_server/srv_pipe.c:2439(api_rpcTNP)
api_rpcTNP: \spoolss: SPOOLSS_OPENPRINTEREX failed.
[2011/09/14 16:09:29.001633, 0] lib/charcnv.c:650(convert_string_talloc)
Conversion error: Illegal multibyte sequence(@DD^W^THDD^X^T^A^D)
[2011/09/14 16:09:29.001724, 0] rpc_server/srv_pipe.c:2439(api_rpcTNP)
api_rpcTNP: \spoolss: SPOOLSS_OPENPRINTEREX failed.
[2011/09/14 16:20:05.843419, 0] lib/charcnv.c:650(convert_string_talloc)
Conversion error: Illegal multibyte
sequence(88DF^H^NE09F^T^T`D9^K^T)
[2011/09/14 16:20:05.843511, 0] rpc_server/srv_pipe.c:2439(api_rpcTNP)
api_rpcTNP: \spoolss: SPOOLSS_OPENPRINTEREX failed.
[2011/09/14 16:20:06.107415, 0] lib/charcnv.c:650(convert_string_talloc)
Conversion error: Illegal multibyte
sequence(88DF^H^NE09F^T^T`D9^K^T)
[2011/09/14 16:20:06.107788, 0] rpc_server/srv_pipe.c:2439(api_rpcTNP)
achim~
Am 14.09.2011 14:19, schrieb Claus Rosenberger:
From the Windows side the samba connected printers show printer not
connected if the problem appears, on all clients the same time. But Cups connected
printers will be shown as Printer Ready. This situation is just a few minutes, now it was
45 minutes, but no more interesting things in the logfiles. Perhaps somebody knows whicn
keywords to search for.
Am 14.09.2011 14:03:37, schrieb Claus Rosenberger:
Thats really annoying because the printing with samba is not possible, just
printing directly to cups is possible. The clients are working with UTF-8, the
server is working with UTF-8, don't know why character conversion should be a
problem here.
More details:
[2011/09/14 13:55:24.173846, 5] rpc_server/srv_pipe.c:2367(api_pipe_request)
Requested \PIPE\\spoolss
[2011/09/14 13:55:24.173878, 4] rpc_server/srv_pipe.c:2404(api_rpcTNP)
api_rpcTNP: \spoolss op 0x45 - api_rpcTNP: rpc command: SPOOLSS_OPENPRINTEREX
[2011/09/14 13:55:24.173912, 6] rpc_server/srv_pipe.c:2434(api_rpcTNP)
api_rpc_cmds[69].fn == 0x7f844834b140
[2011/09/14 13:55:24.173953, 3] lib/charcnv.c:644(convert_string_talloc)
convert_string_talloc: Conversion error: Illegal multibyte
sequence(B3Û8A8A8AF89C^G)
[2011/09/14 13:55:24.173986, 0] lib/charcnv.c:650(convert_string_talloc)
Conversion error: Illegal multibyte sequence(B3Û8A8A8AF89C^G)
[2011/09/14 13:55:24.174017, 1] ../librpc/ndr/ndr.c:395(ndr_pull_error)
ndr_pull_error(5): Bad character conversion
[2011/09/14 13:55:24.174064, 0] rpc_server/srv_pipe.c:2439(api_rpcTNP)
api_rpcTNP: \spoolss: SPOOLSS_OPENPRINTEREX failed.
[2011/09/14 13:55:24.174099, 3]
rpc_server/srv_pipe_hnd.c:344(free_pipe_context)
free_pipe_context: destroying talloc pool of size 0
[2011/09/14 13:55:24.174130, 3]
rpc_server/srv_pipe_hnd.c:656(process_complete_pdu)
process_complete_pdu: DCE/RPC fault sent on pipe \spoolss
[2011/09/14 13:55:24.174161, 10]
rpc_server/srv_pipe_hnd.c:180(set_incoming_fault)
set_incoming_fault: Setting fault state on pipe \spoolss
[2011/09/14 13:55:24.174193, 5] rpc_parse/parse_prs.c:89(prs_debug)
00 smb_io_rpc_hdr
major : 05
0001 minor : 00
0002 pkt_type : 03
0003 flags : 23
0004 pack_type0: 10
0005 pack_type1: 00
0006 pack_type2: 00
0007 pack_type3: 00
0008 frag_len : 0020
000a auth_len :
000c call_id : 796c
[2011/09/14 13:55:24.174346, 5] rpc_parse/parse_prs.c:89(prs_debug)
10 smb_io_rpc_hdr_resp resp
0010 alloc_hint:
0014 context_id:
0016 cancel_ct : 00
0017 reserved : 00
[2011/09/14 13:55:24.174431, 5] rpc_parse/parse_prs.c:89(prs_debug)
18 smb_io_rpc_hdr_fault fault
0018 status : DCERPC_FAULT_OP_RNG_ERROR
001c reserved:
[2011/09/14 13:55:24.174487, 10]
rpc_server/srv_pipe_hnd.c:776(write_to_internal_pipe)
write_to_pipe: data_used = 2670
[2011/09/14 13:55:24.174538, 6]
rpc_server/srv_pipe_hnd.c:813(read_from_internal_pipe)
name: \spoolss len: 1024
[2011/09/14 13:55:24.174573, 10]
rpc_server/srv_pipe_hnd.c:854(read_from_internal_pipe)
read_from_pipe: \spoolss: current_pdu_len = 32, current_pdu_sent = 0
returning 32 bytes.
Am
Re: [Samba] Samba Printing api_rpcTNP: \spoolss: SPOOLSS_OPENPRINTEREX failed
After connecting the same printers directly to cups using the same drivers the printouts are available without any problems. So probably some conversion inside of samba will cancel the printjobs. Am 11.08.2011 11:32, schrieb Claus Rosenberger: Hello, after upgrading to samba 3.5.6 of Debian Squeeze some printouts will not printed. The same prinjob will printed after a couple of tries. I increased the loglevel and there are only a few messages which showing whtat could be the problem. The printjobs doesn't arrive at cups. [2011/08/10 11:32:12.700665, 0] lib/charcnv.c:650(convert_string_talloc) Conversion error: Illegal multibyte sequence(E8DE^A^H 8C^R ) [2011/08/10 11:32:12.700720, 1] ../librpc/ndr/ndr.c:395(ndr_pull_error) ndr_pull_error(5): Bad character conversion [2011/08/10 11:32:12.700756, 0] rpc_server/srv_pipe.c:2439(api_rpcTNP) api_rpcTNP: \spoolss: SPOOLSS_OPENPRINTEREX failed. [2011/08/10 11:32:13.901183, 0] lib/charcnv.c:650(convert_string_talloc) Conversion error: Illegal multibyte sequence(E8DE^A^H 8C^R ) [2011/08/10 11:32:13.924149, 1] ../librpc/ndr/ndr.c:395(ndr_pull_error) ndr_pull_error(5): Bad character conversion [2011/08/10 11:32:13.924206, 0] rpc_server/srv_pipe.c:2439(api_rpcTNP) api_rpcTNP: \spoolss: SPOOLSS_OPENPRINTEREX failed. The printer is a Konica Minolta bizhup 40P, which is installed on client with Point and Print and the newest ppd files from Konica Minolta. What could be the problem? Thank you Claus -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Samba Printing api_rpcTNP: \spoolss: SPOOLSS_OPENPRINTEREX failed
Hello, after upgrading to samba 3.5.6 of Debian Squeeze some printouts will not printed. The same prinjob will printed after a couple of tries. I increased the loglevel and there are only a few messages which showing whtat could be the problem. The printjobs doesn't arrive at cups. [2011/08/10 11:32:12.700665, 0] lib/charcnv.c:650(convert_string_talloc) Conversion error: Illegal multibyte sequence(E8DE^A^H 8C^R ) [2011/08/10 11:32:12.700720, 1] ../librpc/ndr/ndr.c:395(ndr_pull_error) ndr_pull_error(5): Bad character conversion [2011/08/10 11:32:12.700756, 0] rpc_server/srv_pipe.c:2439(api_rpcTNP) api_rpcTNP: \spoolss: SPOOLSS_OPENPRINTEREX failed. [2011/08/10 11:32:13.901183, 0] lib/charcnv.c:650(convert_string_talloc) Conversion error: Illegal multibyte sequence(E8DE^A^H 8C^R ) [2011/08/10 11:32:13.924149, 1] ../librpc/ndr/ndr.c:395(ndr_pull_error) ndr_pull_error(5): Bad character conversion [2011/08/10 11:32:13.924206, 0] rpc_server/srv_pipe.c:2439(api_rpcTNP) api_rpcTNP: \spoolss: SPOOLSS_OPENPRINTEREX failed. The printer is a Konica Minolta bizhup 40P, which is installed on client with Point and Print and the newest ppd files from Konica Minolta. What could be the problem? Thank you Claus -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba Printing api_rpcTNP: \spoolss: SPOOLSS_OPENPRINTEREX failed
I guess you need to set unix charset = utf8 had a similar issue last week, which was fixed that way. achim~ Am 11.08.2011 11:32, schrieb Claus Rosenberger: Hello, after upgrading to samba 3.5.6 of Debian Squeeze some printouts will not printed. The same prinjob will printed after a couple of tries. I increased the loglevel and there are only a few messages which showing whtat could be the problem. The printjobs doesn't arrive at cups. [2011/08/10 11:32:12.700665, 0] lib/charcnv.c:650(convert_string_talloc) Conversion error: Illegal multibyte sequence(E8DE^A^H8C^R ) [2011/08/10 11:32:12.700720, 1] ../librpc/ndr/ndr.c:395(ndr_pull_error) ndr_pull_error(5): Bad character conversion [2011/08/10 11:32:12.700756, 0] rpc_server/srv_pipe.c:2439(api_rpcTNP) api_rpcTNP: \spoolss: SPOOLSS_OPENPRINTEREX failed. [2011/08/10 11:32:13.901183, 0] lib/charcnv.c:650(convert_string_talloc) Conversion error: Illegal multibyte sequence(E8DE^A^H8C^R ) [2011/08/10 11:32:13.924149, 1] ../librpc/ndr/ndr.c:395(ndr_pull_error) ndr_pull_error(5): Bad character conversion [2011/08/10 11:32:13.924206, 0] rpc_server/srv_pipe.c:2439(api_rpcTNP) api_rpcTNP: \spoolss: SPOOLSS_OPENPRINTEREX failed. The printer is a Konica Minolta bizhup 40P, which is installed on client with Point and Print and the newest ppd files from Konica Minolta. What could be the problem? Thank you Claus -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba Printing api_rpcTNP: \spoolss: SPOOLSS_OPENPRINTEREX failed
I already have set unix charset = utf8, so it must be another reason ... Am 11.08.2011 19:56, schrieb Achim Gottinger: I guess you need to set unix charset = utf8 had a similar issue last week, which was fixed that way. achim~ Am 11.08.2011 11:32, schrieb Claus Rosenberger: Hello, after upgrading to samba 3.5.6 of Debian Squeeze some printouts will not printed. The same prinjob will printed after a couple of tries. I increased the loglevel and there are only a few messages which showing whtat could be the problem. The printjobs doesn't arrive at cups. [2011/08/10 11:32:12.700665, 0] lib/charcnv.c:650(convert_string_talloc) Conversion error: Illegal multibyte sequence(E8DE^A^H8C^R ) [2011/08/10 11:32:12.700720, 1] ../librpc/ndr/ndr.c:395(ndr_pull_error) ndr_pull_error(5): Bad character conversion [2011/08/10 11:32:12.700756, 0] rpc_server/srv_pipe.c:2439(api_rpcTNP) api_rpcTNP: \spoolss: SPOOLSS_OPENPRINTEREX failed. [2011/08/10 11:32:13.901183, 0] lib/charcnv.c:650(convert_string_talloc) Conversion error: Illegal multibyte sequence(E8DE^A^H8C^R ) [2011/08/10 11:32:13.924149, 1] ../librpc/ndr/ndr.c:395(ndr_pull_error) ndr_pull_error(5): Bad character conversion [2011/08/10 11:32:13.924206, 0] rpc_server/srv_pipe.c:2439(api_rpcTNP) api_rpcTNP: \spoolss: SPOOLSS_OPENPRINTEREX failed. The printer is a Konica Minolta bizhup 40P, which is installed on client with Point and Print and the newest ppd files from Konica Minolta. What could be the problem? Thank you Claus -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] OS X LION issue with Samba printing
A user who upgraded to OS X Lion could no longer add the Samba hosted printers to his system. In this account the user logon rights are limited by workstation. Checking the Samba logs showed that OS X Lion was sending workstation as the NetBIOS name instead of the configured NetBIOS name (same as hostname). The configured hostname is clearly sent to the DHCP server. Once I allowed that user rights from workstation workstation the printers worked just fine. I am a bit concerned if the other Mac users (fortunately not too many - never thought I would say that) upgrade - multiple systems sending the same NetBIOS name of workstation (assuming they will all break in the same way) may be problematic. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] printing = cups issue ....
Using samba 3.4.9 and cups 1.4.3 I have printing = cups, but for some reason samba is not picking up the cups printers or creating the printers share. The problem is obviously this, from the samba logs: [2011/03/28 14:09:43, 0] printing/print_cups.c:103(cups_connect) Unable to connect to CUPS server localhost:631 - Connection refused However, cupsd is most certainly listening on localhost:631, and an lpstat -a -h localhost gives a list of printers. Why is samba not able to communicate with it? I've turned off all security measures (apparmor, etc.) but still no. Tim Kelley t...@c4tech.com 504-896-8234 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] printing = cups issue ....
Hi Tim, On Tue, 19 Jul 2011 10:16:49 -0500 (CDT) Tim Kelley t...@c4tech.com wrote: ... The problem is obviously this, from the samba logs: [2011/03/28 14:09:43, 0] printing/print_cups.c:103(cups_connect) Unable to connect to CUPS server localhost:631 - Connection refused Please provide full logs with log level = 10 configured in smb.conf. Also, does anything relevant appear in the cups access log? However, cupsd is most certainly listening on localhost:631, and an lpstat -a -h localhost gives a list of printers. Why is samba not able to communicate with it? I've turned off all security measures (apparmor, etc.) but still no. Hmm. In my case lpstat always connects to the local cupsd via the Unix domain socket (e.g. /var/run/cups/cups.sock), even with the -h option specified. Looks like it's due to /etc/cups/client.conf configuration. You may want to check with strace whether yours is doing the same. Cheers, David -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Printing: Request to make return connection to client optional samba 3.5.x
On Thu, Mar 17, 2011 at 10:57:41AM +0100, Urs Beckmann wrote: We have a network of Samba print-stations. There are complains from users of slow printing, which can be tracked to the return-connection which samba-server makes to print-client for dynamic update of printer-status. Since samba-servers are on different subnets than print-clients, the return-connection from samba to windows-client always fails in windows-firewall, but the tries to build up the return-connection lead to delay in printing and sometimes to delays in printer-properties dialog. It's not possible for us to ask clients to open their firewalls, we need a solution on print-server. What helps is to modify samba source as follows: in file rpc_server/srv_spoolss_nt.c: function spoolss_connect_to_client: do nothing but return False; Unfortunately a modified samba-version is not welcome here politically, so if this feature of optionally (configurable in smb.conf) not making the return-connection could be built into next version of samba in the 3.5.x line it would be very helpful. An other issue is the timeout for making a connection from Samba to the Windows DC for print authentication, fixed at 10 seconds, which is sometimes too small. This is in file libsmb/cliconnect.c: cli_set_timeout(cli, 1); /* 10 seconds */ If this timeout could optionally be increased to 30 seconds it would also be very helpful. Does the attached patch help you? I've added patches for 3.5 and master. You should add spoolss backchannel = no to your smb.conf [global] section to disable the backchannel for all printers. Please report if it solves your issue. If you need that in 3.5.next, you should open a bug report at https://bugzilla.samba.org. With best regards, Volker Lendecke -- SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen phone: +49-551-37-0, fax: +49-551-37-9 AG Göttingen, HRB 2816, GF: Dr. Johannes Loxen -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Printing: Request to make return connection to client optional samba 3.5.x
On Fri, Mar 18, 2011 at 04:19:58PM +0100, Volker Lendecke wrote: On Thu, Mar 17, 2011 at 10:57:41AM +0100, Urs Beckmann wrote: We have a network of Samba print-stations. There are complains from users of slow printing, which can be tracked to the return-connection which samba-server makes to print-client for dynamic update of printer-status. Since samba-servers are on different subnets than print-clients, the return-connection from samba to windows-client always fails in windows-firewall, but the tries to build up the return-connection lead to delay in printing and sometimes to delays in printer-properties dialog. It's not possible for us to ask clients to open their firewalls, we need a solution on print-server. What helps is to modify samba source as follows: in file rpc_server/srv_spoolss_nt.c: function spoolss_connect_to_client: do nothing but return False; Unfortunately a modified samba-version is not welcome here politically, so if this feature of optionally (configurable in smb.conf) not making the return-connection could be built into next version of samba in the 3.5.x line it would be very helpful. An other issue is the timeout for making a connection from Samba to the Windows DC for print authentication, fixed at 10 seconds, which is sometimes too small. This is in file libsmb/cliconnect.c: cli_set_timeout(cli, 1); /* 10 seconds */ If this timeout could optionally be increased to 30 seconds it would also be very helpful. Does the attached patch help you? I've added patches for 3.5 and master. You should add spoolss backchannel = no to your smb.conf [global] section to disable the backchannel for all printers. Please report if it solves your issue. If you need that in 3.5.next, you should open a bug report at https://bugzilla.samba.org. Missing attachment :-). Can you add it to v3-6-test and master. I really think we need this one :-). I'll open the bug report for 3.5.next once you've resent the attachment. Thanks ! Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Printing: Request to make return connection to client optional samba 3.5.x
On Fri, Mar 18, 2011 at 10:12:59AM -0700, Jeremy Allison wrote:
Missing attachment :-). Can you add it to v3-6-test and
master. I really think we need this one :-).
The mailing list ate it. Here they are inline.
Volker
From 810d7e464dfaa575b1a6ac49531caa40719da795 Mon Sep 17 00:00:00 2001
From: Volker Lendecke v...@samba.org
Date: Fri, 18 Mar 2011 16:12:42 +0100
Subject: [PATCH] s3: Add spoolss backchannel parameter
---
.../smbdotconf/printing/spoolssbackchannel.xml | 16
source3/include/proto.h|1 +
source3/param/loadparm.c | 12
source3/rpc_server/srv_spoolss_nt.c|6 ++
4 files changed, 35 insertions(+), 0 deletions(-)
create mode 100644 docs-xml/smbdotconf/printing/spoolssbackchannel.xml
diff --git a/docs-xml/smbdotconf/printing/spoolssbackchannel.xml
b/docs-xml/smbdotconf/printing/spoolssbackchannel.xml
new file mode 100644
index 000..dc168fe
--- /dev/null
+++ b/docs-xml/smbdotconf/printing/spoolssbackchannel.xml
@@ -0,0 +1,16 @@
+samba:parameter name=spoolss backchannel
+ context=S
+print=1
+type=boolean
+ xmlns:samba=http://www.samba.org/samba/DTD/samba-doc;
+synonymprint ok/synonym
+description
+ paraWindows print clients often demand that the server opens
+connections back to them. Due to firewall settings this can cause
+considerable timeouts. By setting this parameter to
+constantno/constant the Samba print server will not even try
+to connect to clients and treat corresponding requests as if the
+connection back to the client failed.
+/description
+value type=defaultyes/value
+/samba:parameter
diff --git a/source3/include/proto.h b/source3/include/proto.h
index ef80b92..3b0f28b 100644
--- a/source3/include/proto.h
+++ b/source3/include/proto.h
@@ -4186,6 +4186,7 @@ bool lp_guest_ok(int );
bool lp_guest_only(int );
bool lp_administrative_share(int );
bool lp_print_ok(int );
+bool lp_spoolss_backchannel(int );
bool lp_map_hidden(int );
bool lp_map_archive(int );
bool lp_store_dos_attributes(int );
diff --git a/source3/param/loadparm.c b/source3/param/loadparm.c
index 76e2303..d88327e 100644
--- a/source3/param/loadparm.c
+++ b/source3/param/loadparm.c
@@ -450,6 +450,7 @@ struct service {
bool bAdministrative_share;
bool bGuest_ok;
bool bPrint_ok;
+ bool bSpoolssBackchannel;
bool bMap_system;
bool bMap_hidden;
bool bMap_archive;
@@ -594,6 +595,7 @@ static struct service sDefault = {
False, /* bAdministrative_share */
False, /* bGuest_ok */
False, /* bPrint_ok */
+ True, /* bSpoolssBackchannel */
False, /* bMap_system */
False, /* bMap_hidden */
True, /* bMap_archive */
@@ -2642,6 +2644,15 @@ static struct parm_struct parm_table[] = {
.flags = FLAG_HIDE,
},
{
+ .label = spoolss backchannel,
+ .type = P_BOOL,
+ .p_class= P_LOCAL,
+ .ptr= sDefault.bSpoolssBackchannel,
+ .special= NULL,
+ .enum_list = NULL,
+ .flags = FLAG_ADVANCED,
+ },
+ {
.label = printing,
.type = P_ENUM,
.p_class= P_LOCAL,
@@ -5665,6 +5676,7 @@ FN_LOCAL_BOOL(lp_guest_ok, bGuest_ok)
FN_LOCAL_BOOL(lp_guest_only, bGuest_only)
FN_LOCAL_BOOL(lp_administrative_share, bAdministrative_share)
FN_LOCAL_BOOL(lp_print_ok, bPrint_ok)
+FN_LOCAL_BOOL(lp_spoolss_backchannel, bSpoolssBackchannel)
FN_LOCAL_BOOL(lp_map_hidden, bMap_hidden)
FN_LOCAL_BOOL(lp_map_archive, bMap_archive)
FN_LOCAL_BOOL(lp_store_dos_attributes, bStoreDosAttributes)
diff --git a/source3/rpc_server/srv_spoolss_nt.c
b/source3/rpc_server/srv_spoolss_nt.c
index afc27fe..5fb00d0 100644
--- a/source3/rpc_server/srv_spoolss_nt.c
+++ b/source3/rpc_server/srv_spoolss_nt.c
@@ -2617,6 +2617,12 @@ WERROR
_spoolss_RemoteFindFirstPrinterChangeNotifyEx(pipes_struct *p,
return WERR_SERVER_UNAVAILABLE;
}
+ if (!lp_spoolss_backchannel(snum)) {
+ DEBUG(10, (_spoolss_RemoteFindFirstPrinterChangeNotifyEx:
+ backchannel disabled\n));
+ return WERR_SERVER_UNAVAILABLE;
+ }
+
if (!interpret_string_addr(client_ss, p-client_address,
AI_NUMERICHOST)) {
return WERR_SERVER_UNAVAILABLE;
--
1.7.0.4
From 34e68e7a378f3bd89eea836aefef5477b518d5ee Mon Sep 17 00:00:00 2001
From: Volker Lendecke v...@samba.org
Date: Fri, 18 Mar 2011 16:12:42 +0100
Subject: [PATCH] s3: Add spoolss
Re: [Samba] Printing: Request to make return connection to client optional samba 3.5.x
On Fri, Mar 18, 2011 at 06:18:35PM +0100, Volker Lendecke wrote: On Fri, Mar 18, 2011 at 10:12:59AM -0700, Jeremy Allison wrote: Missing attachment :-). Can you add it to v3-6-test and master. I really think we need this one :-). The mailing list ate it. Here they are inline. Thanks. I'm going to push it but rename the parameter to print notify backchannel as that way it is known to be associated with printing and should be easier to find for administrators. Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Printing: Request to make return connection to client optional samba 3.5.x
Hi We have a network of Samba print-stations. There are complains from users of slow printing, which can be tracked to the return-connection which samba-server makes to print-client for dynamic update of printer-status. Since samba-servers are on different subnets than print-clients, the return-connection from samba to windows-client always fails in windows-firewall, but the tries to build up the return-connection lead to delay in printing and sometimes to delays in printer-properties dialog. It's not possible for us to ask clients to open their firewalls, we need a solution on print-server. What helps is to modify samba source as follows: in file rpc_server/srv_spoolss_nt.c: function spoolss_connect_to_client: do nothing but return False; Unfortunately a modified samba-version is not welcome here politically, so if this feature of optionally (configurable in smb.conf) not making the return-connection could be built into next version of samba in the 3.5.x line it would be very helpful. An other issue is the timeout for making a connection from Samba to the Windows DC for print authentication, fixed at 10 seconds, which is sometimes too small. This is in file libsmb/cliconnect.c: cli_set_timeout(cli, 1); /* 10 seconds */ If this timeout could optionally be increased to 30 seconds it would also be very helpful. Thank you Urs Beckmann ETH Zürich, Informatikdienste, VPP RZE25, Clausiusstr. 59, 8092 Zürich Tel 044 632 34 88, urs.beckm...@id.ethz.ch -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Printing trouble with Windows XP clients; Windows 7 and Mac client work fine
I'm trying to switch our network from IP-based printing (directly to the printers) to using Samba printing via our existing server, both for Point-and-Print functionality and to be able to log print usage. I've followed the directions in the HOWTO and also the policy information in the WIKI (at http://wiki.samba.org/index.php/Implementing_System_Policies_with_Samba) to remove point-and-print restrictions. I've loaded the drivers on the server, apparently with success, via a Windows XP machine's Server Properties box (while logged in as a user with admin privileges on the domain). The drivers show up on the server and are automatically downloaded when I attempt to connect to a printer, whether on XP or Windows 7. (I may have tested a non-domain Vista machine, not sure, but definitely have tested several non-domain Windows 7 machines). Printing works fine from Windows 7 and Mac clients (although the latter are obviously not doing Point and Print). Printing does not work from XP clients, whether domain members or not. I have tried bumping the log level on a per-machine basis on one Windows 7 box and one Windows XP box, and the only difference that looks out of place is the Windows XP box apparently looking for shell32.dll on the server and not finding it. I can post the log files somewhere, but I'm not sure if there's something in particular (beyond an error condition) that I should be looking for—I've tried both log level 3 and log level 20, so I have a ton of information currently logging. I can see the printer drivers being found, printer settings being seen, etc. On the client, I've been trying the Print a test page button from the printer dialog box. The error I get is The test page failed to print. Would you like to view the print troubleshooter for assistance? Nothing useful (or even apparently related) appears in the System or Application logs on the client. Kevin T. Broderick IT Communications Coordinator KILLINGTON MOUNTAIN SCHOOL E: kbroder...@killingtonmountainschool.org P: 802-422-5671 F: 802-422-5678 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] samba printing from 64-bit windows server 2008
Problem solved - or at least, workaround found - so I'm posting it to the list for the benefit of future archive-divers. Bug report at: https://bugzilla.samba.org/show_bug.cgi?id=7506 Basically, the problem is with changes Microsoft made between 2003 and 2008 for Terminal Server - a machine which does not have the Terminal Server role will not have this problem. A Server 2008 Terminal Server host attempting to add a samba-maintained printer (with samba 3.5.3 or below, at least) will fail to connect to the printer and return the error code 0x06d1. Workaround is as follows: 1) On the Windows Server 2008 TS host, bring up the Server Manager. 2) Under Features, install Group Policy Management if it isn't installed already. 3) Under Group Policy Management, drill down til you find the policy which is applying to your machine. 4) Right click the Group Policy Object and select edit. 5) In the resulting editor window, drill down to Computer Configuration:Policies:Administrative Templates:Printers 6) Find the setting Always render print jobs on the server and disable it. 7) reboot the machine. Yes, I know; Microsofts documentation says that leaving this policy not configured is the same as disabling it. They lie. - rob. On 06/08/2010 11:43 AM, Rob Moser wrote: Some additional information on this problem: I set up wireshark to do a packet trace of the connection attempt. I'm not familiar enough with what the traffic should look like to know whats unusual, but the one thing that jumped out at me towards the end of the conversation was a SPOOLSS OpenPrinterEx request on the network printer, followed by a response with the return code of 5 - Access denied. Aha! I say to myself, must be a permissions problem... but a packet trace of the successful connection from the XP box shows several similar Access denied messages. Maybe its irrelevant, but it seemed worth mentioning. I also upped the debug level on smbd and captured a more detailed log. The Printer handle not found message is still the most relevant-looking thing there; the details around it look like: [2010/06/08 11:35:36, 3] smbd/ipc.c:handle_trans(442) trans \PIPE\ data=44 params=0 setup=2 [2010/06/08 11:35:36, 3] smbd/ipc.c:named_pipe(393) named pipe command on name [2010/06/08 11:35:36, 4] rpc_server/srv_pipe_hnd.c:get_rpc_pipe(1231) search for pipe pnum=71df [2010/06/08 11:35:36, 3] smbd/ipc.c:api_fd_reply(351) Got API command 0x26 on pipe spoolss (pnum 71df) [2010/06/08 11:35:36, 3] rpc_server/srv_pipe_hnd.c:free_pipe_context(500) free_pipe_context: destroying talloc pool of size 0 [2010/06/08 11:35:36, 4] rpc_server/srv_pipe.c:api_rpcTNP(2352) api_rpcTNP: spoolss op 0x1d - api_rpcTNP: rpc command: SPOOLSS_CLOSEPRINTER [2010/06/08 11:35:36, 4] rpc_server/srv_lsa_hnd.c:find_policy_by_hnd_internal(179) Policy not found: [000] 00 00 00 00 18 00 00 00 00 00 00 00 0E 4C 78 8D .Lx. [010] 28 24 00 00 ($.. [2010/06/08 11:35:36, 2] rpc_server/srv_spoolss_nt.c:find_printer_index_by_hnd(273) find_printer_index_by_hnd: Printer handle not found: Policy not found: [000] 00 00 00 00 18 00 00 00 00 00 00 00 0E 4C 78 8D \ .Lx. [010] 28 24 00 00 ($.. [2010/06/08 11:35:36, 2] rpc_server/srv_spoolss_nt.c:find_printer_index_by_hnd(273) find_printer_index_by_hnd: Printer handle not found: close_printer_handle: Invalid handle (OURS:9256:9256) [2010/06/08 11:35:36, 4] rpc_server/srv_pipe.c:api_rpcTNP(2387) api_rpcTNP: bad handle fault return. (I don't want to post a full log or the full packet trace - way too much for a mailing list. If no one recognises the problem from this much then I'll attach full data to a bug report.) Thanks for any suggestions, - rob. On 06/07/2010 03:51 PM, Rob Moser wrote: I have a redhat EL5 samba server hosting a collection of printers and joined to a domain. I can connect to this server and print happily from a 32-bit XP box on the domain, but a 64-bit windows server 2008 box cannot connect, and returns the error 0x06d1. I get the same results with samba 3.0.33 (came with redhat), 3.5.3 (the latest from sernet), and 3.3.12 (this message from the samba-technical archives - http://lists.samba.org/archive/samba-technical/2010-February/069145.html - mentions that at least as of February there were issues with 3.4.x+ and 64-bit OS'.) /var/log/samba/log.smb from the time around the failed connection contains: [2010/06/07 14:45:24, 2] lib/access.c:check_access(406) Allowed connection from :::134.114.138.126 (:::134.114.138.126) [Repeated many times] [2010/06/07 14:45:24, 2] rpc_server/srv_spoolss_nt.c:find_printer_index_by_hnd(273) find_printer_index_by_hnd: Printer handle not found: find_printer_index_by_hnd: Printer handle not found: close_printer_handle: Invalid handle (OURS:29459:29459)
Re: [Samba] samba printing from 64-bit windows server 2008
Some additional information on this problem: I set up wireshark to do a packet trace of the connection attempt. I'm not familiar enough with what the traffic should look like to know whats unusual, but the one thing that jumped out at me towards the end of the conversation was a SPOOLSS OpenPrinterEx request on the network printer, followed by a response with the return code of 5 - Access denied. Aha! I say to myself, must be a permissions problem... but a packet trace of the successful connection from the XP box shows several similar Access denied messages. Maybe its irrelevant, but it seemed worth mentioning. I also upped the debug level on smbd and captured a more detailed log. The Printer handle not found message is still the most relevant-looking thing there; the details around it look like: [2010/06/08 11:35:36, 3] smbd/ipc.c:handle_trans(442) trans \PIPE\ data=44 params=0 setup=2 [2010/06/08 11:35:36, 3] smbd/ipc.c:named_pipe(393) named pipe command on name [2010/06/08 11:35:36, 4] rpc_server/srv_pipe_hnd.c:get_rpc_pipe(1231) search for pipe pnum=71df [2010/06/08 11:35:36, 3] smbd/ipc.c:api_fd_reply(351) Got API command 0x26 on pipe spoolss (pnum 71df) [2010/06/08 11:35:36, 3] rpc_server/srv_pipe_hnd.c:free_pipe_context(500) free_pipe_context: destroying talloc pool of size 0 [2010/06/08 11:35:36, 4] rpc_server/srv_pipe.c:api_rpcTNP(2352) api_rpcTNP: spoolss op 0x1d - api_rpcTNP: rpc command: SPOOLSS_CLOSEPRINTER [2010/06/08 11:35:36, 4] rpc_server/srv_lsa_hnd.c:find_policy_by_hnd_internal(179) Policy not found: [000] 00 00 00 00 18 00 00 00 00 00 00 00 0E 4C 78 8D .Lx. [010] 28 24 00 00 ($.. [2010/06/08 11:35:36, 2] rpc_server/srv_spoolss_nt.c:find_printer_index_by_hnd(273) find_printer_index_by_hnd: Printer handle not found: Policy not found: [000] 00 00 00 00 18 00 00 00 00 00 00 00 0E 4C 78 8D \ .Lx. [010] 28 24 00 00 ($.. [2010/06/08 11:35:36, 2] rpc_server/srv_spoolss_nt.c:find_printer_index_by_hnd(273) find_printer_index_by_hnd: Printer handle not found: close_printer_handle: Invalid handle (OURS:9256:9256) [2010/06/08 11:35:36, 4] rpc_server/srv_pipe.c:api_rpcTNP(2387) api_rpcTNP: bad handle fault return. (I don't want to post a full log or the full packet trace - way too much for a mailing list. If no one recognises the problem from this much then I'll attach full data to a bug report.) Thanks for any suggestions, - rob. On 06/07/2010 03:51 PM, Rob Moser wrote: I have a redhat EL5 samba server hosting a collection of printers and joined to a domain. I can connect to this server and print happily from a 32-bit XP box on the domain, but a 64-bit windows server 2008 box cannot connect, and returns the error 0x06d1. I get the same results with samba 3.0.33 (came with redhat), 3.5.3 (the latest from sernet), and 3.3.12 (this message from the samba-technical archives - http://lists.samba.org/archive/samba-technical/2010-February/069145.html - mentions that at least as of February there were issues with 3.4.x+ and 64-bit OS'.) /var/log/samba/log.smb from the time around the failed connection contains: [2010/06/07 14:45:24, 2] lib/access.c:check_access(406) Allowed connection from :::134.114.138.126 (:::134.114.138.126) [Repeated many times] [2010/06/07 14:45:24, 2] rpc_server/srv_spoolss_nt.c:find_printer_index_by_hnd(273) find_printer_index_by_hnd: Printer handle not found: find_printer_index_by_hnd: Printer handle not found: close_printer_handle: Invalid handle (OURS:29459:29459) From the 2008 machine, I can browse the samba server in wexplorer and see the printers, but trying to set up a networked printer generates the error above. Any suggestions? Thanks, - rob. # testparm Load smb config files from /etc/samba/smb.conf Unknown parameter encountered: idmap domains Ignoring unknown parameter idmap domains Processing section [printers] Processing section [print$] Processing section [drivers$] Loaded services file OK. Server role: ROLE_DOMAIN_MEMBER Press enter to see a dump of your service definitions [global] workgroup = NAU-STUDENTS realm = STUDENTS.FROOT.NAU.EDU netbios aliases = dev-acadprtsrv2.ucc.nau.edu server string = Samba Server security = ADS log level = 2 max log size = 50 socket options = TCP_NODELAY IPTOS_LOWDELAY SO_SNDBUF=8192 SO_RCVBUF=8192 SO_KEEPALIVE printcap name = cups wins server = 134.114.138.35 idmap alloc backend = tdb idmap uid = 1 - 400 idmap gid = 1 - 400 winbind use default domain = Yes idmap alloc config:range = 1 - 400 idmap config FROOT:range = 301 - 400 idmap config FROOT:backend = tdb idmap config FROOT:default = no idmap config
[Samba] samba printing from 64-bit windows server 2008
I have a redhat EL5 samba server hosting a collection of printers and joined to a domain. I can connect to this server and print happily from a 32-bit XP box on the domain, but a 64-bit windows server 2008 box cannot connect, and returns the error 0x06d1. I get the same results with samba 3.0.33 (came with redhat), 3.5.3 (the latest from sernet), and 3.3.12 (this message from the samba-technical archives - http://lists.samba.org/archive/samba-technical/2010-February/069145.html - mentions that at least as of February there were issues with 3.4.x+ and 64-bit OS'.) /var/log/samba/log.smb from the time around the failed connection contains: [2010/06/07 14:45:24, 2] lib/access.c:check_access(406) Allowed connection from :::134.114.138.126 (:::134.114.138.126) [Repeated many times] [2010/06/07 14:45:24, 2] rpc_server/srv_spoolss_nt.c:find_printer_index_by_hnd(273) find_printer_index_by_hnd: Printer handle not found: find_printer_index_by_hnd: Printer handle not found: close_printer_handle: Invalid handle (OURS:29459:29459) From the 2008 machine, I can browse the samba server in wexplorer and see the printers, but trying to set up a networked printer generates the error above. Any suggestions? Thanks, - rob. # testparm Load smb config files from /etc/samba/smb.conf Unknown parameter encountered: idmap domains Ignoring unknown parameter idmap domains Processing section [printers] Processing section [print$] Processing section [drivers$] Loaded services file OK. Server role: ROLE_DOMAIN_MEMBER Press enter to see a dump of your service definitions [global] workgroup = NAU-STUDENTS realm = STUDENTS.FROOT.NAU.EDU netbios aliases = dev-acadprtsrv2.ucc.nau.edu server string = Samba Server security = ADS log level = 2 max log size = 50 socket options = TCP_NODELAY IPTOS_LOWDELAY SO_SNDBUF=8192 SO_RCVBUF=8192 SO_KEEPALIVE printcap name = cups wins server = 134.114.138.35 idmap alloc backend = tdb idmap uid = 1 - 400 idmap gid = 1 - 400 winbind use default domain = Yes idmap alloc config:range = 1 - 400 idmap config FROOT:range = 301 - 400 idmap config FROOT:backend = tdb idmap config FROOT:default = no idmap config NAU:range = 201 - 300 idmap config NAU:backend = tdb idmap config NAU:default = no idmap config NAU-STUDENTS:range = 1 - 200 idmap config NAU-STUDENTS:backend = tdb idmap config NAU-STUDENTS:default = yes hosts allow = 127., 134.114., 10.5. [printers] comment = All Printers path = /var/spool/samba printable = Yes default devmode = No browseable = No [print$] path = /var/lib/samba/drivers write list = @NAU-STUDENTS\Domain Admins, @domain admins force user = root force group = domain admins force create mode = 0664 force directory mode = 0774 browseable = No [drivers$] path = /usr/local/printbilling/drivers/ write list = @NAU-STUDENTS\Domain Admins, @domain admins force user = root force group = domain admins force create mode = 0664 force directory mode = 0774 browseable = No -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba Printing to a Windows 7 x64 workstation
The version of samba you're running would help. And perhaps turn up the loglevel on your samba client and see if any errors are logged. DrewTech wrote: I am printing from a older samba build to a Windows 7 x64 PC and the print job would start printing then recycle and start over again. There is no set page where it would stop, sometimes it will stop at page 5, 7, 25. TY Please advice -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Samba Printing to a Windows 7 x64 workstation
I am printing from a older samba build to a Windows 7 x64 PC and the print job would start printing then recycle and start over again. There is no set page where it would stop, sometimes it will stop at page 5, 7, 25. TY Please advice -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Printing w/ 64bit clients
Greetings, Just noticed latest rev for samba (v3.5.2). Is this ok to use with printing for 64bit clients or do you still recommend sticking with the latest v3.3? thanks, Ryan -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Printing Slow-down with Samba 3.5.1
Hu John, On Wed, Mar 31, 2010 at 02:27:54PM -0400, John Welch wrote: We have a Windows 2003 Active Directory environment with a mixture of Windows 2000/2003 and Linux (CentOS 4/5) / Samba servers. The Samba versions on some of the Linux machines are getting a little old (3.0 and 3.2) and we are starting to introduce Windows 7 in our environment, so I thought now might be a good time to upgrade. On a fully patched CentOS 5 test machine I upgraded to Samba 3.5.1 using the packages from the sernet repos. For the most part things seem OK, except that I've noticed a great deal of latency when trying to print (CUPS) to a printer shared on the test Samba 3.5.1 machine. Any type of task involving this printer (viewing properties, selecting the printer, actually printing a document) takes at least a few seconds longer than it used to. In investigating this problem I didn't really see anything relevant in the Samba logs, but for each printing task I do I see messages like the following repeated several times in the CUPS logs: I [31/Mar/2010:12:38:12 -0400] cupsdCloseClient: SSL shutdown successful! I'm guessing this might have something to do with the new Samba cups encrypt parameter. However, the default is supposed to be no, so I'm not sure why I'm seeing these SSL messages. I even tried explicitly setting the parameter to no in my smb.conf file, but this had no effect. All the printing tasks do eventually work (or at least from what I've found so far), but the extra time involved to complete the tasks is an annoyance. Backing off to 3.4 series (3.4.7) fixes the problem, so it definitely seems to be a 3.5 thing. I have no problem upgrading to 3.4.x instead of the 3.5 series, at least for now. But just wondering if I've maybe missed a configuration change that needs to be made either to Samba or CUPS to fix this issue. Any help would be appreciated. this might be related to bug https://bugzilla.samba.org/show_bug.cgi?id=6727 (will be fixed in Samba 3.5.2.). Cheers, Karolin -- Samba http://www.samba.org SerNet http://www.sernet.de sambaXP http://www.sambaxp.org pgpGSnYG8r1rH.pgp Description: PGP signature -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Printing Slow-down with Samba 3.5.1
- Karolin Seeger ksee...@samba.org wrote: Hu John, On Wed, Mar 31, 2010 at 02:27:54PM -0400, John Welch wrote: We have a Windows 2003 Active Directory environment with a mixture of Windows 2000/2003 and Linux (CentOS 4/5) / Samba servers. The Samba versions on some of the Linux machines are getting a little old (3.0 and 3.2) and we are starting to introduce Windows 7 in our environment, so I thought now might be a good time to upgrade. On a fully patched CentOS 5 test machine I upgraded to Samba 3.5.1 using the packages from the sernet repos. For the most part things seem OK, except that I've noticed a great deal of latency when trying to print (CUPS) to a printer shared on the test Samba 3.5.1 machine. Any type of task involving this printer (viewing properties, selecting the printer, actually printing a document) takes at least a few seconds longer than it used to. In investigating this problem I didn't really see anything relevant in the Samba logs, but for each printing task I do I see messages like the following repeated several times in the CUPS logs: I [31/Mar/2010:12:38:12 -0400] cupsdCloseClient: SSL shutdown successful! I'm guessing this might have something to do with the new Samba cups encrypt parameter. However, the default is supposed to be no, so I'm not sure why I'm seeing these SSL messages. I even tried explicitly setting the parameter to no in my smb.conf file, but this had no effect. All the printing tasks do eventually work (or at least from what I've found so far), but the extra time involved to complete the tasks is an annoyance. Backing off to 3.4 series (3.4.7) fixes the problem, so it definitely seems to be a 3.5 thing. I have no problem upgrading to 3.4.x instead of the 3.5 series, at least for now. But just wondering if I've maybe missed a configuration change that needs to be made either to Samba or CUPS to fix this issue. Any help would be appreciated. this might be related to bug https://bugzilla.samba.org/show_bug.cgi?id=6727 (will be fixed in Samba 3.5.2.). Cheers, Karolin Hi Karolin, Thanks for pointing me to the direction of this bug. However, unless I'm reading things wrong I'm not sure this bug applies to my situation. It seems to indicate that this bug exists in the 3.4.x series, and at least in my test environment 3.4.7 seems fine. It is only 3.5.1 where I am seeing the problem. Also, this bug talks mostly about issues going into the Properties for a printer, while my slow down happens whenever I do anything with the printer (properties page, select printer from drop-down, actually printing a document, etc.). Thanks again, John -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Printing Slow-down with Samba 3.5.1
Hello all, We have a Windows 2003 Active Directory environment with a mixture of Windows 2000/2003 and Linux (CentOS 4/5) / Samba servers. The Samba versions on some of the Linux machines are getting a little old (3.0 and 3.2) and we are starting to introduce Windows 7 in our environment, so I thought now might be a good time to upgrade. On a fully patched CentOS 5 test machine I upgraded to Samba 3.5.1 using the packages from the sernet repos. For the most part things seem OK, except that I've noticed a great deal of latency when trying to print (CUPS) to a printer shared on the test Samba 3.5.1 machine. Any type of task involving this printer (viewing properties, selecting the printer, actually printing a document) takes at least a few seconds longer than it used to. In investigating this problem I didn't really see anything relevant in the Samba logs, but for each printing task I do I see messages like the following repeated several times in the CUPS logs: I [31/Mar/2010:12:38:12 -0400] cupsdCloseClient: SSL shutdown successful! I'm guessing this might have something to do with the new Samba cups encrypt parameter. However, the default is supposed to be no, so I'm not sure why I'm seeing these SSL messages. I even tried explicitly setting the parameter to no in my smb.conf file, but this had no effect. All the printing tasks do eventually work (or at least from what I've found so far), but the extra time involved to complete the tasks is an annoyance. Backing off to 3.4 series (3.4.7) fixes the problem, so it definitely seems to be a 3.5 thing. I have no problem upgrading to 3.4.x instead of the 3.5 series, at least for now. But just wondering if I've maybe missed a configuration change that needs to be made either to Samba or CUPS to fix this issue. Any help would be appreciated. Thanks, John -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Clustered Samba Printing
Hi Bill, I am using clustered samba printing for a couple of years and it works fine, this is my setup: 3 sun server with sun cluster, let's call them samba1 samba2 and samba3 are individually joined to the windows domain using the hostnames samba1/2/3. Through the sun cluster they use together a shared address called 'printserver' with the 'bind interface only' option set to the shared hostname I have a loadbalanced samba setup for printing. To make sure all server use the same config I have 'ntforms.tdb', 'printers.tdb' and 'ntdrivers.tdb' on a shared global storage, linked via symlink into the three local samba/var/locks dirs. The 'samba printcap' is shared globally as well as the 'drivers' dir of cause. One thing about this construction is that samba1/2/3 still and always publish the printers over ther local ip adress though they will not accept a connection over these adresses. You need a firewall to get rid of this or unconfigure those printer in the AD. For some reason I have a cron restart running every morning, this is nice to get rid of old processes and connections and to have a fresh start from the ground for all three nodes... Hope this helps, don't hesitate to write me e-mail if you have further questions, well and maybe I got it all wrong and there is a much more clever idea about clustered printing, love to hear something about it then ;) cheers christoph On Mon, 15 Mar 2010, Bill Morris wrote: Hi Folks, I'm part of a Novell department that is working on moving from Novell NDPS printing to Samba printing. I have been told that the Samba environment will have to be clustered to assure the same level of redundancy for printing. Does anyone have any pointers? Whether actual experience in this or a location of good documentation of the clustering process? Thanks for any assistance, Bill Morris Bill Morris (bill_mor...@ncsu.edu) Systems Hosted Systems North Carolina State University -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba 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: https://lists.samba.org/mailman/options/samba
Re: [Samba] Clustered Samba Printing
Hi Bill, I am using clustered samba printing for a couple of years and it works fine, this is my setup: 3 sun server with sun cluster, let's call them samba1 samba2 and samba3 are individually joined to the windows domain using the hostnames samba1/2/3. Through the sun cluster they use together a shared address called 'printserver' with the 'bind interface only' option set to the shared hostname I have a loadbalanced samba setup for printing. To make sure all server use the same config I have 'ntforms.tdb', 'printers.tdb' and 'ntdrivers.tdb' on a shared global storage, linked via symlink into the three local samba/var/locks dirs. The 'samba printcap' is shared globally as well as the 'drivers' dir of cause. One thing about this construction is that samba1/2/3 still and always publish the printers over ther local ip adress though they will not accept a connection over these adresses. You need a firewall to get rid of this or unconfigure those printer in the AD. For some reason I have a cron restart running every morning, this is nice to get rid of old processes and connections and to have a fresh start from the ground for all three nodes... Hope this helps, don't hesitate to write me e-mail if you have further questions, well and maybe I got it all wrong and there is a much more clever idea about clustered printing, love to hear something about it then ;) cheers christoph On Mon, 15 Mar 2010, Bill Morris wrote: Hi Folks, I'm part of a Novell department that is working on moving from Novell NDPS printing to Samba printing. I have been told that the Samba environment will have to be clustered to assure the same level of redundancy for printing. Does anyone have any pointers? Whether actual experience in this or a location of good documentation of the clustering process? Thanks for any assistance, Bill Morris Bill Morris (bill_mor...@ncsu.edu) Systems Hosted Systems North Carolina State University -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba 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: https://lists.samba.org/mailman/options/samba
[Samba] Clustered Samba Printing
Hi Folks, I'm part of a Novell department that is working on moving from Novell NDPS printing to Samba printing. I have been told that the Samba environment will have to be clustered to assure the same level of redundancy for printing. Does anyone have any pointers? Whether actual experience in this or a location of good documentation of the clustering process? Thanks for any assistance, Bill Morris Bill Morris (bill_mor...@ncsu.edu) Systems Hosted Systems North Carolina State University -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Printing queues not clearing after server crash
We had a server crash last night and now the print queues (from the Windows clients) are not clearing after the job prints. I'm using Samba version 3.0.26a-0.9-1787-SUSE-SLES9 and CUPS cups-1.1.20-108.44. I'm thinking I've got a corrupt tdb file but not sure which one(s) to check. Advice / suggestions? Bob Dehn This communication and any attachments are confidential, protected by Communications Privacy Act 18 USCS § 2510, solely for the use of the intended recipient, and may contain legally privileged material. If you are not the intended recipient, please return or destroy it immediately. Thank you. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Printing from Vista/W2K8 with 3.4 Print Server
I have a Samba 3.4.0 print server with WinXP, Win2K3, Vista, and Win2K8 clients. The print server functions fine with WinXP and Win2K3. The drivers show up properly and if you look in server properties from those clients you can see the Samba printer port, the drivers, and print forms. However under Vista and Win2K8 server I get nothing. The clients say that the drivers aren't installed, and when I go to look at the server properties on either client everything is blank. There is no Samba print port, no print forms, and the installed drivers show up as a couple characters of gobbelty-gook. I haven't been able to discern any errors when looking at the log files. Anyone have some insight? Help is much appreciated. Neil -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Printing:(Samba + CUPS + LDAP) Windows Clients(2000/XP) Slow get status printer.
Hello! Help please 1)i have: CentOS 5.2 final Samba 3.0.28-0.e15.8 Cups 1.2.4-11.18.el5 90 printers connected to cups by lpd/lpr and samba shared with installed windows drivers using rpcclient. 2)problem When windows clients press CTRL+P from any aplication (windows notepad, Word), window appears which shows list of printers, connected to client from my samba server. After i click on the printer an about 10 seconds long delay occurs. And then printing ok. But 10 second - too long. But if user belongs to group (Domain admins in this case) which specified as admin users in smb.conf (admin users = '@Domain Admins'), delay does not occurs! (1-2 seconds). Logs indicates no errors. Samba using LDAP which installed on remote host. 3)smb.conf, cupsd.conf, ldap.conf ==smb.conf= [global] log file = /var/log/samba.log.%m log level = 0 domain logons = no domain master = no local master = no preferred master = no wins support = no dns proxy = no os level = 0 # server setup --- wins server = 10.1.1.203 netbios name = testsrv workgroup = SOMETHING security = user admin users = @Domain Admins passdb backend = ldapsam:ldap://10.1.2.203 ldap admin dn = uid=radius,ou=GK,ou=Users,dc=something ldap group suffix = ou=NTGroups ldap idmap suffix = ou=Idmap ldap machine suffix = ou=Computers ldap suffix = dc=someting ldap user suffix = ou=Users idmap gid = 100-2000 idmap uid = 100-2000 client ntlmv2 auth = Yes # print setup --- cups server = localhost:631 load printers = yes printing = cups printcap = cups # printcap cache time = 60 # lpq cache time = 0 use client driver = no [printers] comment = All Printers path = /var/spool/samba readonly = no browseable = no guest ok = yes writable = no printable = yes [print$] comment = Printer Driver Download Area path = /etc/samba/drivers browseable = yes guest ok = yes read only = yes [drivers] readonly = yes guest ok = yes path = /mnt/test/ ==cupsd.conf= cupsd.conf LogLevel error SystemGroup sys root # Allow remote access Port 631 # Disable printer sharing and shared printers. Listen testsrv:631 #Listen /var/run/cups/cups.sock Browsing Off DefaultAuthType Basic Location / Allow all # Allow remote administration... Order allow,deny Allow @LOCAL /Location Location /admin Require user @SYSTEM Encryption Required # Allow remote administration... Order allow,deny Allow @LOCAL /Location Location /admin/conf AuthType Basic Require user @SYSTEM # Allow remote access to the configuration files... Order allow,deny Allow @LOCAL /Location Policy default Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job Purge-Jobs Set-Job-Attributes Create-Job-Subscription Renew-Subscription Cancel-Subscription Get-Notifications Reprocess-Job Cancel-Current-Job Suspend-Current-Job Resume-Job CUPS-Move-Job Order allow,deny Allow all /Limit Limit CUPS-Add-Modify-Printer CUPS-Delete-Printer CUPS-Add-Modify-Class CUPS-Delete-Class CUPS-Set-Default AuthType Basic Require user @SYSTEM Order deny,allow /Limit Limit Pause-Printer Resume-Printer Enable-Printer Disable-Printer Pause-Printer-After-Current-Job Hold-New-Jobs Release-Held-New-Jobs Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer Startup-Printer Promote-Job Schedule-Job-After CUPS-Accept-Jobs CUPS-Reject-Jobs AuthType Basic Order deny,allow /Limit Limit CUPS-Authenticate-Job Require user @OWNER @SYSTEM Order deny,allow /Limit Limit All Order deny,allow /Limit Limit Cancel-Job Order deny,allow Require user @OWNER @SYSTEM /Limit /Policy ldap.conf uri ldap://10.1.2.203 basedc=something bind_policy soft idle_timelimit 3700 pam_lookup_policy yes pam_passwordexop nss_initgroups_ignoreusers root,ldap nss_schema rfc2307bis nss_map_attribute uniqueMember member ssl start_tls ldap_version2 pam_filter objectclass=posixaccount nss_base_passwd ou=Users,dc=something nss_base_shadow ou=Users,dc=something nss_base_group ou=NTGroups,dc=something tls_checkpeer no -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Printing:(Samba + CUPS + LDAP) Windows Clients(2000/XP) Slow get status printer.
on log level = 3 shows next errors: [2009/03/29 21:19:53, 3] rpc_server/srv_spoolss_nt.c:_spoolss_setprinterdata(8164) _spoolss_setprinterdata: change denied by handle access permissions [2009/03/29 21:19:52, 3] rpc_server/srv_spoolss_nt.c:_spoolss_open_printer_ex(1675) access DENIED for printer open I can understand samba then user have a Insufficient access and samba doesn't work. but i can't understand issue then work slow? -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Printing from Windows with Kyocera Drivers - which one to use ?
Hello I just ordered a new Kyocera FS-1030 - no more inkjets - and am currently preparing the clients and the server for the new printer. Installing the PPDs on the server was easy but I am unsure which client driver to use. On the server I am using samba-3.0.9-2.6 and cups-1.1.20-108.31. My current plan is to install a Local Raw Printer in Cups and then let the clients print with the windows printer drivers supplied by Kyocera. Kyocera uses three kinds of drivers, KX, PCL and KPDL. Which one should I use if I plan to print with the setup described ? As a general question I have always wondered if the connection between a client and printer in such a setting is always only unidirectional or if there is a way to get back status messages from the printer back to the client with SAMBA ? Is there a way to enable the clients to delete entries from the printer queue ? Yours sincerely Stefan -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
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 = removed for security 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
[Samba] Printing XP - 3.2 Now really slow (just like the old days)
Guys, My wife needed to print something this evening to our normal HP 4 attached to our cups server running samba-3.2.1-0.1.126. Nothing has changed in the last two months going from 3.0.28a to the 3.2.x flavor of samba. However, something has brought printing to its knees. I pulled out all the old tricks, hacked the registry to delete any entries in HKCU\Printers\DevModes and DevModes2 of the type \\server\printer. Removal of the entries didn't change a thing. I captured an ethereal/wireshark trace and I have that available to anyone if interested. Have there been any changes in 3.2.x that would effect printing? It does seem to print once every conceivable timer in window times out, but were talking 120-150 seconds. Any Ideas? -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Printing XP - 3.2 Now really slow (just like the old days)
David C. Rankin wrote: Guys, Have there been any changes in 3.2.x that would effect printing? It does seem to print once every conceivable timer in window times out, but were talking 120-150 seconds. Any Ideas? Guys, I can confirm, this seems to be an XP only issue. Vista prints just fine to the same server. I have also confirmed the XP behavior on 2 other boxes. In all regards, the behavior is identical, printing basically freezes the application and printer dialog (if open) for about 2.5 minutes until everything in XP times out, then the documents will actually print, but not before you get the grayed boxes and application not responding messages. What can I send you that would help solve this atavistic printing conundrum? Just let me know and I'll be glad to help. Anything so my wife can print. When she needs to print, it seems to be an immediate thing, every time... -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Printing XP - 3.2 Now really slow (just like the old days)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David C. Rankin wrote: David C. Rankin wrote: Guys, Have there been any changes in 3.2.x that would effect printing? It does seem to print once every conceivable timer in window times out, but were talking 120-150 seconds. Any Ideas? Guys, I can confirm, this seems to be an XP only issue. Vista prints just fine to the same server. I have also confirmed the XP behavior on 2 other boxes. In all regards, the behavior is identical, printing basically freezes the application and printer dialog (if open) for about 2.5 minutes until everything in XP times out, then the documents will actually print, but not before you get the grayed boxes and application not responding messages. What can I send you that would help solve this atavistic printing conundrum? Just let me know and I'll be glad to help. Anything so my wife can print. When she needs to print, it seems to be an immediate thing, every time... Standard debug steps would seem to apply here... logging at the time, doing a strace or whatever your OS happens to use (note you did not supply it unless I missed something), etc. - -- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Systems Programmer II |$| |__| | | |__/ | \| _| |[EMAIL PROTECTED] - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent.|IST/AST - NJMS Medical Science Bldg - C630 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIpENNmb+gadEcsb4RAlyGAJ4wunJScMKB0LS7n1TQKnMYbaWk8QCguCSq qeTJsUmYxYBPVFavWyFvL/o= =jUnU -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 XP - 3.2 Now really slow (just like the old days)
On Thu, Aug 14, 2008 at 02:01:26AM -0500, David C. Rankin wrote: Guys, My wife needed to print something this evening to our normal HP 4 attached to our cups server running samba-3.2.1-0.1.126. Nothing has changed in the last two months going from 3.0.28a to the 3.2.x flavor of samba. However, something has brought printing to its knees. I pulled out all the old tricks, hacked the registry to delete any entries in HKCU\Printers\DevModes and DevModes2 of the type \\server\printer. Removal of the entries didn't change a thing. I captured an ethereal/wireshark trace and I have that available to anyone if interested. Have there been any changes in 3.2.x that would effect printing? It does seem to print once every conceivable timer in window times out, but were talking 120-150 seconds. Any Ideas? There's a bug with a missing reply_printclose() that just got fixed in the tree by Bartosz Antosik that may be causing this. It could cause print jobs to timeout on the Windows side. Patch is attached, and it will be in 3.2.2. Jeremy. diff --git a/source/smbd/reply.c b/source/smbd/reply.c index ef49d58..88c8ae8 100644 --- a/source/smbd/reply.c +++ b/source/smbd/reply.c @@ -4672,6 +4672,8 @@ void reply_printclose(struct smb_request *req) return; } + reply_outbuf(req, 0, 0); + END_PROFILE(SMBsplclose); return; } -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Printing XP - 3.2 Now really slow (just like the old days)
Jeremy Allison wrote: On Thu, Aug 14, 2008 at 02:01:26AM -0500, David C. Rankin wrote: Guys, My wife needed to print something this evening to our normal HP 4 attached to our cups server running samba-3.2.1-0.1.126. Nothing has changed in the last two months going from 3.0.28a to the 3.2.x flavor of samba. However, something has brought printing to its knees. I pulled out all the old tricks, hacked the registry to delete any entries in HKCU\Printers\DevModes and DevModes2 of the type \\server\printer. Removal of the entries didn't change a thing. I captured an ethereal/wireshark trace and I have that available to anyone if interested. Have there been any changes in 3.2.x that would effect printing? It does seem to print once every conceivable timer in window times out, but were talking 120-150 seconds. Any Ideas? There's a bug with a missing reply_printclose() that just got fixed in the tree by Bartosz Antosik that may be causing this. It could cause print jobs to timeout on the Windows side. Patch is attached, and it will be in 3.2.2. Jeremy. Patch installed and verified -- IT IS FIXED!! Printing again works like a charm from XP. Now all we have to do is wait for the updated rpms from Lars and we can get off of the /usr/local/samba binaries ;-) I don't know how Lars does it. I could not get anything to build from the samba.spec-10.3. The samba-vscan link doesn't work for Source11: So I just applied the patch, compiled and used the default local install. I had no problems with new binaries at all. For anyone else wanting to test building from source on openSuSE, after the build and install to /usr/local/samba, you can use the following command lines to start nmbd and smbd to make use of the remainder of your standard rpm configuration and also keep your normal log files separate: /usr/local/samba/sbin/nmbd --daemon --configfile=/etc/samba/smb.conf --log-basename=log.nmb.test /usr/local/samba/sbin/smbd --daemon --configfile=/etc/samba/smb.conf --log-basename log.smb.test --smb-passwd-file=/etc/samba/smbpasswd --private-dir=/etc/samba -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] samba printing with cups driver and cups with non PS printers
Hello, I just finished to read chapter 22 of the samba howto. This chapter explains very well how printing from a win client via samba and cups work. If I understood it right, printing a file from windows to a non postscript printer via cups driver, samba an cups works like this: - application prints generating an EMF file ( windows spooler ) - the cups ( or adobe ) printer driver converts this file to postscript and sends it to samba that passes the file to cups - cups takes the ps file and creates a raster ( bitmap ) - cups converts this raster data to the file printed ( PCL or ESC/P ) IMHO there are steps here that could be avoided. EMF files are no more than a series of calls to windows GDI funtions. This GDI function create a DIB ( device independent bitmap ) Wouldn't it be more efficient to let windows convert the EMF file to a DIB and convert this direct to a cups raster and send this to cups ? The two conversion from EMF to PS and from PS to raster could be replaced by one. Also possible conversion problems between emf and ps could be avoided. This printer driver could continue to use the PPD system for configuration. The mime type for cups rasters is also registered at IANA. http://www.iana.org/assignments/media-types/application/vnd.cups-raster. Bye Andreas -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Printing problem
Hi, I ran into a strange printing-problem: We're using OpenBSD 4.2 and Samba Version 3.0.28 and include our printers directly from /etc/printcap; whenever I enter a printername that contains numbers, smbd gives me the errors below. Any idea why samba messes up with digits in printernames? /var/log/log.smbd (with smbd started in debuglevel 10) [2008/05/19 17:07:59, 3] /usr/ports/net/samba/w-samba-3.0.28/samba-3.0.28/source/printing/pcap.c:pcap_cache_reload(117) reloading printcap cache [2008/05/19 17:07:59, 3] /usr/ports/net/samba/w-samba-3.0.28/samba-3.0.28/source/printing/pcap.c:pcap_cache_reload(223) reload status: ok [2008/05/19 17:07:59, 7] /usr/ports/net/samba/w-samba-3.0.28/samba-3.0.28/source/param/loadparm.c:lp_servicenumber(5200) lp_servicenumber: couldn't find mfgZO01 [2008/05/19 17:07:59, 8] /usr/ports/net/samba/w-samba-3.0.28/samba-3.0.28/source/param/loadparm.c:add_a_service(2574) add_a_service: Creating snum = 12 for mfgZO01 [2008/05/19 17:07:59, 10] /usr/ports/net/samba/w-samba-3.0.28/samba-3.0.28/source/param/loadparm.c:hash_a_service(2621) hash_a_service: hashing index 12 for service name mfgZO01 [2008/05/19 17:07:59, 3] /usr/ports/net/samba/w-samba-3.0.28/samba-3.0.28/source/param/loadparm.c:lp_add_printer(2746) adding printer service mfgZO01 [2008/05/19 17:07:59, 7] /usr/ports/net/samba/w-samba-3.0.28/samba-3.0.28/source/param/loadparm.c:lp_servicenumber(5200) lp_servicenumber: couldn't find prnZO01 [2008/05/19 17:07:59, 8] /usr/ports/net/samba/w-samba-3.0.28/samba-3.0.28/source/param/loadparm.c:add_a_service(2574) add_a_service: Creating snum = 13 for prnZO01 [2008/05/19 17:07:59, 10] /usr/ports/net/samba/w-samba-3.0.28/samba-3.0.28/source/param/loadparm.c:hash_a_service(2621) hash_a_service: hashing index 13 for service name prnZO01 [2008/05/19 17:07:59, 3] /usr/ports/net/samba/w-samba-3.0.28/samba-3.0.28/source/param/loadparm.c:lp_add_printer(2746) adding printer service prnZO01 -- -- using the following /etc/printcap file (ip removed for privacy reasons): -- # $OpenBSD: printcap,v 1.4 2003/03/28 21:32:30 jmc Exp $ #lp|local line printer:\ # :lp=/dev/lp:sd=/var/spool/output:lf=/var/log/lpd-errs: #rp|remote line printer:\ # :lp=:rm=printhost:rp=lp:sd=/var/spool/output:lf=/var/log/lpd-errs: prnZO01|prnZO01:\ :lp=:rm=(printerIp1):rp=lp:sd=/var/spool/printer/prnZO01:sh:lf=/var/log/lpd-errs: mfgZO01|mfgZO01:\ :lp=:rm=(printerIp2):rp=lp:sd=/var/spool/printer/mfgZO01:sh:lf=/var/log/lpd-errs: If i change the printcap file into the following, i dont get the problem any more: --- # $OpenBSD: printcap,v 1.4 2003/03/28 21:32:30 jmc Exp $ #lp|local line printer:\ # :lp=/dev/lp:sd=/var/spool/output:lf=/var/log/lpd-errs: #rp|remote line printer:\ # :lp=:rm=printhost:rp=lp:sd=/var/spool/output:lf=/var/log/lpd-errs: prnZO|prnZO:\ :lp=:rm=(printerIp1):rp=lp:sd=/var/spool/printer/prnZO01:sh:lf=/var/log/lpd-errs: mfgZO|mfgZO:\ :lp=:rm=(printerIp2):rp=lp:sd=/var/spool/printer/mfgZO01:sh:lf=/var/log/lpd-errs: -- Heres our smb.conf: -- [global] workgroup = ### netbios name = ### server string = Samba Server security = domain log file = /var/log/samba/smbd.%m ;log level = 5 max log size = 50 ;passdb backend = tdbsam socket options = TCP_NODELAY interfaces = # wins support = no wins server = # os level = 65 map system = yes map archive = yes map hidden = yes create mask = 0771 directory mask = 0771 csc policy = disable enable privileges = Yes printing = bsd load printers = yes show add printer wizard = yes printcap name = /etc/printcap # printer admin = @domadmins printcap cache time = 15 lpq cache time = 30 default devmode = yes [printers] comment = SMB Print Spool path = /var/spool/samba/spool browseable = No guest ok = Yes public = Yes writable = No printable = Yes [print$] default devmode = yes comment = Printer Drivers path = /usr/local/share/printer_drivers
RE: [Samba] Printing Problem with Samba ' Failed to allocate a print job'
FYI, rebooting did not fix this problem either. If anybody has any suggestions I would appreciate it. I'm almost at the point of renaming the printer to see if that helps (it shouldn't but who knows). Misty -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Misty Stanley-Jones Sent: Tuesday, April 08, 2008 4:53 PM To: samba@lists.samba.org Subject: RE: [Samba] Printing Problem with Samba ' Failed to allocate a print job' Hi Bill, That would be fabulous (in a bad way) but it is not the case. Here is the equivalent part of dumpe2fs for /dev/sda1 (/data): Inode count: 183156736 Block count: 366286008 Reserved block count: 18314300 Free blocks: 287497221 Free inodes: 181068686 And here is for /dev/sdf1 (/): Inode count: 14057472 Block count: 28103701 Reserved block count: 1405185 Free blocks: 17311944 Free inodes: 13849218 Any other ideas would be appreciated! --Misty -Original Message- From: William Jojo [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 08, 2008 1:49 PM To: Misty Stanley-Jones Subject: Re: [Samba] Printing Problem with Samba ' Failed to allocate a print job' This will sound stupid, I am certain, but is this an inode issue? Does the FS type you are using auto-extend (like JFS2 on AIX) the number of available inodes? Or fragmentation perhaps? I only ask since you clearly have enough space, but a lack of inode may appear as no space left on device and a high level of fragmentation in JFS (not jfs2) on AIX will throw strange errors. Cheers, Bill (PS: I know you are not running AIX. :-) :-) ) No virus found in this outgoing message. Checked by AVG. Version: 7.5.519 / Virus Database: 269.22.9/1365 - Release Date: 4/8/2008 7:30 AM -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba No virus found in this incoming message. Checked by AVG. Version: 7.5.519 / Virus Database: 269.22.9/1365 - Release Date: 4/8/2008 7:30 AM No virus found in this outgoing message. Checked by AVG. Version: 7.5.519 / Virus Database: 269.22.9/1365 - Release Date: 4/8/2008 7:30 AM -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Printing Problem with Samba ' Failed to allocate a print job'
I’m using Samba 3.0.24 on Ubuntu Feisty. I’m managing my printers with CUPS. Just yesterday, one printer stopped being able to print through Samba. This printer still prints fine directly from CUPS. When I try to send any print job to the print via Samba, I get this: [2008/04/08 11:15:58, 0] printing/printing.c:allocate_print_jobid(2262) allocate_print_jobid: failed to allocate a print job for queue truss_hp4050_2 [2008/04/08 11:15:58, 3] printing/printing.c:print_job_start(2431) print_job_start: returning fail. Error = No space left on device At first glance, I would think the disk was full. It’s actually not: [EMAIL PROTECTED]:~# df -h FilesystemSize Used Avail Use% Mounted on /dev/sdf1 106G 41G 60G 41% / varrun 1006M 844K 1005M 1% /var/run varlock 1006M 4.0K 1006M 1% /var/lock procbususb 1006M 140K 1006M 1% /proc/bus/usb udev 1006M 140K 1006M 1% /dev devshm 1006M 0 1006M 0% /dev/shm /dev/sda1 1.4T 293G 1014G 23% /data /dev/md0 1.2T 770G 380G 67% /backup /data/home1.4T 293G 1014G 23% /home Then I checked to make sure the permissions on the spool directory were OK: [EMAIL PROTECTED]:~# ls -ld /data/samba/spool drwxrwxrwt 3 root Domain Users 49152 2008-04-08 11:17 /data/samba/spool I don’t use /var/spool/samba but here are its permissions anyway: [EMAIL PROTECTED]:~# ls -ld /var/spool/samba drwxrwxrwt 2 root root 4096 2007-05-22 13:53 /var/spool/samba Thinking it might just be a temporary thing with Samba, I restarted it last night after everyone left. The problem still persists. I have not restarted the entire server yet. There are no errors in dmesg or /var/log/messages. I checked this morning to see if there was a newer Samba version for Feisty, but there isn’t. I found a few instances of this type of problem on Google, but no real answers. Plus, they all seemed to be old. Thanks for any help, Misty No virus found in this outgoing message. Checked by AVG. Version: 7.5.519 / Virus Database: 269.22.9/1365 - Release Date: 4/8/2008 7:30 AM -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Printing Problem with Samba ' Failed to allocate a print job'
Hi Bill, That would be fabulous (in a bad way) but it is not the case. Here is the equivalent part of dumpe2fs for /dev/sda1 (/data): Inode count: 183156736 Block count: 366286008 Reserved block count: 18314300 Free blocks: 287497221 Free inodes: 181068686 And here is for /dev/sdf1 (/): Inode count: 14057472 Block count: 28103701 Reserved block count: 1405185 Free blocks: 17311944 Free inodes: 13849218 Any other ideas would be appreciated! --Misty -Original Message- From: William Jojo [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 08, 2008 1:49 PM To: Misty Stanley-Jones Subject: Re: [Samba] Printing Problem with Samba ' Failed to allocate a print job' This will sound stupid, I am certain, but is this an inode issue? Does the FS type you are using auto-extend (like JFS2 on AIX) the number of available inodes? Or fragmentation perhaps? I only ask since you clearly have enough space, but a lack of inode may appear as no space left on device and a high level of fragmentation in JFS (not jfs2) on AIX will throw strange errors. Cheers, Bill (PS: I know you are not running AIX. :-) :-) ) No virus found in this outgoing message. Checked by AVG. Version: 7.5.519 / Virus Database: 269.22.9/1365 - Release Date: 4/8/2008 7:30 AM -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Samba printing via CUPS fails
Hi Having switched my Samba server from a Solaris box to a RHEL3 Linux box I cannot get printing to work. Linux box is using CUPS to reference various network available printers. Printer drivers have been made available from the Samba server itself under print$. The Samba version is 3.0.9-1.3E.13.2 (the default with RHEL3) and CUPS is 1.1.17-13.3.43 (again the RHEL3 default) [print$] comment = Printer Driver Download Area path = /etc/samba/drivers admin users = root, lansley, blansle write list = root, lansley, blansle read only = No create mask = 0644 guest ok = Yes [printers] comment = All printers path = /var/samba/spool guest ok = Yes printable = Yes browseable = No Printers are configured on Win XP clients using rundll32,PrintUIEntry /in /n \\sambaserver\printername Printers all show up as available and ready but test page print results in a Access is denied message. Accessing homes shares from the same Samba server work fine so user authentication does appear to be working. I've verified that the path in print$ and printers is valid and accessible. Any clues? Cheers, Bob -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Printing failure through PDC
Volker Lendecke wrote: On Sat, Mar 22, 2008 at 04:12:26PM -0400, Rich West wrote: I recently went through a system upgrade, which resulted in an upgrade of Samba to 3.0.28a. This is for a home network, so it isn't heavily taxed (only by family members), but I do use the environment as a sandbox of sorts for stuff that I plan to roll in to production in the office. Can you recompile Samba with -g and run it under valgrind? The logfile of the segfault would be very helpful. Hrmm.. I'll have to work on that, then. :( I'm running off of the standard RPM... -Rich -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Printing failure through PDC
Rich West wrote: I recently went through a system upgrade, which resulted in an upgrade of Samba to 3.0.28a. This is for a home network, so it isn't heavily taxed (only by family members), but I do use the environment as a sandbox of sorts for stuff that I plan to roll in to production in the office. I had some funky issues with authentication to start with after the upgrade, so I went through the (somewhat) painful steps to set up ldapsam. I managed to get all of the users set up within LDAP, and all of the machine accounts configured within LDAP, and logging in and out of the domain with roaming profiles (using samba to create the machine accounts and user accounts turned out to be the right way to do it rather than to hand modify the LDAP accounts). The only remaining issue is with regard to printing: When a Windows user connects to the printer (hppsc2510) and sends a test page, they get an error stating that the job failed to print (unable to create print job). In the log.system name file, I can see: [..snip...] -- At this point, I'm truly unsure of what is failing. I've made sure that /var/spool/samba exists and is world writeable. I tried moving it out of the way and testing, and samba gave an appropriate error in the log file. I tried shutting down CUPS and doing the same test, and samba gave an appropriate error then, too. I can print via the command line on the samba server (a Fedora 8 box) as the same user who is logged in on the windows box... Any ideas? -Rich Actually, I made some headway.. I found that we had an old setting for disable spoolss = yes in place. Removing that allowed things to get a tiny bit forward. I'm not seeing much logged, but I am getting Test page failed to print ... Access is denied. from the windows side. The Windows box successfully gets the driver as supplied by the samba server, so I know that part is working. I'm just not sure what the Access is denied. is referring to... -Rich -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Printing failure through PDC
On Sat, Mar 22, 2008 at 04:12:26PM -0400, Rich West wrote: I recently went through a system upgrade, which resulted in an upgrade of Samba to 3.0.28a. This is for a home network, so it isn't heavily taxed (only by family members), but I do use the environment as a sandbox of sorts for stuff that I plan to roll in to production in the office. Can you recompile Samba with -g and run it under valgrind? The logfile of the segfault would be very helpful. Thanks, Volker pgpXkr2hIyErV.pgp Description: 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 failure through PDC
I recently went through a system upgrade, which resulted in an upgrade of Samba to 3.0.28a. This is for a home network, so it isn't heavily taxed (only by family members), but I do use the environment as a sandbox of sorts for stuff that I plan to roll in to production in the office. I had some funky issues with authentication to start with after the upgrade, so I went through the (somewhat) painful steps to set up ldapsam. I managed to get all of the users set up within LDAP, and all of the machine accounts configured within LDAP, and logging in and out of the domain with roaming profiles (using samba to create the machine accounts and user accounts turned out to be the right way to do it rather than to hand modify the LDAP accounts). The only remaining issue is with regard to printing: When a Windows user connects to the printer (hppsc2510) and sends a test page, they get an error stating that the job failed to print (unable to create print job). In the log.system name file, I can see: [2008/03/22 15:03:04, 1] smbd/service.c:make_connection_snum(1033) cortex (192.168.56.5) connect to service windows_user initially as user windows_user (uid=17361, gid=17362) (pid 26541) [2008/03/22 16:04:06, 1] smbd/service.c:make_connection_snum(1033) cortex (192.168.56.5) connect to service hppsc2510 initially as user windows_user (uid=17361, gid=17362) (pid 29537) [2008/03/22 16:04:06, 0] lib/fault.c:fault_report(41) === [2008/03/22 16:04:06, 0] lib/fault.c:fault_report(42) INTERNAL ERROR: Signal 11 in pid 29537 (3.0.28a-0.fc8) Please read the Trouble-Shooting section of the Samba3-HOWTO [2008/03/22 16:04:06, 0] lib/fault.c:fault_report(44) From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf [2008/03/22 16:04:06, 0] lib/fault.c:fault_report(45) === [2008/03/22 16:04:06, 0] lib/util.c:smb_panic(1655) PANIC (pid 29537): internal error [2008/03/22 16:04:06, 0] lib/util.c:log_stack_trace(1759) BACKTRACE: 10 stack frames: #0 smbd(log_stack_trace+0x1c) [0x2accf59c] #1 smbd(smb_panic+0x43) [0x2accf683] #2 smbd [0x2acbd040] #3 /lib64/libpthread.so.0 [0x2c42f540] #4 smbd(reply_printopen+0x7e) [0x2ab480de] #5 smbd [0x2ab81274] #6 smbd(smbd_process+0x7b1) [0x2ab82211] #7 smbd(main+0xa20) [0x2ad84260] #8 /lib64/libc.so.6(__libc_start_main+0xf4) [0x2d968074] #9 smbd [0x2ab13479] [2008/03/22 16:04:06, 0] lib/fault.c:dump_core(181) dumping core in /var/log/samba/cores/smbd [2008/03/22 16:04:06, 1] smbd/service.c:make_connection_snum(1033) cortex (192.168.56.5) connect to service hppsc2510 initially as user windows_user (uid=17361, gid=17362) (pid 29540) [2008/03/22 16:04:06, 0] lib/fault.c:fault_report(41) === [2008/03/22 16:04:06, 0] lib/fault.c:fault_report(42) INTERNAL ERROR: Signal 11 in pid 29540 (3.0.28a-0.fc8) Please read the Trouble-Shooting section of the Samba3-HOWTO [2008/03/22 16:04:06, 0] lib/fault.c:fault_report(44) From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf [2008/03/22 16:04:06, 0] lib/fault.c:fault_report(45) === [2008/03/22 16:04:06, 0] lib/util.c:smb_panic(1655) PANIC (pid 29540): internal error [2008/03/22 16:04:06, 0] lib/util.c:log_stack_trace(1759) BACKTRACE: 10 stack frames: #0 smbd(log_stack_trace+0x1c) [0x2accf59c] #1 smbd(smb_panic+0x43) [0x2accf683] #2 smbd [0x2acbd040] #3 /lib64/libpthread.so.0 [0x2c42f540] #4 smbd(reply_printopen+0x7e) [0x2ab480de] #5 smbd [0x2ab81274] #6 smbd(smbd_process+0x7b1) [0x2ab82211] #7 smbd(main+0xa20) [0x2ad84260] #8 /lib64/libc.so.6(__libc_start_main+0xf4) [0x2d968074] #9 smbd [0x2ab13479] [2008/03/22 16:04:06, 0] lib/fault.c:dump_core(181) dumping core in /var/log/samba/cores/smbd --- Unfortunately, it doesn't actually place anything in /var/log/samba/cores/smbd. At least, it hasn't in the past couple of days. I turned up the debugging to 9 and went through the same test of printing a test page, and I got: [2008/03/22 14:43:25, 6] smbd/process.c:process_smb(1067) got message type 0x0 of len 0x23 [2008/03/22 14:43:25, 3] smbd/process.c:process_smb(1068) Transaction 20 of length 39 [2008/03/22 14:43:25, 5] lib/util.c:show_msg(506) [2008/03/22 14:43:25, 5] lib/util.c:show_msg(516) size=35 smb_com=0x71 smb_rcls=0 smb_reh=0 smb_err=0 smb_flg=24 smb_flg2=51207 smb_tid=1 smb_pid=65279 smb_uid=101 smb_mid=64832 smt_wct=0 smb_bcc=0 [2008/03/22 14:43:25, 3] smbd/process.c:switch_message(926) switch message SMBtdis (pid 25593) conn 0x2aeaa4b0 [2008/03/22 14:43:25, 3] smbd/sec_ctx.c:set_sec_ctx(241) setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0 [2008/03/22 14:43:25, 5] auth/auth_util.c:debug_nt_user_token(448) NT user token: (NULL) [2008/03/22
Re: [Samba] Printing samba, cups and legacy 16 bit applications
ridiculously simple, what confounded me was that vb3 was able to print to macromedia flash paper, several other network printers shared under windows xp and win98 and pdf printers. maybe something special with the PS driver. many tks Ciro On Fri, Feb 29, 2008 at 12:17 PM, Jim Shanks [EMAIL PROTECTED] wrote: hello everybody, I have come to a dead end. I have successfully configured cups and samba to print from windows with automated drivers download. It works perfectly, but for one little problem, most of the printing here in my company are reports printed by the ERP software, which has been developed by ouserlves some 12 years ago in (oohh sucks) Visual basic 3. The problem is: Every single application prints successfully except apps developed in Vb3. I have developed a wonderful test app with amazing 3 lines of code. event form load cmdialog1.action=5 'opens windows common dialog for choosing printer printer.print time 'prints time in the upper left corner of the page printer.enddoc 'finishes print job end the same app built with vb6 prints ok, built with vb3 does not print, and what's worse, does not generate any kind of error, the job simply disapears. worse than that. if i check the print to file option of the ps driver, save the file with whatever name, copy it to my cups/samba server and print it with lpr, it prints, either from vb3 or vb6. i believe the problem is with the 8.3 filename restriction of vb3 and the smbprn.XX filename of samba spool directory although i`m not certain of who really creates this file, the app, the windows driver or samba itself. i have pcap files of the network from the moment i click the ok button in the printing dialog, But i could not make any sense out of them. if someone could be of any help! tks a lot Ciro Souza Ciro, It's been quite a while since I had to do this, but if I remember right, with Windows 2000 and Windows XP clients running most 16 bit applications, you'll have to capture a local LPT port to your network printer in order to get the application to print. Run the following at the DOS prompt at the client workstation: net use LPT2: \\servername\shared-printer-name Then from the 16-bit application, print to LPT2 Jim -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Printing samba, cups and legacy 16 bit applications
hello everybody, I have come to a dead end. I have successfully configured cups and samba to print from windows with automated drivers download. It works perfectly, but for one little problem, most of the printing here in my company are reports printed by the ERP software, which has been developed by ouserlves some 12 years ago in (oohh sucks) Visual basic 3. The problem is: Every single application prints successfully except apps developed in Vb3. I have developed a wonderful test app with amazing 3 lines of code. event form load cmdialog1.action=5 'opens windows common dialog for choosing printer printer.print time 'prints time in the upper left corner of the page printer.enddoc 'finishes print job end the same app built with vb6 prints ok, built with vb3 does not print, and what's worse, does not generate any kind of error, the job simply disapears. worse than that. if i check the print to file option of the ps driver, save the file with whatever name, copy it to my cups/samba server and print it with lpr, it prints, either from vb3 or vb6. i believe the problem is with the 8.3 filename restriction of vb3 and the smbprn.XX filename of samba spool directory although i`m not certain of who really creates this file, the app, the windows driver or samba itself. i have pcap files of the network from the moment i click the ok button in the printing dialog, But i could not make any sense out of them. if someone could be of any help! tks a lot Ciro Souza Ciro, It's been quite a while since I had to do this, but if I remember right, with Windows 2000 and Windows XP clients running most 16 bit applications, you'll have to capture a local LPT port to your network printer in order to get the application to print. Run the following at the DOS prompt at the client workstation: net use LPT2: \\servername\shared-printer-name Then from the 16-bit application, print to LPT2 Jim -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Printing samba, cups and legacy 16 bit applications
hello everybody, I have come to a dead end. I have successfully configured cups and samba to print from windows with automated drivers download. It works perfectly, but for one little problem, most of the printing here in my company are reports printed by the ERP software, which has been developed by ouserlves some 12 years ago in (oohh sucks) Visual basic 3. The problem is: Every single application prints successfully except apps developed in Vb3. I have developed a wonderful test app with amazing 3 lines of code. event form load cmdialog1.action=5 'opens windows common dialog for choosing printer printer.print time 'prints time in the upper left corner of the page printer.enddoc 'finishes print job end the same app built with vb6 prints ok, built with vb3 does not print, and what's worse, does not generate any kind of error, the job simply disapears. worse than that. if i check the print to file option of the ps driver, save the file with whatever name, copy it to my cups/samba server and print it with lpr, it prints, either from vb3 or vb6. i believe the problem is with the 8.3 filename restriction of vb3 and the smbprn.XX filename of samba spool directory although i`m not certain of who really creates this file, the app, the windows driver or samba itself. i have pcap files of the network from the moment i click the ok button in the printing dialog, But i could not make any sense out of them. if someone could be of any help! tks a lot Ciro Souza -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Printing; privileges separation (follow up: printing/nt_printing.c)
Roel van Meer writes: I'm using samba 3.0.26a with cups as printing backend, which are both working fine. However, I would like to grant all users access to all print jobs, but without granting them the right to add or modify printers and printer settings. When I grant users the SePrintOperatorPrivilege privilege, they can indeed cancel other people's jobs, but then they can also rename printers on the server (which breaks things). Does anyone know if it is possible to separate access to these two operations, or to grant normal users the right to remove other people's jobs without them having the SePrintOperatorPrivilege priv? I received a very helpful suggestion from Dale Schroeder on this. He said it was possible to grant users or groups the 'Manage Documents' privilege from a Windows client. However, when I do this, users are still not allowed to cancel other users' print jobs. Some debugging of the samba code showed that the request is denied in print_access_check() in printing/nt_printing.c. The code I see there does something I do not understand. When canceling a job you need JOB_ACCESS_ADMINISTER privileges, but the code modifies this to check for PRINTER_ACCESS_ADMINISTER privs. The comments preceding this statement are: /* Now this is the bit that really confuses me. The access type needs to be changed from JOB_ACCESS_ADMINISTER to PRINTER_ACCESS_ADMINISTER for this to work. Something to do with the child (job) object becoming like a printer?? -tpot */ When I comment the line changing the access_type (line 5514), canceling print jobs works as expected. Does anyone know why I would need PRINTER_ACCESS_ADMINISTER instead of JOB_ACCESS_ADMINISTER? Does changing it introduce security problems? I can file a bug report if necessary. Regards, roel -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Printing; privileges separation
Hi list, I'm using samba 3.0.26a with cups as printing backend, which are both working fine. However, I would like to grant all users access to all print jobs, but without granting them the right to add or modify printers and printer settings. When I grant users the SePrintOperatorPrivilege privilege, they can indeed cancel other people's jobs, but then they can also rename printers on the server (which breaks things). Does anyone know if it is possible to separate access to these two operations, or to grant normal users the right to remove other people's jobs without them having the SePrintOperatorPrivilege priv? Thanks in advance for any input, roel -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Printing multiple copies in Cups
I have a cups setup for printing purpose. The problem I am facing is that it doesn't print more than 1 copy of the same document in single print command. could someone guide me how to fix this problem?. Rajeev R. Veedu -- 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: 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
[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: [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
Re: [Samba] printing from dos works...not from smbclient
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jørgen Kold wrote: Hi We have a newly started server(Sun-Fire-T200) running samba. From one day to another samba printing just stopped working. We have found out following: When forwarding printing to another server through printers.conf it works. When printing from dos through the command: echo ^MHello^L \\servername\printer it also works. When right clicking on the printer choosing Print test print it does not work. When using smbclient to print from the server it also works. Whenever we create a printer with the original name it just dosn't work. ERRNotEnoughDetails (not enough details provided to generate an adequate response) cheers, jerry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGTcH5IR7qMdg1EfYRAjP8AJ470D7h6iKeOKMy0QgOHIQCtItONQCdHV/L 73mrj4njVgwIrR6fnXCSG4Y= =5xzx -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 from dos works...not from smbclient
Hi We have a newly started server(Sun-Fire-T200) running samba. From one day to another samba printing just stopped working. We have found out following: When forwarding printing to another server through printers.conf it works. When printing from dos through the command: echo ^MHello^L \\servername\printer it also works. When right clicking on the printer choosing Print test print it does not work. When using smbclient to print from the server it also works. Whenever we create a printer with the original name it just dosn't work. Any idears? Jorgen -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Printing and file share problems
Hello List, I have a samba PDC (3.0.10-1.4E11) running on centos, and workstations running WinXP, Vista and Win98 under the samba domain. The PDC is also a file and print server; everything was working fine but suddenly this morning all win98 stations stop printing also couldnt access a database in a share. The XP and Vista works fine. I checked the samba logs and found these messages ( a lot of them ) [2007/05/14 17:54:40, 0] tdb/tdbutil.c:tdb_log(725) tdb(/var/cache/samba/printing/xerox.tdb): rec_read bad magic 0x6d732f2f at offset=22048 [2007/05/14 17:54:40, 0] tdb/tdbutil.c:tdb_log(725) tdb(/var/cache/samba/printing/xerox.tdb): rec_read bad magic 0x6d732f2f at offset=22048 [2007/05/14 17:54:49, 1] libsmb/clispnego.c:parse_negTokenTarg(251) Failed to parse negTokenTarg at offset 21 [2007/05/14 17:54:50, 0] tdb/tdbutil.c:tdb_log(725) googled some threats about it but no replies, I will appreciate any help about this issue. I dont know if it is smbd related, maybe it went corrupt. Thanks in advance, --Ivan. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] printing problem
I'm testing a printserver with Samab/ Cups. Every time I want to upload the driver to samba for printing I get the following error: Printer settings could not be saves. Access denied I chmod 777 the driver directory and spool directory. I gave specified the user as printer admin in the share. My firewall is disabled. Why is it still giving me the access denied error? Best Regards, Roland de Lepper -- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] printing problem
Hi Roland I recently had the same horrible nightmare ;) Please do not ask me for any raesons but try the following: Change the permissions of the driver-files on your windows-system. Remove any write protection. Then try to upload again. Good luck! Denis W-SYS, IT- Medienservice Göttingen T: 0551 - 20 19 834 F: 0551 - 37 06 983 W: http://www.w-sys.info [EMAIL PROTECTED] schrieb: I'm testing a printserver with Samab/ Cups. Every time I want to upload the driver to samba for printing I get the following error: Printer settings could not be saves. Access denied I chmod 777 the driver directory and spool directory. I gave specified the user as printer admin in the share. My firewall is disabled. Why is it still giving me the access denied error? Best Regards, Roland de Lepper -- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] printing problem
Hi denis, Thnaks...this worked, but now I have the problem that I cannot connect to the printer. Access denied, unable to connect Best Regards, Roland de Lepper -- Denis Wollenhaupt [EMAIL PROTECTED]To: [EMAIL PROTECTED] cc: 09/03/2007 13:42 Subject: Re: [Samba] printing problem Hi Roland I recently had the same horrible nightmare ;) Please do not ask meabout any raesons but try the following: Change the permissions of the driver-files on your windows-system. Remove any write protection. Then try to upload again. Good luck! Denis W-SYS, IT- Medienservice Göttingen T: 0551 - 20 19 834 F: 0551 - 37 06 983 W: http://www.w-sys.info [EMAIL PROTECTED] schrieb: I'm testing a printserver with Samab/ Cups. Every time I want to upload the driver to samba for printing I get the following error: Printer settings could not be saves. Access denied I chmod 777 the driver directory and spool directory. I gave specified the user as printer admin in the share. My firewall is disabled. Why is it still giving me the access denied error? Best Regards, Roland de Lepper -- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] printing problem
Hi again So I would check ther perms the used directories (eg. tmp-dir /vat/spool/cups/tmp) W-SYS, IT- Medienservice Göttingen T: 0551 - 20 19 834 F: 0551 - 37 06 983 W: http://www.w-sys.info [EMAIL PROTECTED] schrieb: Hi denis, Thnaks...this worked, but now I have the problem that I cannot connect to the printer. Access denied, unable to connect -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] printing problem
Hi Roland I recently had the same horrible nightmare ;) Please do not ask meabout any raesons but try the following: Change the permissions of the driver-files on your windows-system. Remove any write protection. Then try to upload again. Good luck! Denis W-SYS, IT- Medienservice Göttingen T: 0551 - 20 19 834 F: 0551 - 37 06 983 W: http://www.w-sys.info [EMAIL PROTECTED] schrieb: I'm testing a printserver with Samab/ Cups. Every time I want to upload the driver to samba for printing I get the following error: Printer settings could not be saves. Access denied I chmod 777 the driver directory and spool directory. I gave specified the user as printer admin in the share. My firewall is disabled. Why is it still giving me the access denied error? Best Regards, Roland de Lepper -- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] printing problem
[EMAIL PROTECTED] schrieb: I'm testing a printserver with Samab/ Cups. Every time I want to upload the driver to samba for printing I get the following error: Printer settings could not be saves. Access denied I chmod 777 the driver directory and spool directory. I gave specified the user as printer admin in the share. My firewall is disabled. Why is it still giving me the access denied error? Possible reasons: 1) The driver wants to do some initialization which fails. So: which driver? 2) Your might be using and old and buggy samba version. 3) You have no W32X86 directory in your driver directory 4) You printer admin authentication fails for some reason ... The first thing I'll allways suggest is to call Start-Run from your windows menu and enter \\your samba server\print$. Change into the W32X86 directory and try to create a file or folder. If this fails, you have an authentication or unix rights issue. Otherwise you'll have to go further with more details. Regards, Martin -- Martin Zielinski [EMAIL PROTECTED] Software Development SEH Computertechnik GmbH www.seh.de -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] printing problem
sorry, but the driver upload didn't worked either. I thought it worked, but it was the local driver that was installed and not the one on the printserver. This is really a nightmare. Best Regards, Roland de Lepper -- Senior MIS engineer. Lite-On IT BV Meerenakkerplein 16 5652 BJ Eindhoven The Netherlands E-Mail : [EMAIL PROTECTED] Tel : +31-(0)40-2508086 Denis Wollenhaupt [EMAIL PROTECTED]To: [EMAIL PROTECTED] cc: samba@lists.samba.org 09/03/2007 14:03 Subject: Re: [Samba] printing problem Hi again So I would check ther perms the used directories (eg. tmp-dir /vat/spool/cups/tmp) W-SYS, IT- Medienservice Göttingen T: 0551 - 20 19 834 F: 0551 - 37 06 983 W: http://www.w-sys.info [EMAIL PROTECTED] schrieb: Hi denis, Thnaks...this worked, but now I have the problem that I cannot connect to the printer. Access denied, unable to connect -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] printing problem
Hi Martin, 1) driver is a HP laserjet 1300n with a jet directcard 2) samba version = 3.0.20.4 3) I have a W32X86 directory in my driver directory and can add new folders to it 4) sorry...cannot check this. smb.conf [global] workgroup = LITEONIT.COM netbios name = NLHOL1F1 security = domain winbind use default domain = Yes password server = 192.168.0.1 hosts allow = 192.168.0.0/24 127.0.0.0/8 os level = 50 encrypt passwords = Yes idmap uid = 15000-2 idmap gid = 15000-2 wins support = Yes winbind separator = + winbind enum users = Yes winbind enum groups = Yes logfile = /var/log/samba/log.%m socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 printing = cups use client driver = yes load printers = yes printcap name = /etc/printcap printer admin = root LITEONIT.COM+Roland_deLepper max print jobs = 100 lpq cache time = 20 show add printer wizard = yes print command = lpr -r -P %p %s [printers] comment = all printers printable = yes admin users = @domainadmins LITEONIT.COM+Roland_deLepper path = /var/spool/samba guest ok = yes printer admin = LITEONIT.COM+Roland_deLepper show add printer wizard = yes [print$] comment = printer download section path = /etc/samba/drivers browseable = yes guest ok = yes write list = @domainadmins read only = no [lj1300n] comment = HP Laserjet 1300n path = /var/spool/samba/lj1300n printable = yes guest ok = yes writable = yes printer admin = LITEONIT.COM+Roland_deLepper use client driver = yes Best Regards, Roland de Lepper -- Martin Zielinski [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: samba@lists.samba.org 09/03/2007 14:11 Subject: Re: [Samba] printing problem [EMAIL PROTECTED] schrieb: I'm testing a printserver with Samab/ Cups. Every time I want to upload the driver to samba for printing I get the following error: Printer settings could not be saves. Access denied I chmod 777 the driver directory and spool directory. I gave specified the user as printer admin in the share. My firewall is disabled. Why is it still giving me the access denied error? Possible reasons: 1) The driver wants to do some initialization which fails. So: which driver? 2) Your might be using and old and buggy samba version. 3) You have no W32X86 directory in your driver directory 4) You printer admin authentication fails for some reason ... The first thing I'll allways suggest is to call Start-Run from your windows menu and enter \\your samba server\print$. Change into the W32X86 directory and try to create a file or folder. If this fails, you have an authentication or unix rights issue. Otherwise you'll have to go further with more details. Regards, Martin -- Martin Zielinski [EMAIL PROTECTED] Software Development SEH Computertechnik GmbH www.seh.de -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] printing problem
Hi, I put comments inline. [EMAIL PROTECTED] schrieb: Hi Martin, 1) driver is a HP laserjet 1300n with a jet directcard 2) samba version = 3.0.20.4 3) I have a W32X86 directory in my driver directory and can add new folders to it 4) sorry...cannot check this. smb.conf [global] workgroup = LITEONIT.COM netbios name = NLHOL1F1 security = domain winbind use default domain = Yes password server = 192.168.0.1 hosts allow = 192.168.0.0/24 127.0.0.0/8 os level = 50 encrypt passwords = Yes idmap uid = 15000-2 idmap gid = 15000-2 wins support = Yes winbind separator = + winbind enum users = Yes winbind enum groups = Yes logfile = /var/log/samba/log.%m socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 printing = cups use client driver = yes ^ That's exactly what you *don't* want to do. Please remove this line and try again. load printers = yes printcap name = /etc/printcap printer admin = root LITEONIT.COM+Roland_deLepper max print jobs = 100 lpq cache time = 20 show add printer wizard = yes print command = lpr -r -P %p %s [...] [printers] comment = all printers printable = yes admin users = @domainadmins LITEONIT.COM+Roland_deLepper path = /var/spool/samba guest ok = yes printer admin = LITEONIT.COM+Roland_deLepper ^^ This is a global parameter. show add printer wizard = yes [print$] comment = printer download section path = /etc/samba/drivers browseable = yes guest ok = yes write list = @domainadmins ^^ I'm really not shure about this, but you might add LITEONIT.COM+Roland_deLepper here, allthough read only = no ^^^ might make the write list obsolete. [lj1300n] comment = HP Laserjet 1300n path = /var/spool/samba/lj1300n printable = yes guest ok = yes writable = yes printer admin = LITEONIT.COM+Roland_deLepper use client driver = yes ^^^ Please remove. BTW it's a global parameter, too. Best Regards, Roland de Lepper -- [...] Hope that helps. Regards, Martin -- Martin Zielinski [EMAIL PROTECTED] Software Development SEH Computertechnik GmbH www.seh.de -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] printing problem
Hi Martin, thanks...this worked. But...the next problem arise. The driver is uploaded to the server now. This is good. I connected to the prinbter via start-settings-printers and added the printer as available printer from my printserver. This all went ok, but when I want to print, the print doesn't come out en I see the following error message in my logs: ERROR: string overflow by 1 (256 - 255) in safe_strcpy (NT_STATUS_DISK_FULL opening remote spool smbprn_00) I'm admin on the windows box (domain admin) Best Regards, Roland de Lepper -- Martin Zielinski [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: samba@lists.samba.org 09/03/2007 14:52 Subject: Re: [Samba] printing problem Hi, I put comments inline. [EMAIL PROTECTED] schrieb: Hi Martin, 1) driver is a HP laserjet 1300n with a jet directcard 2) samba version = 3.0.20.4 3) I have a W32X86 directory in my driver directory and can add new folders to it 4) sorry...cannot check this. smb.conf [global] workgroup = LITEONIT.COM netbios name = NLHOL1F1 security = domain winbind use default domain = Yes password server = 192.168.0.1 hosts allow = 192.168.0.0/24 127.0.0.0/8 os level = 50 encrypt passwords = Yes idmap uid = 15000-2 idmap gid = 15000-2 wins support = Yes winbind separator = + winbind enum users = Yes winbind enum groups = Yes logfile = /var/log/samba/log.%m socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 printing = cups use client driver = yes ^ That's exactly what you *don't* want to do. Please remove this line and try again. load printers = yes printcap name = /etc/printcap printer admin = root LITEONIT.COM+Roland_deLepper max print jobs = 100 lpq cache time = 20 show add printer wizard = yes print command = lpr -r -P %p %s [...] [printers] comment = all printers printable = yes admin users = @domainadmins LITEONIT.COM+Roland_deLepper path = /var/spool/samba guest ok = yes printer admin = LITEONIT.COM+Roland_deLepper ^^ This is a global parameter. show add printer wizard = yes [print$] comment = printer download section path = /etc/samba/drivers browseable = yes guest ok = yes write list = @domainadmins ^^ I'm really not shure about this, but you might add LITEONIT.COM+Roland_deLepper here, allthough read only = no ^^^ might make the write list obsolete. [lj1300n] comment = HP Laserjet 1300n path = /var/spool/samba/lj1300n printable = yes guest ok = yes writable = yes printer admin = LITEONIT.COM+Roland_deLepper use client driver = yes ^^^ Please remove. BTW it's a global parameter, too. Best Regards, Roland de Lepper -- [...] Hope that helps. Regards, Martin -- Martin Zielinski [EMAIL PROTECTED] Software Development SEH Computertechnik GmbH www.seh.de -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] printing problem
Hi Martin, Denis, Finally it all works. Print came not out because i configured cups wrong. Thanks for your help Best Regards, Roland de Lepper -- [EMAIL PROTECTED] Sent by: To: Martin Zielinski [EMAIL PROTECTED] [EMAIL PROTECTED]cc: samba@lists.samba.org s.samba.org Subject: Re: [Samba] printing problem 09/03/2007 15:35 Hi Martin, thanks...this worked. But...the next problem arise. The driver is uploaded to the server now. This is good. I connected to the prinbter via start-settings-printers and added the printer as available printer from my printserver. This all went ok, but when I want to print, the print doesn't come out en I see the following error message in my logs: ERROR: string overflow by 1 (256 - 255) in safe_strcpy (NT_STATUS_DISK_FULL opening remote spool smbprn_00) I'm admin on the windows box (domain admin) Best Regards, Roland de Lepper -- Martin Zielinski [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: samba@lists.samba.org 09/03/2007 14:52 Subject: Re: [Samba] printing problem Hi, I put comments inline. [EMAIL PROTECTED] schrieb: Hi Martin, 1) driver is a HP laserjet 1300n with a jet directcard 2) samba version = 3.0.20.4 3) I have a W32X86 directory in my driver directory and can add new folders to it 4) sorry...cannot check this. smb.conf [global] workgroup = LITEONIT.COM netbios name = NLHOL1F1 security = domain winbind use default domain = Yes password server = 192.168.0.1 hosts allow = 192.168.0.0/24 127.0.0.0/8 os level = 50 encrypt passwords = Yes idmap uid = 15000-2 idmap gid = 15000-2 wins support = Yes winbind separator = + winbind enum users = Yes winbind enum groups = Yes logfile = /var/log/samba/log.%m socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 printing = cups use client driver = yes ^ That's exactly what you *don't* want to do. Please remove this line and try again. load printers = yes printcap name = /etc/printcap printer admin = root LITEONIT.COM+Roland_deLepper max print jobs = 100 lpq cache time = 20 show add printer wizard = yes print command = lpr -r -P %p %s [...] [printers] comment = all printers printable = yes admin users = @domainadmins LITEONIT.COM+Roland_deLepper path = /var/spool/samba guest ok = yes printer admin = LITEONIT.COM+Roland_deLepper ^^ This is a global parameter. show add printer wizard = yes [print$] comment = printer download section path = /etc/samba/drivers browseable = yes guest ok = yes write list = @domainadmins ^^ I'm really not shure about this, but you might add LITEONIT.COM+Roland_deLepper here, allthough read only = no ^^^ might make the write list obsolete. [lj1300n] comment = HP Laserjet 1300n path = /var/spool/samba/lj1300n printable = yes guest ok = yes writable = yes printer admin = LITEONIT.COM+Roland_deLepper use client driver = yes
Re: [Samba] printing problem
The error message seems to be saying that you have no space left on the spooling disk. This could be true, or you may have a permission problem with the spooling folder on your Linux box. [EMAIL PROTECTED] wrote: Hi Martin, thanks...this worked. But...the next problem arise. The driver is uploaded to the server now. This is good. I connected to the prinbter via start-settings-printers and added the printer as available printer from my printserver. This all went ok, but when I want to print, the print doesn't come out en I see the following error message in my logs: ERROR: string overflow by 1 (256 - 255) in safe_strcpy (NT_STATUS_DISK_FULL opening remote spool smbprn_00) I'm admin on the windows box (domain admin) Best Regards, Roland de Lepper -- Martin Zielinski [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: samba@lists.samba.org 09/03/2007 14:52 Subject: Re: [Samba] printing problem Hi, I put comments inline. [EMAIL PROTECTED] schrieb: Hi Martin, 1) driver is a HP laserjet 1300n with a jet directcard 2) samba version = 3.0.20.4 3) I have a W32X86 directory in my driver directory and can add new folders to it 4) sorry...cannot check this. smb.conf [global] workgroup = LITEONIT.COM netbios name = NLHOL1F1 security = domain winbind use default domain = Yes password server = 192.168.0.1 hosts allow = 192.168.0.0/24 127.0.0.0/8 os level = 50 encrypt passwords = Yes idmap uid = 15000-2 idmap gid = 15000-2 wins support = Yes winbind separator = + winbind enum users = Yes winbind enum groups = Yes logfile = /var/log/samba/log.%m socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 printing = cups use client driver = yes ^ That's exactly what you *don't* want to do. Please remove this line and try again. load printers = yes printcap name = /etc/printcap printer admin = root LITEONIT.COM+Roland_deLepper max print jobs = 100 lpq cache time = 20 show add printer wizard = yes print command = lpr -r -P %p %s [...] [printers] comment = all printers printable = yes admin users = @domainadmins LITEONIT.COM+Roland_deLepper path = /var/spool/samba guest ok = yes printer admin = LITEONIT.COM+Roland_deLepper ^^ This is a global parameter. show add printer wizard = yes [print$] comment = printer download section path = /etc/samba/drivers browseable = yes guest ok = yes write list = @domainadmins ^^ I'm really not shure about this, but you might add LITEONIT.COM+Roland_deLepper here, allthough read only = no ^^^ might make the write list obsolete. [lj1300n] comment = HP Laserjet 1300n path = /var/spool/samba/lj1300n printable = yes guest ok = yes writable = yes printer admin = LITEONIT.COM+Roland_deLepper use client driver = yes ^^^ Please remove. BTW it's a global parameter, too. Best Regards, Roland de Lepper -- [...] Hope that helps. Regards, Martin -- Martin Zielinski [EMAIL PROTECTED] Software Development SEH Computertechnik GmbH www.seh.de -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] printing problem
Hi everybody, when a i have to install a new printer driver i do the following: 1 - install the printer driver on a windows machine 2 - share the printer on windows machine 3 - use smbclient to connect to windows printer share and download the printer files drivers 4 - use rpcclient to connect to windows printer share to see what files are needed to register the printer driver correctly 5 - use rpcclient to register the files of printer driver just this Marcos --- [EMAIL PROTECTED] escreveu: sorry, but the driver upload didn't worked either. I thought it worked, but it was the local driver that was installed and not the one on the printserver. This is really a nightmare. Best Regards, Roland de Lepper -- Senior MIS engineer. Lite-On IT BV Meerenakkerplein 16 5652 BJ Eindhoven The Netherlands E-Mail : [EMAIL PROTECTED] Tel : +31-(0)40-2508086 Denis Wollenhaupt [EMAIL PROTECTED]To: [EMAIL PROTECTED] cc: samba@lists.samba.org 09/03/2007 14:03 Subject: Re: [Samba] printing problem Hi again So I would check ther perms the used directories (eg. tmp-dir /vat/spool/cups/tmp) W-SYS, IT- Medienservice Göttingen T: 0551 - 20 19 834 F: 0551 - 37 06 983 W: http://www.w-sys.info [EMAIL PROTECTED] schrieb: Hi denis, Thnaks...this worked, but now I have the problem that I cannot connect to the printer. Access denied, unable to connect -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba __ Fale com seus amigos de graça com o novo Yahoo! Messenger http://br.messenger.yahoo.com/ -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] printing problem
Hi Dale, i'm using cups 1.2.7-2. thanks Marcos. --- Dale Schroeder [EMAIL PROTECTED] escreveu: Are you using CUPS? If yes, which version? There was such an error in CUPS 1.2.3 or 1.2.4 - I forget which one. Dale x wrote: Hi everybody, i have a debian etch with samba 3.0.23c-4 (it's not the latest version) installed. this server is a member server (print server) of windows 2003 active directory domain - i'm using winbind to provide single sign-on. my problem is that i have a network printer HP Color Laserjet 2600n and it doesn't print using landscape orientation, just with portrait orientation. i'm using point and click to install and update workstation's printer driver - my workstations are win98, win2k and some winxp. thanks Marcos __ Fale com seus amigos de graça com o novo Yahoo! Messenger http://br.messenger.yahoo.com/ __ Fale com seus amigos de graça com o novo Yahoo! Messenger http://br.messenger.yahoo.com/ -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] printing problem
Hi everybody, i have a debian etch with samba 3.0.23c-4 (it's not the latest version) installed. this server is a member server (print server) of windows 2003 active directory domain - i'm using winbind to provide single sign-on. my problem is that i have a network printer HP Color Laserjet 2600n and it doesn't print using landscape orientation, just with portrait orientation. i'm using point and click to install and update workstation's printer driver - my workstations are win98, win2k and some winxp. thanks Marcos __ Fale com seus amigos de graça com o novo Yahoo! Messenger http://br.messenger.yahoo.com/ -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] printing without a spool
Hello all at Samba I'm new to this list. I need to investigate the possibility of configuring a Samba print server without a spool (that's right: without a spool !!!). I know this is really strange, but I really need to get some clear ideas on this. I'm developing a project with very (very) limited disk storage and one of the possibilities we are considering is printing without spool (with all the disadvantages it implies...)... Can anyone shed some light on this matter ? Thank you very much regards Joao -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Samba printing crashes all inet services
Thanks, I checked this and found that I had the most recent glibc update for FC4. I then downloaded the most recent FC4 source samba rpm from fedora and I have recompiled this and installed, but I still have exactly the same core dumping problem. Martin -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 31 December 2006 09:35 To: samba@lists.samba.org Subject: Re: [Samba] Samba printing crashes all inet services Suggest you check to see if there are any glibc updates for your FC4. - John T. On Saturday 30 December 2006 22:54, Martin E. Main wrote: Now upgraded to latest version and instead of crashing the network it core dumps instead with following output:- [2006/12/31 08:49:10, 1] smbd/service.c:make_connection_snum(941) martin (192.168.10.2) connect to service canon_inkjet initially as user mmain (uid=0, gid=500) (pid 5819) [2006/12/31 08:49:10, 0] smbd/nttrans.c:call_nt_transact_ioctl(2332) call_nt_transact_ioctl(0x280004): Currently not implemented. [2006/12/31 08:50:42, 0] lib/fault.c:fault_report(41) === [2006/12/31 08:50:42, 0] lib/fault.c:fault_report(42) INTERNAL ERROR: Signal 11 in pid 5819 (3.0.23a-1.fc4.1) Please read the Trouble-Shooting section of the Samba3-HOWTO [2006/12/31 08:50:42, 0] lib/fault.c:fault_report(44) From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf [2006/12/31 08:50:42, 0] lib/fault.c:fault_report(45) === [2006/12/31 08:50:42, 0] lib/util.c:smb_panic(1614) PANIC (pid 5819): internal error [2006/12/31 08:50:42, 0] lib/util.c:log_stack_trace(1721) BACKTRACE: 23 stack frames: #0 smbd(log_stack_trace+0x2d) [0x707e1d] #1 smbd(smb_panic+0x56) [0x707f40] #2 smbd [0x6f4f16] #3 [0xcc6420] #4 smbd(delete_printer_key+0x17) [0x72d6c6] #5 smbd [0x79af1d] #6 smbd [0x79be99] #7 smbd(store_reg_values+0x46) [0x798bdf] #8 smbd(_reg_set_value+0x13c) [0x605b1d] #9 smbd [0x602d75] #10 smbd(api_rpcTNP+0x1d1) [0x658620] #11 smbd(api_pipe_request+0x220) [0x658ca6] #12 smbd [0x655dfd] #13 smbd [0x6562c5] #14 smbd(write_to_pipe+0xe7) [0x653d4c] #15 smbd [0x55db54] #16 smbd [0x55e0af] #17 smbd(reply_trans+0x5c3) [0x55e9ab] #18 smbd [0x5b139d] #19 smbd(smbd_process+0x840) [0x5b2707] #20 smbd(main+0xa5d) [0x7aba80] #21 /lib/libc.so.6(__libc_start_main+0xdf) [0x9c7d7f] #22 smbd [0x5429c1] [2006/12/31 08:50:42, 0] lib/fault.c:dump_core(173) dumping core in /var/log/samba/cores/smbd -Original Message- From: Res [mailto:[EMAIL PROTECTED] Sent: 30 December 2006 14:18 To: Martin Main Cc: samba Subject: Re: [Samba] Samba printing crashes all inet services On Sat, 30 Dec 2006, Martin E. Main wrote: Hi, I have a rather unusual problem with samba printing, which pulls down all networking services on my linux box. I have a Linux box running FC4 running samba 3.0.14a before asking for help, one should always ensure one is running latest stable, this is 3.0.23d you might otherwise be asking about a possible bug corrected ages ago :) -- Cheers Res So, you think you can tell Heaven from Hell? - Roger Waters -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba printing crashes all inet services
On Sun, Dec 31, 2006 at 04:09:20PM +0400, Martin E. Main wrote: Thanks, I checked this and found that I had the most recent glibc update for FC4. I then downloaded the most recent FC4 source samba rpm from fedora and I have recompiled this and installed, but I still have exactly the same core dumping problem. Ok, next step. Can you file a bug report at https://bugzilla.samba.org and upload your smb.conf and a debug level 10 log of smbd leading to that crash? The log may be large, so better set 'max log size = 0'. Thanks, Volker pgpZiZeNSFcdd.pgp Description: 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] Samba printing crashes all inet services
Thanks, now raised as bug #4316. Rgds, Martin -Original Message- From: Volker Lendecke [mailto:[EMAIL PROTECTED] Sent: 31 December 2006 19:45 To: Martin Main Cc: samba Subject: Re: [Samba] Samba printing crashes all inet services On Sun, Dec 31, 2006 at 04:09:20PM +0400, Martin E. Main wrote: Thanks, I checked this and found that I had the most recent glibc update for FC4. I then downloaded the most recent FC4 source samba rpm from fedora and I have recompiled this and installed, but I still have exactly the same core dumping problem. Ok, next step. Can you file a bug report at https://bugzilla.samba.org and upload your smb.conf and a debug level 10 log of smbd leading to that crash? The log may be large, so better set 'max log size = 0'. Thanks, Volker -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Samba printing crashes all inet services
Hi, I have a rather unusual problem with samba printing, which pulls down all networking services on my linux box. I have a Linux box running FC4 running samba 3.0.14a I have Canon Pixma ip1200 inkjet connected via usb and running under cups. Printing from a Windows XP box works whenever I run test print and thereafter, but leave it a couple of days and I try and print again, the printer stops after printing a couple of lines, then all network services on the Linux box die. As the Linux box has no monitor / keyboard, I end up having to power down from the front panel as I lose sshd services (my normal method of accessing the Linux box) The only thing that I have managed to trace in smbd.log is as follows:- [2006/12/29 09:37:28, 1] smbd/service.c:make_connection_snum(642) martin (192.168.10.2) connect to service canon_inkjet initially as user mmain (uid=0, gid=500) (pid 23041) [2006/12/29 09:37:28, 0] smbd/nttrans.c:call_nt_transact_ioctl(2317) call_nt_transact_ioctl(0x280004): Currently not implemented. Nothing of significance in the main system logs My smb.conf is as follows:- # Global parameters [global] workgroup = MAINS server string = Linux Server interfaces = eth0 obey pam restrictions = Yes pam password change = Yes passwd program = /usr/bin/passwd %u passwd chat = *New*password* %n\n *Retype*new*password* %n\n *passwd:*all*authentication*tokens*updated*successfully* username map = /etc/samba/smbusers unix password sync = Yes log file = /var/log/samba/%m.log max log size = 0 name resolve order = lmhosts hosts wins bcast time server = Yes socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 printcap name = /etc/printcap disable spoolss = Yes add machine script = /usr/sbin/useradd -d /dev/null -g samba-clients -s /bin/false -M %u domain logons = Yes preferred master = Yes domain master = Yes ldap ssl = no admin users = administrator, mmain cups options = raw [canon_inkjet] comment = Canon iP1200 path = /var/spool/samba guest ok = Yes printable = Yes printer name = Canon use client driver = Yes Any suggestions or hints I can follow, most appreciated. Many Thanks, Martin -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba printing crashes all inet services
On Sat, 30 Dec 2006, Martin E. Main wrote: Hi, I have a rather unusual problem with samba printing, which pulls down all networking services on my linux box. I have a Linux box running FC4 running samba 3.0.14a before asking for help, one should always ensure one is running latest stable, this is 3.0.23d you might otherwise be asking about a possible bug corrected ages ago :) -- Cheers Res So, you think you can tell Heaven from Hell? - Roger Waters -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Samba printing crashes all inet services
Now upgraded to latest version and instead of crashing the network it core dumps instead with following output:- [2006/12/31 08:49:10, 1] smbd/service.c:make_connection_snum(941) martin (192.168.10.2) connect to service canon_inkjet initially as user mmain (uid=0, gid=500) (pid 5819) [2006/12/31 08:49:10, 0] smbd/nttrans.c:call_nt_transact_ioctl(2332) call_nt_transact_ioctl(0x280004): Currently not implemented. [2006/12/31 08:50:42, 0] lib/fault.c:fault_report(41) === [2006/12/31 08:50:42, 0] lib/fault.c:fault_report(42) INTERNAL ERROR: Signal 11 in pid 5819 (3.0.23a-1.fc4.1) Please read the Trouble-Shooting section of the Samba3-HOWTO [2006/12/31 08:50:42, 0] lib/fault.c:fault_report(44) From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf [2006/12/31 08:50:42, 0] lib/fault.c:fault_report(45) === [2006/12/31 08:50:42, 0] lib/util.c:smb_panic(1614) PANIC (pid 5819): internal error [2006/12/31 08:50:42, 0] lib/util.c:log_stack_trace(1721) BACKTRACE: 23 stack frames: #0 smbd(log_stack_trace+0x2d) [0x707e1d] #1 smbd(smb_panic+0x56) [0x707f40] #2 smbd [0x6f4f16] #3 [0xcc6420] #4 smbd(delete_printer_key+0x17) [0x72d6c6] #5 smbd [0x79af1d] #6 smbd [0x79be99] #7 smbd(store_reg_values+0x46) [0x798bdf] #8 smbd(_reg_set_value+0x13c) [0x605b1d] #9 smbd [0x602d75] #10 smbd(api_rpcTNP+0x1d1) [0x658620] #11 smbd(api_pipe_request+0x220) [0x658ca6] #12 smbd [0x655dfd] #13 smbd [0x6562c5] #14 smbd(write_to_pipe+0xe7) [0x653d4c] #15 smbd [0x55db54] #16 smbd [0x55e0af] #17 smbd(reply_trans+0x5c3) [0x55e9ab] #18 smbd [0x5b139d] #19 smbd(smbd_process+0x840) [0x5b2707] #20 smbd(main+0xa5d) [0x7aba80] #21 /lib/libc.so.6(__libc_start_main+0xdf) [0x9c7d7f] #22 smbd [0x5429c1] [2006/12/31 08:50:42, 0] lib/fault.c:dump_core(173) dumping core in /var/log/samba/cores/smbd -Original Message- From: Res [mailto:[EMAIL PROTECTED] Sent: 30 December 2006 14:18 To: Martin Main Cc: samba Subject: Re: [Samba] Samba printing crashes all inet services On Sat, 30 Dec 2006, Martin E. Main wrote: Hi, I have a rather unusual problem with samba printing, which pulls down all networking services on my linux box. I have a Linux box running FC4 running samba 3.0.14a before asking for help, one should always ensure one is running latest stable, this is 3.0.23d you might otherwise be asking about a possible bug corrected ages ago :) -- Cheers Res So, you think you can tell Heaven from Hell? - Roger Waters -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba printing crashes all inet services
Suggest you check to see if there are any glibc updates for your FC4. - John T. On Saturday 30 December 2006 22:54, Martin E. Main wrote: Now upgraded to latest version and instead of crashing the network it core dumps instead with following output:- [2006/12/31 08:49:10, 1] smbd/service.c:make_connection_snum(941) martin (192.168.10.2) connect to service canon_inkjet initially as user mmain (uid=0, gid=500) (pid 5819) [2006/12/31 08:49:10, 0] smbd/nttrans.c:call_nt_transact_ioctl(2332) call_nt_transact_ioctl(0x280004): Currently not implemented. [2006/12/31 08:50:42, 0] lib/fault.c:fault_report(41) === [2006/12/31 08:50:42, 0] lib/fault.c:fault_report(42) INTERNAL ERROR: Signal 11 in pid 5819 (3.0.23a-1.fc4.1) Please read the Trouble-Shooting section of the Samba3-HOWTO [2006/12/31 08:50:42, 0] lib/fault.c:fault_report(44) From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf [2006/12/31 08:50:42, 0] lib/fault.c:fault_report(45) === [2006/12/31 08:50:42, 0] lib/util.c:smb_panic(1614) PANIC (pid 5819): internal error [2006/12/31 08:50:42, 0] lib/util.c:log_stack_trace(1721) BACKTRACE: 23 stack frames: #0 smbd(log_stack_trace+0x2d) [0x707e1d] #1 smbd(smb_panic+0x56) [0x707f40] #2 smbd [0x6f4f16] #3 [0xcc6420] #4 smbd(delete_printer_key+0x17) [0x72d6c6] #5 smbd [0x79af1d] #6 smbd [0x79be99] #7 smbd(store_reg_values+0x46) [0x798bdf] #8 smbd(_reg_set_value+0x13c) [0x605b1d] #9 smbd [0x602d75] #10 smbd(api_rpcTNP+0x1d1) [0x658620] #11 smbd(api_pipe_request+0x220) [0x658ca6] #12 smbd [0x655dfd] #13 smbd [0x6562c5] #14 smbd(write_to_pipe+0xe7) [0x653d4c] #15 smbd [0x55db54] #16 smbd [0x55e0af] #17 smbd(reply_trans+0x5c3) [0x55e9ab] #18 smbd [0x5b139d] #19 smbd(smbd_process+0x840) [0x5b2707] #20 smbd(main+0xa5d) [0x7aba80] #21 /lib/libc.so.6(__libc_start_main+0xdf) [0x9c7d7f] #22 smbd [0x5429c1] [2006/12/31 08:50:42, 0] lib/fault.c:dump_core(173) dumping core in /var/log/samba/cores/smbd -Original Message- From: Res [mailto:[EMAIL PROTECTED] Sent: 30 December 2006 14:18 To: Martin Main Cc: samba Subject: Re: [Samba] Samba printing crashes all inet services On Sat, 30 Dec 2006, Martin E. Main wrote: Hi, I have a rather unusual problem with samba printing, which pulls down all networking services on my linux box. I have a Linux box running FC4 running samba 3.0.14a before asking for help, one should always ensure one is running latest stable, this is 3.0.23d you might otherwise be asking about a possible bug corrected ages ago :) -- Cheers Res So, you think you can tell Heaven from Hell? - Roger Waters -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] problem with cups and samba: printing is disabled
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/28/2006 05:40 AM, Luca Ferrari escreveu: Hi, I've got a windows printer that is no more working. If I try to see the status of the printer I get: What do you mean with is no more working? It was working but you upgrade or change something on the system and it stopped? Or it was working on another computer and you change it to a new machine? And what do you mean with a windows printer? It was installed phisically on a windows system? Or are you using it via printer share? server:~ # lpc status la02 la02: printer is on device 'smb' speed -1 queuing is enabled printing is disabled no entries daemon present that means printing is no enabled. If I try to enable the printer I cannot get the printer enabled: server:~ # lpadmin -p la02 -E server:~ # lpc status la02 la02: printer is on device 'smb' speed -1 queuing is enabled printing is disabled no entries daemon present In the printers.conf file there's the message: Printer la02 Info la02 DeviceURI smb://guest:[EMAIL PROTECTED]/l_a02 State Stopped StateMessage Call timed out: server did not respond after 1 milliseconds closing remote file _stdin_ Accepting Yes JobSheets none none QuotaPeriod 0 PageLimit 0 KLimit 0 /Printer The server is not answering, something is wrong with the machine that is sharing the printer. but if I smbclient to the printer I cannot connect! Any idea? Yes, check the printer server and access control. Thanks, Luca Kind regards, - -- Felipe Augusto van de Wiel [EMAIL PROTECTED] Coordenadoria de Tecnologia da Informação (CTI) - SEDU/PARANACIDADE http://www.paranacidade.org.br/ Phone: (+55 41 3350 3300) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Debian - http://enigmail.mozdev.org iD8DBQFFInsDCj65ZxU4gPQRAgH+AKCURHQWVa7lJ8Cs2+elUUs5dFNbyQCfQpZ/ UJJGYtJ2h1RG153bzOmfSSo= =WDTl -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] problem with cups and samba: printing is disabled
Hi, I've got a windows printer that is no more working. If I try to see the status of the printer I get: server:~ # lpc status la02 la02: printer is on device 'smb' speed -1 queuing is enabled printing is disabled no entries daemon present that means printing is no enabled. If I try to enable the printer I cannot get the printer enabled: server:~ # lpadmin -p la02 -E server:~ # lpc status la02 la02: printer is on device 'smb' speed -1 queuing is enabled printing is disabled no entries daemon present In the printers.conf file there's the message: Printer la02 Info la02 DeviceURI smb://guest:[EMAIL PROTECTED]/l_a02 State Stopped StateMessage Call timed out: server did not respond after 1 milliseconds closing remote file _stdin_ Accepting Yes JobSheets none none QuotaPeriod 0 PageLimit 0 KLimit 0 /Printer but if I smbclient to the printer I cannot connect! Any idea? Thanks, Luca -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
