similar to: changing printer device settings: changes not applied.

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

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 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]

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

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've a question about a problem using a samba share in a UNIX AIX server. In my scenarious there is a fileNET server (running on a win2000 server) which use a samba share on a AIX sever for cacheing file, this share is configured for allow access to a particular user (pangol). It seams that user have access permission but an error is returned when fileNET try to write a file. Thanks in

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, We've installed a samba-printserver at a customer using a large number of Nashuatec-printers. Most of them are Optra T164, formerly known as NRG P6025 PS3. In our setup we defined 1 user (printadmin) which manages all printers. All printusers are mapped to guest. User printadmin installed the printdrivers on the server and the clients download the driver during their first connection.

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 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:

Hi all, After building Samba 4.1.20 for Ubuntu 14.04 x64 I encountered this issue when using shared printers: every time a client prints or changes printer settings, this message is logged in the log: dcerpc_spoolss_ReplyClosePrinter failed [NT_STATUS_RPC_PROCNUM_OUT_OF_RANGE]. Printers print fine, so it is probably harmless, but I still wonder why this happens. With log level = 3 I get

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

On a server that has been running smoothly since it was setup, and with no changes to configurations or network or anything, users cannot save a shared QuickBooks file. they have been regularly using, updating and saving to this file for a few months. All users are able to create and update other files in the same share. I have not confirmed if they are able to create and update new QuickBooks

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

Hai, Can you tell me the brand and driver of the printer your trying , that helps. ( or send me a copy/link of the driver your installing ) I had a read thought your old(er) threat, but that didnt help. I did find the error in the following source code of samba. source3/rpc_server/srv_spoolss_nt.c but i cant help with that code much to complex for me, but at least you know is a "by

queue with the new driver, on teh samba server I see: rpcclient -U <uid> <printserver> -c 'enumdrivers' [ snip ] [Windows x64] Printer Driver Info 1: Driver Name: [KONICA MINOLTA 350/250/200 VPS] [printserver] # rpcclient -U<uid> -c 'setdriver itmfp1_x64 "KONICA MINOLTA 350/250/200 VPS"' <printserver> Enter chbeyer's password:

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