similar to: printing in wine usinc /etc/printcap

I'm running Samba 3.0.21a (blastwave build) on Solaris 9. The Solaris servers have no printers attached or accessible, just file service. Samba users authenticate off a Win2003 AD controller and get printing from that. I got rid of the "Unable to connect to CUPS Server" errors by adding to smb.conf the line printing=bsd but I am still getting smbd[4809]: [ID 702911 daemon.error]

Hi, following situation: 1) You create a raw printer (called "testprinter") under cups and leave the description-field (info-field) empty. cups will create an entry in /etc/printcap of the form testprinter|testprinter:rm=linux100:rp=testprinter: 2) You start samba with a standard [printers] and [print$] share. samba will expose the printqueue to the clients. 3) You upload a windows

I don't have a solution, but I do want to keep this thread alive until we get it resolved. I'm in the same situation. I can print fine, but it says that annoying message. Do you guys print to an LPD unix queue? My linux print server is sending the job to a LPD linux box that is connected to the printer local. (Our printer support requires it that way). Has anyone been able to

I have played around with samba now for quite a while but couldnt print on my win2k box with koffice. with the command line smbclient it works: smbclient //server/hpdeskje -N -P -U user -c 'print hello' prints a text (from the file hello) "Hello World" Also a print to file file off my win2k box would print fine with smbclient. Only, I cant quite find out how the printcap

Hi list. I'm having problems w/ printing using Samba on Redhat 8. Shared drives work fine yet my CUPS printing doesn't work. I sure appreciate any input. For what it's worth, I couldn't find any printing related errors in /var/log/samba/. I notice that the printcap doesn't have a sub-directory named cups like my old Debian box. Could that be it? Here's my smb.conf

Morning... Just spent this evening getting printing setup off my FreeBSD machine (oh, how I love Solaris at these times *groan*)...got it now so that I can print directly from Netscape, color and graphics and all. The printer is an HP 560c. Now, I want to be able to print from my Windoze95 machine, and have samba setup for that, as well as file sharing. If I setup my Windoze machine such

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi, i currently tried to setup a samba print server which uses cups as default printing system and for some special printers i want to use my own scripts. samba-3.0.0 is linked against libcups and printing via cups and the driver download works perfect. whe i try to specify a special printer with "printing = bsd/lprng/sysv" my own

I am using samba-2.2.7-3.7.2 on a redhat 7.2 server with an attached printer which is run by CUPS. It worked OK until I upgraded to samba-2.2.7-3.7.2. Now I can print locally on the server machine, but not from the windows machines on the LAN. The error message on the windows box is " Unable to create a print job." Another error, produced daily when samba is "re-initialized"

On 28/03/2008 12:05 PM, seanpor at acm.org wrote: > Good afternoon, > > This is possibly a windows only bug, definitely of comparatively low > importance - but for the sake of completeness here we go. I've > searched http://bugs.R-project.org/ etc., but can find no mention. > > For RGui.exe, the CPU usage goes to 100% for certain dialog boxes for > the duration that

The Wine development release 3.13 is now available. What's new in this release (see below for details): - Vulkan support on macOS using MoltenVK. - Initial support for performance data in the registry. - Mono engine updated with some bug fixes. - Support for fetching BIOS information on Linux. - GnuTLS also used on macOS when available. - Improvements in the standard Task Dialog.

Good afternoon, This is possibly a windows only bug, definitely of comparatively low importance - but for the sake of completeness here we go. I've searched http://bugs.R-project.org/ etc., but can find no mention. For RGui.exe, the CPU usage goes to 100% for certain dialog boxes for the duration that the dialog box is visible, e.g. * check CPU usage is low * On the RGui.exe menu chose

Hi Ingo, >It is just a WAVEFORMATEX with a GUID in it. For the ACM system it is just a format with the id >WAVE_FORMAT_EXTENSIBLE and since ACM drivers are not registered by wFormatTag it should be working. >For testing purposes I've written a Vorbis ACM driver, that uses a WAVEFORMATEXTENSIBLE and I experienced >a problem when opening files with Media Player. It spend quite some

The Wine development release 1.1.16 is now available. What's new in this release (see below for details): - Improved SANE scanner support. - Support for digital CD audio playback. - Improved cookies management in Wininet. - Support for building stand-alone 16-bit modules. - Many fixes to the regression tests on Windows. - Various bug fixes. The source is available from the

Hi, I just upgraded from cups-1.3.8/samba-3.4.1 to cups-1.4.1/samba-3.4.3 After upgrading, the samba log showed that it could not find the printcap file - previously cups was not generating a printcap file, but things worked fine. I changed cupsd.conf to produce a printcap file, but the samba log shows it cannot find it, even though I placed it in /etc, /etc/cups, /usr/local/etc,

Hello all. I'm currently setting up a RedHat box with 4 nics to handle SMB printing for 4 separate subnets. I have CUPS printing set up and functioning. I have a separate smb.conf file configured to bind to one interface each, and everything is dandy. Here is where I hit my problem. When I have the following line from the conf file set as you see it, I see all the print queues without

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Noticed the following when conducting torture tests today: [2006/05/12 14:04:24, 0] printing/pcap.c:pcap_cache_reload(159) Unable to open printcap file /etc/printcap for read! ...which to me, was interesting, because I was not under the impression I was using load printers. Apparently, at some point, it became the default. That's fine, but I

Hi folks, I have a print server, running SPARC Solaris 9. I've just upgraded from Samba 3.0.10 to 3.0.22 and immediately hit system load issues which appear to be related to the use of "lpstat -v" to determine the available print queues. There are about 70 Unix print queues on this system. Running "lpstat -v" can take something like 20s of wall-clock time. lpstat

Peter> My problem is browsing printers that names are more than Peter> 8 chars long. Any printer that is longer than 8 chars (in the Peter> printcap file) does not show up when browsing. Peter> Anybody else affected by this? Is there a fix? Jim> I had considered "fixing" the code but then I wondered whether I would run Jim> into DOS's 8.3 filenaming convention

Hi I?ve been carrying out some upgrades to our SCO Unixware 7 server. I?ve updated from 7.1.3 to 7.1.4, and then installed maintenance pack2. On the Samba side, this means that Samba has been upgraded from 2.2.8a (with UnxWare 7.1.3) to 3.0.0 (with UnixWare 7.1.4). Everything seemed to be working fine at this point. Samba was then upgraded to 3.0.10 (with maintenance pack 2), and I

According to all of the documentation I can find, an /etc/printcap file (or whatever filename is specified with the Printcap directive) is generated by cupsd ever time a printer is added or removed. On all of my CentOS 6.7 systems, this is NOT happening. I can restart cups and add or remove printers over and over and it still doesn't generate the printcap file. Is this a known issue, or is