search for: openprinterex

...ows XP client with a samba server. The windows driver seems to use different ways of smb/printer communication for printing in normal/duplex mode and for printing brochures. The latter failes silently. normal/duplex printing uses: SMB Open Print File Request brochure printing starts with: SPOOLSS OpenPrinterEx request I recorded the network transmission during printing and received the following for brochure printing (which fails): Source Dest Protocol Info client server SMB Session Setup AndX Request, NTLMSSP_NEGOTIATE server client SMB Session Setup AndX Response, NTLMSSP_CHALLENGE,...

...printer and not a network printer connection. This is much the same behavior that occurs when disable spoolss = yes. Under normal circumstances, the NT/200x client attempts to open the network printer using MS-RPC. Because the client considers the printer to be local, it attempts to issue the OpenPrinterEx() call requesting access rights associated with the logged on user. If the user possesses local administrator rights but not root privilege on the Samba host (often the case), the OpenPrinterEx() call fails. The result is that the client now displays an "Access Denied; Unable to connect&qu...

I have a small Samba 2.2.1a plus Win2k workgroup. Samba is running on Redhat 7.2. There is a networked laserjet 5000 using a static IP which I can print to successfuly from the linux box, and from the win2k workstations via the queue on the linux box. The weird thing is that, on the win2k worksations, if I double click on the printer icon the status of the printer is reported as "Access

...recv: 4280 353 1.016831 192.168.40.46 192.168.40.2 TCP [TCP segment of a reassembled PDU] 354 1.018438 192.168.40.46 192.168.40.2 TCP [TCP segment of a reassembled PDU] 355 1.018453 192.168.40.46 192.168.40.2 SPOOLSS OpenPrinterEx request, \\CORN\rawPrinter 356 1.018470 192.168.40.2 192.168.40.46 TCP microsoft-ds > 58439 [ACK] Seq=198047 Ack=199308 Win=41664 Len=0 357 1.018803 192.168.40.2 192.168.40.46 SPOOLSS OpenPrinterEx response 358 1.023767 192.168.40.46...

Hi, I have Samba 2.2.3a setup on a RH Linux 2.4.18-10 box as a print server. It works fine, well kind of. The users can print their documents but on their end the get the good old "Access Denied, unable to connect" error. It does not seem to have any effect on the actual printing but its sucks not being able to cancel a job. Anyone know if it is possible to not get this error and

...all of the Linux printers just fine as well. But, the APW does not appear in the Printers folder for the Linux host machine when viewed in the W2K virtual machine. According to the Samba docs, this is because "The APW will be show only if the connected user is able to successfully execute an OpenPrinterEx(\\server) with administrative privileges (i.e. root or printer admin)." As a result, I can't add Windows 2000 printer drivers to Samba, so I can't print from the W2K virtual machine. What should I check next? Thanks! Mark # smb.conf is the main samba configuration file. You find a...

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 all. I was wondering if anyone had a successful exampel of using the "add printer command" with cups so that the windows print migrator could be utilised. Seeing as Jerry as spent time on this it would be a shame not to know how to use it. ;-) I'm guessing that it would be along the lines of: add printer command = lpadmin option1 option2 && cupsaddsmb option1 but

I have a Red Hat Linux release 7.1 (Seawolf) Samba 2.2.4 PDC and fileserver built with --with-ldapsam. The clients are either win9x or WinY2k. Authenitcation, etc... all works great. But print sharing is a real pain. Under 2.2.1a printing worked great, but our VOIP phone system wouldn't joint the domain until we upgraded to 2.2.4. Initial testing of 2.2.4 made it seem like everything