similar to: Solution! CUPS Printing / Win2K with Access Denied

Have other expirenced "bad drivers" which corrupt the output when brinting via Samba / CUPS in RAW mode? I have a HP LJ4000 and some little label printer working fine on a network. Today a Gestetner 3222 was added (also goes by some Richo PN#) with their current PCL6 and PCL5e driver. The printer does not have its PS card installed, so I can't use that. Multiple pages are printed

After much trying I have finally got this to work and I'm slightly embarassed to admit that the old RTFM tripped me up. In the Samba 3 HOWTO - the official one, rather than the draft I was originally using - it states quite clearly that to get point 'n' print to work "use client driver" needs to be set to "no" in the [global] section of smb.conf, and the samba

Greetings- I have not found discussed / documented what to do with machine accounts when moving a Samba PDC to new hardware. I have seen that uid/gid numbers must match between the old/new system. I am thinking to use adduser to accomplish that, then make the numbers on the new server match, using a text editor. After that, can I simply enter the machine account entries by hand with a text

OK we do all the steps in my previous missive and everything looks fine, landscape, collating the whole works. This is on a Laserjet 4000 with the latest PCL6 driver. The firm still has a good number of Laserjet 4s so we dutifully load up the latest PCL5E driver for the 4 and connect to the 4 on a couple of workstations. Everything goes to hell. Landscpae, collating and all other problems

Greetings- I am wondering if anyone from the Samba team would happen to have interest in creating official builds for Ubuntu? To add a twist, unfortunately I would not be fishing for 7.10 packages, but rather 7.04 as we ran into too many issues with 7.10 whereas 7.04 seems rock solid stable. Or, are there packages built of Samba releases for Ubuntu external to samba.org? Thanks, -- Michael

Hello all! Samba works fine. GREATE WORK OF SAMBA TEAM!!! But when i try to upload more than one driver for printers samba writes to log: [2001/03/30 13:30:18, 0] printing/nt_printing.c:move_driver_to_download_area(1178) move_driver_to_download_area: Unable to rename [WIN40/hpblgbe.drv] to [WIN40/0/hpblgbe.drv] and then if i try to download driver to workstation, samba says that driver is not

Recently, we added a Sharp AR-M550N copier to our network. This device functions as an MFC (scanner/printer/copier). When I attempt to install the drivers to the SAMBA server, I receive an error message which displays briefly and then I receive the following error message when trying to access the properties of the printer. Function address 0x3119c9f caused a protection fault. (exception code

I found the solution, or at least a work around, for my posting: "Can not grant SeMachineAccountPrivilege on Debian Etch" I ended up: 1) ssh to Debian Etch as root 2) smbpasswd -a root 3) issue the "net rpc rights grant ..." command SUCCESS!!! So, that raises the question that what MUST be executed as user root verses a member of ntgroup="Domain Admins"? I suspect

Maybe there's a trivial solution to this, but it's confused the hell out of me. I'm trying to upload the latest Windows XP PCL6 driver for our Laserjet 4250TN to my Samba 3.0.11 server. It works, and uploads the driver files, but then at the end it produces an error on the XP client "the operation could not be completed". The logs on the samba server state:

This occurs with Samba downloaded drivers of an installed printer. When attempting to view the printer properties you receive the following error: ?Function address 0x2d04193 caused a protection fault. (exception code 0xc0000005) Some or all property page(s) may not be displayed.? Followed by: ?The ?<drivername>? printer driver is not installed on this computer. Some printer properties

man smb.conf does not specifically say admin users supports @groupname syntax. Google turns up lots of examples of it being used, but everyone hanging their smb.conf's up to air does not mean they are 100% accurate either. Here, Samba 3.0.4 in PDC mode, I can not get it to accept the name of a group in /etc/group, user ID's only. -- Michael Lueck Lueck Data Systems Remove the upper

I am now getting around to setting up a test printer. CUPS is installed in RAW mode and a test print work A-OK. I also set the CUPS printer que as default. Below are my printer related smb.conf lines for this PDC. [global] ... ########## NT Domain Related ########## admin users = pianoman ldsinst ... ########## Printing ########## printcap name = CUPS printing = CUPS [printers]

Is there a trick to append an additional directory level onto the defauly behavior of a [homes] share looking in /etc/passwd to find the users Linux home dir? It would offer a bit of protection if Windows clients ended up in say the WinHome directory within their Linux home directory when logging in from Windows so they are not tempted to tamper with their desktop settings files for Linux from

Hi folks, I have a samba PDC with about 5 printers (from HP, Kyocera and Canon) and except the one HP Laserjet 2055 PCL6 all drivers (installed via 'Add Printer Wizard Driver Installation') for all printers did install well and without major issues in the print$-driver-share. With this driver all seems well until I finally hit the "ok"-button in the printer properties

Greetings- I am working through coming up with a Linux client integration to Samba PDC's. I mount several shares with this sort of syntax: /bin/mount -t cifs -o credentials=/home/userid/.smbcredentials,uid=userid,gid=userid,dmask=0777,fmask=0666 //ldslnx01/data /mnt/ldslnx01/data/ However when I create new files/dirs on the Samba share from the Linux workstation, the perms are not 0666/0777

Recent list messages got me thinking... Is there a way to support both local and roaming profile with one server / domain? As I understand it, the "magic" line that tells Samba not to do roaming profiles is the smb.conf line: logon path = Which the line must exist, and must be set to null. But that is in the global section. So is there a way to support both local and roaming...

I am testing out Debian Etch, and ran into an issue granting SeMachineAccountPrivilege to an account... which granting that permission had been troublesome in the past. The command I am issuing is: net rpc rights grant LDS-DEMO\\ldsinst SeMachineAccountPrivilege And I try running the command with an account that is a member of the "Domain Admins" group. The command returns: Failed to

One of the servers we admin has countless such errors in log.smbd: [2007/05/07 14:17:08, 0] tdb/tdbutil.c:tdb_log(783) tdb(/var/cache/samba/printing/HPLJ3600.tdb): rec_read bad magic 0x443810ec at offset=28412 The only thread I saw regarding "rec_read" stated: <><><><><> If this really happens often to you, then you have some basic problems with your

Let's keep this on the samba list and not an interactive between you and me...Also, I prefer bottom posting so my reply will be at the bottom. On Fri, 2004-03-12 at 11:54, Lee Thao wrote: > Test page from cups using Postscript driver give printout saying printer is > not license for postsrcipt. Other drivers (Generic - PCL6) produces blank > sheet with a few chars in upper left,

<rant>Every time I set up a new test Samba server, the step to "net rpc rights grant..." ALWAYS fights me tooth and nail... ALWAYS with a different error message. I've even created little scripts to run so I am not typing commands incorrectly... but NNNOOOOOO, the script to grand rights to one stink'n account always has to complain!</rant> OK, this time it is...