search for: cmerrill

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 >

...ndows printer queues. > > Thanks in advance, > Kevin > > > -----Original Message----- > > From: t.pompe@architekt-prinz.at [mailto:t.pompe@architekt-prinz.at] > > Sent: Wednesday, December 22, 2004 2:56 AM > > To: KCollins@nesbittengineering.com > > Cc: cmerrill@redhat.com; samba@lists.samba.org > > Subject: Re-2: [Samba] Samba 3.0.9 doesn't remove printjobs ? > > > > > > -------- Original Message -------- > > Subject: RE: [Samba] Samba 3.0.9 doesn't remove printjobs ? > > (21-Dez-2004 16:50) > > From:...

Is there a good how-to on getting samba to work with Iplanet LDAP ? I already installed it and started configuring from bits and pieces I could find with google, but there're still many things missing. I also found a posting that said samba schema for Iplanet5 shipped with Samba 3.0.8 isn't up to date. What would need to be changed ? Basically I'm looking for a complete walkthrough,

Hi, I'm getting confused about the role that kerberos authentication plays. What exactly is the point of using kerberos to join a samba server to an AD domain? If using kerberos still requires you to rely on winbindd for all the nsswitch stuff then what is the point? I can just as easily specify workgroup = wkgrp security =

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

Running into a lot of people upgrading to the 3.0.6 package that all of a sudden begin to experience the "Failed to verify incoming ticket!" errors etc., that are generally associated with a kerberos package incompatibility. However many of these people are running later versions of kerberos *and* reverting to a previous version of Samba appears to fix the issue. Is there something new

I know this is probably something very simple but I can't for the life of me figure out what's going on. This is a very basic setup using domain security and joined NT style in an AD running in Mixed Mode. I am *not* using winbind, all user and group accounts are represented locally in /etc/passwd and /etc/group. For the most part this is functional, from a windows client I am able

My situation is pretty simple but I'm not able to figure out this last bit (any help is greatly appreciated). I have a Samba3 server that is a standard NT member of an Active Directory. All domain user's have matching local accounts, and the domain groups that are involved also have matching local groups. Clients can set permissions within the shares but are *unable* to add or

Hi, we recently had a customer reporting that a script they run that includes an smbpasswd statement was no longer functioning after upgrading. The smbpasswd command was being used to create an account and set a password -- taking the passwd as the second argument. It looks like there has been a change in the code (possibly security related) and I was just curious what the offical reason is

It's looking like there may be a 1024 character limit for each username map? For example: account1 = user1 user2 user3 user4 user5 (etc. etc. etc.) --After a certain point user accounts are not recognized as being part of the map. Is this an intentional limitation, am I coming up against something else, has anyone else encountered this? Using a semi-ugly workaround of creating

Would anyone care to offer any theories (at this point I'll take whatever I can get) as to why the following happens: 1. w2k boxes can join the domain perfectly, users can logon, life is wonderful. 2. winXP boxes can join the domain perfectly, users authenticate fine, the screen goes blue as if it is about to load up the desktop, the system reboots. 3. Some errors upon relogging in with a

Alright, I promise I won't put in any more threads regarding this nightmare. Let me rephrase my previous question. Is there *anyone* out there who has XP Pro systems successfully logging into Samba PDC's with Netscape Directory backends? I've rebuilt all components a few times and still I get the same behavior. XP Pro authenticates, begins the login process, and then the

Some preliminary testing indicates that there may be problems in the newly released Red Hat 3.0.9 packages (not samba.org's) in regard to joining an AD as a full member (w/kerberos). This may also affect maintaining current membership in such an environment. If anyone has already upgraded and is experiencing the same or different behavior please let me know. Specifically we are seeing

Testing indicates that when a file located on a linux samba share is modified from a windows client, the creation date is modified along with the modification date. It appears that samba doesn't differentiate between the two? I know it's relatively minor in the great scheme of things, but we have seen a few complaints regarding this behavior. Any feedback would be welcome.

For whatever reason I am trying to configure the following environment and am running into trouble towards the end of things. Hopefully I am overlooking something basic, any assistance would be greatly appreciated. 1. Redhat AS 2.1 server running Netscape Directory Server 5.2 2. RHEL3 system using Samba 3.0.8 acting as a PDC integrated with the Netscape LDAP server 3. Win2k/XP clients as