similar to: INTERNAL ERROR Report

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

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

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]

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

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.

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

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

In a prior email, I reported seeing the following in a user log file > 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 handles (1025) on this pipe. > [2003/04/21 15:35:21, 0, pid=2798, effective(502, 501),

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 All, Since updating a from 3.0.1-2 to 3.0.2-1 a few weeks back I've been unable to print. I checked all the obvios settings, but as they had been working perfectly for some time prior was not surprised to find the configuration was correct. The authentication is configured via winbind to a 2000 ADS PDC. security = DOMAIN I've since updated again to 3.0.2-2 and found the issue

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

I have been trying to setup a new print server on Fedora 12 based around samba-3.4.7-58.fc12.x86_64 and cups-1.4.2-28.fc12.x86_64. All looks good except for the ability for printer administrators to manage printers. Whether I specify users in a system group using the deprecated printer admin option, or specifically using net rpc rights and the SePrinterOperatorPrivilege, it does not matter.

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

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

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)

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

Hi, I'm using samba-2.2.1a on a Debian Linux box as a Debian package. It only serves as a printserver for about 35 printers which are all in /etc/printcap. Samba exports them all through the [printers] section in smb.conf. "guest ok = yes" for the [printers] The problem is as follows: - printadmin (having uid 0) logs onto the printserver using a win2k client - printadmin

I'm trying to figure out why I'm getting permission denied when trying to print from one user account only. all others work fine. the print server is configured as a domain controller backed by ldap. aarcane at density:/var/log$ sudo testparm -s Load smb config files from /etc/samba/smb.conf rlimit_max: rlimit_max (1024) below minimum Windows limit (16384) Processing section

Hi folks, First of all I have a well-working samba-2.2.2-20011013 on a Redhat 7.1 with 2.4.7. (Fast like a thunder 8-). Good job guys!) But. I have a little problem with printing: At my work we have only NT 4.0 workstations on our LAN with sp6a or sp5. This problem is appearing when a client try to print onto a printer attached to samba. Sometimes. But sometimes not. > api_net_sam_logon: