similar to: Re-4: Samba 3.0.9 doesn't remove printjobs ?

That was a good hint! Yes, I've installed SP2, and it realy seems to be the Problem. Now I've checked that on a machine with SP1 - and the jobs from the same printqueue are removed correctly there! -------- Original Message -------- Subject: Re: [Samba] Samba 3.0.9 doesn't remove printjobs ? (14-Dez-2004 19:13) From: novosirj@umdnj.edu To: t.pompe@architekt-prinz.at >

Hello! I'm using samba with CUPS printing (with raw passthru) for a long time now and it worked very well. But after upgrading my samba installation from 3.0.2 to 3.0.9, the printjobs (sent from XP Workstations) aren't removed from the joblist anymore. Means: the job is printed correctly, but opening the printqueue on the XP machine still contains the job (not only mine, but jobs from

The interesting part is that PAM nor the SMB auth plugin for Apache requires you to be a member of the domain. However, the caveat with pam_smb_auth is that you have to have a unix account for every windows user you want to authenticate. I guess the behavior I'm trying to achieve is the one achieved with the Apache plugin: 1) Doesn't require you to be a member of the domain 2)

James: (Again someone correct me if I'm wrong) PAM allows local access to the Samba machine as well as authenticating Samba users. Winbind *only* allows for Samba access. This is why I chose *not* to use PAM in my setup. I don't want normal users to have local logon access to *MY* servers. <evil grin> With Winbind, you don't need PAM at all. If you're planning on

> -----Original Message----- > From: samba-bounces+kcollins=nesbittengineering.com@lists.samba.org ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Looks like it's the Virus is forging my address now... :-( Jeesh. What a waste. If the guys writing viruses would put their energies into REAL code, we'd be so much farther ahead. Later, -- Kevin L. Collins, MCSE Systems Manager

Update on the problem all: Turns out a junior administrator had used the IP addy that I was using for my test machine for another machine and didn't tell me about it. Anyway - MAJOR problem averted, but I still have a minor annoyance. I described a very long pause when accessing the SAMBA machine from Windows before, well that is still with me. I finally get what I'm looking for, but it

Jerry, I'm very sorry for this late answer. I should tweak my mailfilters (I didn't expect an answer anymore so I didn't check my samba-mailfolder) That's our situation: - I tried to revert to 3.0.20rc2 and got the error again - I installed 3.0.20 again and rebooted, and the problem went away! (I'm sure that all smbd, nmbd and winbindd daemons were killed before the

Hi, i learned a lot about cups, samba and printerdrivers the last few days and hours. I found a lot of mistakes but i can't change the following situation: I CAN NOT delete printjobs! I can connect to the printers, automatic download the driver, print, stop the printer, start the printer. Any tips, links, hints would be nice. My setup: Debian Sarge - Samba 3.0.14a - Cups 1.1.23. nss_ldap

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi, after upgrading to samba 3.0.8 (debian/unstable, i386) i too encounter similar problems as reported here: http://lists.samba.org/archive/samba/2004-November/095567.html upon logoff from a win2k(sp4) client, the profile cannot be saved and the samba logfile from the client (prinz) gives: [2004/11/26 17:57:06, 2]

A few weeks ago, I upgraded Samba 3.0.1x to 3.0.14a . After the upgrade, all completed printjobs on all 40 printers stayed in samba's print queue (they were removed from the unix-printqueue). When I installed 3.0.20rc2, everything back to normal. But since the upgrade this weekend to 3.0.20, the same thing happens again: no jobs were removed from the samba printerqueue's. Removing

Frans wrote > Did you receive any useful tips in the mean time? No, there was a greate silence. > > For one of our supported organisations I'm investigating a not able to remove print > jobs, as well Oh, I'm not alone. > So I hope you would like to share the tips, in return I could try to be of assitance > as well. Nice, I have additional questions to solve the

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [!! i've Cc'ed several fs lists, please remove when when replying !!] hi all, from time to time i do some benchmarks for several filesystems and several crypto-algorithms too, details here: http://nerdbynature.de/bench/ latest results here: http://nerdbynature.de/bench/prinz/2.6.12-rc3-mm2/bonnie.html

On Tue, 24 Jun 2003 ext3-users-request@redhat.com wrote : >Send Ext3-users mailing list submissions to > ext3-users@redhat.com > >To subscribe or unsubscribe via the World Wide Web, visit > https://www.redhat.com/mailman/listinfo/ext3-users >or, via email, send a message with subject or body 'help' to > ext3-users-request@redhat.com > >You can reach the person

I've got a Samba 2.2.7a domain with an LDAP backend. It's been working for nearly 3 months now without much bother. By the way: Great work and thanks for all of the effort! I have been missing one minor thing from the setup since I moved away from NT 4: Password Expiration. In the past I have posted questions about this on the list and I've gotten two answers: "Wait for

hi, i've made *some* benchmarks, i plan to do more. benchmarks requests welcome, e.g. "please test this...with that.." https://ephigenie.kicks-ass.net/bench/benchmark.html but only in https://ephigenie.kicks-ass.net/bench/prinz are results right now. I hope this is helpful. Thanks, Christian.

Printing from windows clients to Samba through cups works perfectly but old (finished) print jobs are piling up in the print queue for the printer on the client side. I never had this problem with the clients when the server was running RedHat 6.2 with Samba 2.2.8 and LPD. The server has been replaced with a server running a RedHat Enterprise Linux rebuild (TaoLinux). The Samba version is

Hello list, i use now Samba 3.0.2 as PDC with LDAP backend on suse sles8. With the other versions of Samba3 I hade the same problems with the lpq command. I use CUPS printing system with raw options. The clientdrivers are installed on serverside. my smb.conf in the global part printing = cups print command = lpr -r -oraw -P%p %s lpq command = lpq -P'%p'

L.S. Situation: I am running Samba 2.2.7a as my DPC in a small business network with win98/ME clients. A big Fiery printer/scanner/copier device is also part of this network. It has its own printserver. Since Win98/ME can not print to an LPD queue directly, I have setup Samba to spool the printjobs send by the clients to the Fiery server. All is working well, but there is a small problem. This

Hi, I am using Version 3.0.2a of samba on Linux 2.4.18 (suse with self-compiled samba from tarball) smb.conf: [IEPRINT] path = /home/htmprint/tmp printable = Yes print command = /home/htmprint/Programme/virtual_printer.sh %s After some weeks with some thousand printjobs generated by a program running as W2k-service the printer was no more available. I checked printing

I have a Samba 2.2.7a PDC (with an OpenLDAP backend) that seems to be giving me trouble. Here's the scoop: I have Windows 2000 Pro clients running Word 2000. Over the past several days, a lot of them have had trouble with their documents - most of the time during a save. The most critical of these failures presents the following error message when saving: "Word has lost data due to a