similar to: odd swat issues, odd printer issue, odd crashes..

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.

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

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]

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

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)

Hi there, I've a linux server (PII 233, 94mb ram) running Mandrake Linux 9.1 with an HP printer attached to it. I've configured the printer (I'm using CUPS) and it works fine. Next, I've configured samba: [global] . . . workgroup = MYWORKGROUP security = share log level = 2 printing = cups . . . [hp] printer = hp printable = yes path = /var/spool/samba

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

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

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]

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

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

hi! I'm using a pdc samba+ldap+cups (on sarge) with samba 3.0.21a. My problem is that I can't set in pause my shared printer (print and manage jobs are ok). In samba logs and syslog aren't errors (log level 10) except: find_printer_index_by_hnd: Printer handle not found: find_printer_index_by_hnd : Printer handle not found: close_printer_handle: Invalid handle

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)

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

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

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

I've got two brand-new, fully-patched XP SP2 clients who are suffering a mysterious malaise. These two machines will cause a smbd panic when printing or accessing files on a somewhat random basis. Now, the puzzling thing is that three other XP SP2 clients, including one of the exact same configuration, have no issues whatsoever. I've basically ruled out hardware failure on the server,

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 is [2005/07/01 10:37:55, 5]

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 Debian 3.0r1 Samba 3.0 Been getting the same error on the