similar to: Printing from Windows to Samba takes a LOT of time.

Hi there, Some days ago I've sent a mail talking about some problems printing from a Windows machine to a printer installed on a Linux server (running CUPS 1.1.19 and SAMBA 2.2.7) What was happening is when I send a page to be printed, I way 15/20 secs per page. I've installed the network printer with the correct HP drivers. After trying a LOT of stuff, I've installed the

Help! I'm in the process of migrating my companies Windows NT print server to Samba 3.2. (yea) But I'm running into a few problems. (boo) I've searched the archives and google with no success... I have about 15 clients testing out the new server, mainly Win2k. Some work fine, but others have problems connecting, getting the "Unable to Connect" message in the printer folder.

Hi list, I've just figured it out. When we're installing the drivers from adobe there's a part where we must "Select the Printer Model". By default it uses the "Generic Postscript Printer" (it has an associated PPD for that). We must get a PPD for our printer (installed on the linux server) from the www.linuxprinting.org, click the "Browse" button and

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 0x000006d1. 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

I realized that my choice of options for grep did not do a very good job of including the last error message before the INTERNAL ERROR. I've included it in this email. Sorry. create_policy_hnd: ERROR: too many handles (1025) on this pipe. [2003/04/21 15:35:21, 0, pid=2798, effective(502, 501), real(0, 0)] rpc_server/srv_lsa_hnd.c:create_policy_hnd(109) create_policy_hnd: ERROR: too many

I have read the BUGS.txt file, used 'testparm' (successfully), and run through all the steps in DIAGNOSIS.txt. I don't see any problems that those tools have identified. The BUGS.txt file indicated that INTERNAL ERROR was almost certainly the result of a bug. I'm hopeful I have sent you the information you need. Let me know if there is something more I need to send. What

Hello there. I've been having problems with printers, and I could not find anything on google, thats why I'm writing you. A piece of the logfile: [2004/01/13 17:03:51, 2] rpc_server/srv_spoolss_nt.c:find_printer_index_by_hnd(263) find_printer_index_by_hnd: Printer handle not found: _spoolss_fcpn: Invalid handle (OTHER:2730:3433) [2004/01/13 17:03:51, 2]

greetings. my problem is i can't print from windows 2000 or windows xp. my solaris box can print fine. on smoking (solaris 10, samba host) smbclient '//smoking/hp2605' -U jgs%password put /etc/motd i get the printout. on windows, this works: echo hiya^L > \\smoking\hp2605 on windows, from M$ word, the print SEEMS to go into the queue. i click on the printer, get the box that

I am unable to setup printers on my samba system any long after I updated to the latest Solaris 10 Patch cluster. What I get in my log files all the time is: [2007/03/07 11:58:19, 2, effective(60001, 60001), real(0, 0)] rpc_server/srv_spoolss_nt.c:find_printer_index_by_hnd(263) find_printer_index_by_hnd: Printer handle not found: _spoolss_writeprinter: Invalid handle (OTHER:11687:16175)

Before I start, can you CC me if you respond as im not subscribed. thanks! (this is samba 3.0.4 on suse enterprise linux, kernel 2.6.5) first, the swat issue. I had a machine that had 2 network interface cards in it. I have since removed one card, mainly because it caused weird performace issues unrelated to samba. the interface addresses were 192.168.0.200 and 192.168.0.201 another machine now

Howdy! the setup: RH-VALE 6.2.4 running samba2.2.2 cvs from 11/24/2001... user running NT 4.0 SP6a the problem: I have a user that cannot print - She can add the printer but can't print. log for that machine shows the following: ... normal looking connections to obtain drivers - all look OK - no complaints.. .. then this - libsmb/namequery.c:name_query(415) Got a positive name query

Hi all, IPV6 printing is not happening with samba-3.6.x in win7 but the same works on win8 onwords. Why smb_create is calling many times? Because of this file-size getting zero-length. With ipv4-everything works fine. [2014/04/26 12:14:28.867903, 10] printing/printing.c:568(print_job_find) print_job_find: returning system job -1 for jobid 868269967. [2014/04/26 12:14:28.868096, 1]

Hi, I am using Version 3.0.2a of samba on Linux 2.4.18 (suse with self-compiled samba from tarball) smb.conf: [IEPRINT] path = /home/htmprint/tmp printable = Yes print command = /home/htmprint/Programme/virtual_printer.sh %s After some weeks with some thousand printjobs generated by a program running as W2k-service the printer was no more available. I checked printing

Anyone have any suggestions for this? --------------------- Repeatedly getting the following error, any help out there for this? I've dug around the internet for several hours with no luck. [2003/12/11 19:51:34, 2] rpc_server/srv_spoolss_nt.c:find_printer_index_by_hnd(268) find_printer_index_by_hnd: Printer handle not found:_spoolss_writeprinter: Invalid handle (OTHER:1583:10554) Running

do I not have enough info for someont to take a crack at this? hey folks. got cups set up and working on a freebsd 4.11 box running samba 2.2.10. I can print locally from the freebsd box just fine.. when I try to print from remote windows boxes on the network, I only get blank pages (may be empty banner or form feeds). but I jacked up the logging and the only "error" i see in there

I set it up as a raw printer using printconf. I added it to samba with swat and I get te\he following errors in my log. [2002/07/08 17:35:11, 0] rpc_server/srv_spoolss_nt.c:close_printer_handle(257) close_printer_handle: Invalid handle (OTHER) [2002/07/08 17:35:11, 0] rpc_server/srv_spoolss_nt.c:close_printer_handle(257) close_printer_handle: Invalid handle (OTHER) The printer name and the queue

hey Gerald, seems like this is a bug in 2.2.3a (?) Print request from various MS WINDOWS platforms doesn't succeed on the first try but on the second. Sometimes the applications give something back like 'RPC server not reachable' the first time. As soon as there is an already established connection betweeen the client and the server everything works fine, I did some debugging (-d 2)

hey, I still have the problem described further down ! I had to downgrade to an older version to keep printing running on my site, is there any chance to investigate on this ? Please tell me if you need any further information / debugging output. This should be really easy to reproduce... kind regards ~christoph -- /* Christoph Beyer | Office: Building 2b / 23 *\ * DESY

-------- Original Message -------- Subject: [Samba] second printer connection Date: Thu, 04 Mar 2004 14:17:44 -0600 From: Gregory W. Eckrich <newxman@outdrs.net> To: samba <samba@lists.samba.org> PROBLEM: unable to print to the 2nd of two printers on a samba host. ENVIRONMENT: -4 systems in a home network; connected to an HP Pro Curve hub (10 meg) -3 systems run Red Hat linux

Hi list I have two very similar printers set up on CUPS and Samba is configured to share the drivers. I had been playing around with setting up a RAW printer queue with native Windows drivers but eventually gave up on that. I deleted all printers and redid them from scratch and now only one of them works. Setup: Ubuntu Karmic 2.6.31-15-server #50-Ubuntu SMP Tue Nov 10 15:50:36 UTC 2009