similar to: Installing printer drivers makes W2K misbehave

Hi, After using the client driver for a long time, I want to give a try to the drivers installed on Samba server. I am using the how-to at http://us1.samba.org/samba/docs/man/Samba-HOWTO-Collection/classicalprinting.html It goes fine up to "installing drivers into [print$] using APW". I can see a list of drivers files growing into W32X86. But when I try to access the properties of a

Mandi! Julien TEHERY via samba In chel di` si favelave... > I have a question about printer drivers management in Samba4 (Samba version > 4.7.6, Ubuntu 18) First, verify that drivers loading work, with another standard printer, eg, Apple Color LaserJet for examples. Secondly... driver loading is very 'picky'. Try to: a) load the driver 2-5 time subsequently, sometime work b)

Hello, I was using version 3.0.14 and upgraded to 3.0.20a. I did not change my config, however, I am seeing some serious problems now, and I am not sure what to do about it. I noticed there were a large number of changes between these two versions. I looked at the changes briefly, but there are just so many. This samba server is a domain memmber, on an ADS domain with a win 2003 enterprise

Hello! SSIA - when syslinux sees 'BOOT_IMAGE=' on the append line, something seems to go terribly wrong (didn't investigate in detail). You don't even get to see a boot-prompt, even if you try to force it. pxelinux shows the same problem, so I figure it's something generic in the config parser ... Best regards, Andreas P.S: and thanks for this software ;) -- "The

Hello there. I have a network with 35 new Windows 7 (64 bit) PCs that should connect to printers via a cups/samba server. I want them to use their own windows drivers, and I want these to be installed automatically from print$ when they first connect. I'm trying to install the drivers from the clients as described here:

Greetings, We're running samba 3.0.22 on debian sarge. We use the following instructions to set the device mode on new printers: http://us3.samba.org/samba/docs/man/Samba-HOWTO-Collection/classicalprinting.html#prt-modeset How do we query samba to see if a given printer share has it's driver device mode set or not? regards, Ryan

Hi, I was looking though the easy Add Printer Wizard Driver Installation instructions here http://us6.samba.org/samba/docs/man/Samba-HOWTO-Collection/classicalprinting.html#id2620623 but found that it did not work. After saying no to "Do you want to install the driver now" when properties comes up nothing is editable so one can't connect to advanced or new driver to install

Gentleman, In one of my slackware servers I put samba acting as a printer server connected to a Hewlett-Packard 2420D (D stands for duplex). In CUPS I'm using the 'raw' driver. So I let the clients to perform the driver stuff. On samba, I followed the procedures described on http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/classicalprinting.html#inst-rpc to make

Drug US1 US2 Aptecha Celebrex 235.54 269.99 121.02 Detrol LA 157.99 190.99 55.3 Flomax 166.00 190.99 93.45 Lipitor 174.99 200.99 137.7 Novaldex 108.6 129.99 22.48 Norvasc 186.66 203.99 161.93 Plavix 107.99 106.99 64.53 Prevacid 117.39 134.99 59.83 Prilosec 115.99 126.99 57.75 Zyrtec 181.1 200.99 58.79 US1=c(235.54,157.99,166,174.99,108.60,186.66,107.99,117.39,115.99,181.10)

Hi, I've set up a printer called "UREW-EDV" using the cups webinterface. After that an enumprinters give the following output: rpcclient $> enumprintershp LaserJet 1320 PCL 6 flags:[0x800000] name:[\\server\UREW-EDV] description:[\\server\UREW-EDV,,Netzwerkdrucker-EDV] comment:[Netzwerkdrucker-EDV] Next step is uploading a driver using APW:

http://bugs.freedesktop.org/show_bug.cgi?id=18636 Summary: nouveau git does not run on NV34M Product: xorg Version: git Platform: PowerPC OS/Version: All Status: NEW Severity: critical Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org ReportedBy: wouter

Hello All, I'm having trouble with 64 bit Xerox drivers on my Samba server. The below quote if from another thread which I have followed but on the client Win 7 64 bit machine, I get an error: "The specified location does not contain the driver for the Xerox WorkCentre 7675 rev2 PS for the requested processor architecture." Trying to add the driver from at 64 bit client first also

hello everyone. i am running into an issue where xp pro clients must have local admin rights to be able to install a samba printer. the actual error message is: A policy is in effect on your computer which prevents you from connecting to this print queue. Please contact your System Administrator. well, i am the system administrator and am not sure where to go next. i am able to install the

Hello, I have a problem with the point'n'print driver installation. I followed the instructions on https://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/classicalprinting.html#id2626650 Now if I try to print on the Windows client I get an error 0x00000006. Here is my configuration. Printer: Kyocera FS-C2026MFP+ Server: Debian Squeeze, Samba version 3.5.6, CUPS cersion 1.4.4 Client:

Hi, We're running samba-3.0.28a w/ cups-1.3.7 on debian etch to serve point and print to windows clients. http://us6.samba.org/samba/docs/man/Samba-HOWTO-Collection/classicalprinting.html#prt-modeset How do I check if a queue had the device mode set or not? thanks, Ryan

I'm trying to install print drivers onto my samba 3.0.28 server (Fedora Core 8) following the Add Printer Wizard Driver Installation directions here: http://us3.samba.org/samba/docs/man/Samba-HOWTO-Collection/classicalprinting.html#id388379 Unfortunately, when I try to add the print driver, I receive a Windows "Add Printer Driver Wizard : Unable to install Ghostscript PDF, Windows

On Fri, Mar 03, 2023 at 04:17:40PM -0600, Eric Blake wrote: > On Fri, Dec 16, 2022 at 10:32:01PM +0300, Vladimir Sementsov-Ogievskiy wrote: > > s-o-b line missed. > > I'm not sure if the NBD project has a strict policy on including one, > but I don't mind adding it. I've never required it, mostly because it's something that I myself always forget, too, so,

In my continued attempt to get winbindd working on a simple domain, I decided to go through the documentation in more detail, searching for some possibly hidden clues. In doing so I came across some instruction that left me a little confused... Fast Start: Cure for Impatience - Domain Member Server http://us2.samba.org/samba/docs/man/howto/FastStart.html#id2512775 The first point is in the

These are derived from the FreeBSD functions here: https://github.com/freebsd/freebsd/blob/master/sys/libkern/strcasecmp.c Thanks: Eric Blake. --- common/include/Makefile.am | 6 +++ common/include/ascii-ctype.h | 6 +++ common/include/ascii-string.h | 77 ++++++++++++++++++++++++++++ common/include/test-ascii-string.c | 79 +++++++++++++++++++++++++++++ server/main.c

On Mon, Sep 26, 2016 at 11:43:42AM +0100, Alex Bligh wrote: > > > On 26 Sep 2016, at 10:21, Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net> wrote: > > > > Wow, that was quick! Thank you. > > > > I stumbled upon another problem: Apparently nbd-tester-client and nbdkit > > disagree on what constitutes a valid flush request. > >