-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
> Did you remember to reset the signorseal registry entries?
Not needed for Samba 3.
cheers, jerry
=
Samba--- htt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Schurter wrote:
> I'm new to Kerberos. I don't understand how Samba uses the system
> keytab (/etc/krb5.keytab) when "use kerberos keytab = true".
>
> Does Samba use service specific tickets?
> What tickets does Samba add?
> Do I need a cron
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
simo wrote:
> Yes with my patch obey pam restrictions = yes let you use the account
> stack on any configuration (the session stack was already obeyed on any
> configuration).
So then this should be fixed in 3.0.24.
cheers, jerry
===
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
drweb wrote:
>
> I have Samba 3.0.23d. My log level is 5.
> Every day in each user's log I see this records:
> [2006/12/18 16:39:39, 5] smbd/uid.c:change_to_root_user(275)
> change_to_root_user: now uid=(0,0) gid=(0,0)
smbd swaps between running as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John Duthie wrote:
> I am currently testing our company's software with Vista RC-1
> and I've run into a snag I cannot Authenticate a Printer connection to a
> Samba server on a dos prompt
> I can connect to the printer using the GUI for windows printi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Samuel Briesemeister wrote:
> Hey all,
>
> I'm preparing to start development of a new version of
> 'smbstatus' that produces XML output, instead of the tabular
> data it currently produces.
...
> I've started a SourceForge project at
> http://source
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Fluffles wrote:
> Hi guys,
>
> I have one FreeBSD server which will run Samba, and one windows client.
> I want the server to have two shares; each protected with their own
> password. So once i have connected the windows client to one share, when
> i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mirceac,
> In our case the company police rules don't allow us to
> join non Windows machines to our domain.
No offense to you personally, but that is an irresponsible
IT policy and just plan stupid. You can quote me on that one.
cheers, jerry
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gerald (Jerry) Carter wrote:
> Mirceac,
>
>>> In our case the company police rules don't allow us to
>>> join non Windows machines to our domain.
>
> No offense to you personally, but that is an irresponsib
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André Jee wrote:
> So I can't do 'net groupmap modify ntgroup="Domain Admins"
> unixgroup=admin' either because there are no such group.
> If I create one my self 'net groupmap add rid=1000 ntgroup="Domain
> Admins" unixgroup=admin' it still does not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
> XFS use ACL for that.
>
> Each Default entry will provide inheritance.
>
> For applying ACL ont sub-diretcory and file, we have modified the
> file-manager of webmin for manage ACL and inheritance.
> For the rest, sam
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Julius Junghans wrote:
> Hi,
>
> ive created a new user "myuser" with his primary group "users". after adding
> him with pdbedit -a -u myuser to samba pdbedit -L doesnt list the users
> group...? how can i set it?
Create a group mapping for the 'us
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robert Bannocks wrote:
> Will samba's net ads keytab create do this for me? And
> avoid me having to run ktpass.exe on windows for each and
> every host?
Yes. There's very little to do. Just set 'use kerberos
keytab = yes' in smb.conf and then 'n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
TSZ wrote:
> When I try to run usrmgr from XP(root account) I am able to see
> users and groups names, but when I click on it I recive "The
> device attached to the system is not functioning". What is wrong
> with it? Could you help me?
Run a level
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jason Cox wrote:
> Hi all,
>
> I have recently moved to 3.0.22 on a 64 bit
> machine (SLES10) and have found that I get this problem when
> I go to join a new pc to the domain. Is there a way of
> changing the next SID issued by the serve
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jason Cox wrote:
> Jerry,
> I don't want to chenge the existing, just change the next rid
> issued. I have tried to change the sambaNextRid and Samba NextGroupRid in my
> LDAP database, but it still wants to issue the sam 3006 rid.
> Is it posibl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Niels Peuyn wrote:
> Hello,
>
> OS: FreeBSD 6.1
> Samba: 3.0.23c
>
> What kind of exit code do the "delete user script" need, to
> prevent Samba from deleting a user in tdbsam database?
>
> I'm testing Windows "User Manager for Domain" (usrmgr.exe)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Niels Peuyn wrote:
> Hello Jerry,
>
>> The delete user script only manages the Unix account. The
>> passdb entry permissions are handled by the SeAddUsersPrivilege
>> (or connecting as root). There is no current per user security
>> descriptor that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jason Haar wrote:
> Active Directory does allow you to define sites and
> Windows boxes figure out where their closest DC is from
> that information - but it looks like Samba can not?
The upcoming 3.0.24 has site support.
cheers, jerry
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ingo Steuwer wrote:
> Hello
>
> since newer versions (1.2) the cups-libs can inteprete
> the printer-ACLs in a way that a user only gets printers
> listed he is allowed to use.
>
> Samba is "bypassing" that by talking to Cups as root, not as
> the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brian Atkins wrote:
> In the samba client logs I see:
> [2007/01/12 19:56:48, 1] smbd/sesssetup.c:reply_spnego_kerberos(202)
> Failed to verify incoming ticket!
...
> KRB5.CONF:
> ==
> [libdefaults]
> default_realm = MYDOMA
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Fabio Muzzi wrote:
> Hello drweb,
>
> Saturday, November 25, 2006, 4:32:17 PM, you wrote:
>
>
> d> By command:
> d> pdbedit -r gad -G 514 -d0
> d> I cann't change primary group.
>
>
> I was looking through the list archives and found your post.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Angela Gavazzi wrote:
> Hi,
>
> I'm trying to compile samba 3.0.23d for use with ldap as backend.
>
> The system is Debian Sarge fresh installed, all updates installed, and
> openldap-2.3.27 installed from sources.
>
> I searched a lot but couldn't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stéfano Schotten wrote:
> Hi all;
>
> When I access the data hosted in that share using others mount ways
> (except the smbmount/mount.cifs/mount -t smbfs/mount -t cifs) all works
> fine, downhere a benchmark:
>
> 1) Transfer a 500 mb file:
> netcat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Angela Gavazzi wrote:
>> Also check the failure in
>> config.log to see if it is a missing library.
>
> libldap.so is missing.
>
> It's in /usr/local/ldap/lib and the path is set in ld.so.conf.
...
> Is there a better way to tell the samba compile
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rainer Shiz wrote:
> Working on a FC4 box.
> Samba 3.0.23c Source Package.
>
> I would like to know if it is possible to compile samba statically?
> I need to port it to a minimal embedded box.
>
> I tried tweaking ./configure enable-static=yes
> and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
M Azer wrote:
> since i am using "template shell = /bin/bash" in my smb.conf all of our
> users have access to the shell. how do i prevent certain users from being
> able to login using the shell
>
> getent passwd cat
> cat:*:10016:10002:cat:/home/CAD
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joshua Penix wrote:
> Is the "winbind nested groups" functionality not currently working in
> Samba 3.0.23d? The readme files seem to indicate it should be (since
> 3.0.3), but then this message by Jerry to the list...
>
> http://groups.google.com/gr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jason,
> I am running Samba as a PDC with an LDAP backend and all
> is working good, except now I am trying to set up a Samba
> Domain Member server with shares on it that will be
> authenticated via the PDC, but for some reason
> it is not working.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Peter Rindfuss wrote:
> Hi Everybody,
>
> It seems that there is a bug in the implementation of the MS Windows API
> function NetSessionEnum. I am using Windows XP against a Samba 3.023d
> domain controller.
>
> When NetSessionEnum is successful it i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Latrell Wang 王獻綱 wrote:
> Failed to parse cldap reply
Can you send me a raw sniff from Wireshark? And a level 10
debug log from 'net ads info'?
cheers, jerry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.2 (Darwin)
Comment: Using GnuPG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ralf Gross wrote:
> Hi,
>
> I'm trying out samba with winbind. The domain has >10 users and
> I'm having some problems with the wbinfo and getent programs. The
> server is domain member and running debin etch (x86_64) with
> samba-3.0.23d.
>
> id
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Latrell Wang 王獻綱 wrote:
> I looked into the source code, and have some observations:
> 1.
> I don't wrote the realm in my smb.conf, because I get
> the realm form net ads info.
> Once I set realm in the smb.conf, net ads info worked
For any 'net ads'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Fabio Muzzi wrote:
> Hello drweb,
>
> Saturday, November 25, 2006, 4:32:17 PM, you wrote:
>
>
> d> By command:
> d> pdbedit -r gad -G 514 -d0
> d> I cann't change primary group.
>
>
> I was looking through the list archives and found your post.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Hall wrote:
> On Wed, 24 Jan 2007 you wrote
>> No offense,
>
> None taken.
>
>> but making any software update or change to a production system
>> without first testing it in a test environment is an administrative
>> issue, not a software issu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Fabio Muzzi wrote:
> Hello Gerald,
>
> Monday, January 29, 2007, 2:50:54 PM, you wrote:
>
>
>>> d> pdbedit -r gad -G 514 -d0
>>> d> I cann't change primary group.
> [...]
>>> Running Samba 3.0.23d with tdbsam
>
> GJC> The primary group is based on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Pim Zandbergen wrote:
> Is anyone else seeing Vista (final) will not "connect" to
> a samba-hosted printer? I'm getting error 0x0057. I can
> connect to the port only and install a local driver, though.
> It's just that the drivers will not load
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hiro,
> [EMAIL PROTECTED] pub]# getfacl testfolder
> # file: testfolder
> # owner: [EMAIL PROTECTED]
> # group: [EMAIL PROTECTED]
> user::rwx
> mask::rwx
> mask::rwx
> other::---
Any idea why the mask listed twice here. What file system is
this?
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brian H. Nelson wrote:
> I think the message title says it all. I was attempting to do 'make
> test' against 3.0.23d and include the smbtorture4 tests from 4.0.0tp3
> (as I read somewhere to be a good idea). Is there any reason that the
> test should n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jens Nissen wrote:
> smbtorture NEGNOWAIT causes a core dump with a message "
> Abnormal server exit: multiple negprot's are not permitted".
> Is that truely by design??
Yes. That is by design currently.
cheers, jerry
=
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jens Nissen wrote:
> OK - I managed to track down the bug inside Samba,
> but I have no easy way to work around it.
> The dynamic mapping of vfs acls inside Samba does
> not seem to work. See the following sequence in posix_acls.c
> in function get
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Peter Åstrand wrote:
> I've noticed that the "net" command supports the
> PASSWD environment variable, just like smbclient does.
> However, it's not documented. Does this mean that this
> variable is deprecated, or can I trust that it will be
> aro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeremy Allison wrote:
> On Wed, Jan 31, 2007 at 04:30:32PM -0500, Rishi Srivatsavai wrote:
>> Hello All,
>>
>> I would like to add support for advertising Samba shares (browseable ones)
>> on the local network using Multicast DNS. Multicast DNS allows
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
werner maes wrote:
>
> hello
>
> a quick question: is the smbclient program a dfs-aware
> client? can it access dfs points on a microsoft
> dfs server?
Yes. I don't remember which version it was added in through.
Check the release notes. And
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sean Myers wrote:
> I've yet to see someone announce the 3rd edition of "Using
> Samba" from O'Reilly came out this week. I got it on Tuesday,
> so I guess it shipped Monday or Friday.
>
> If anyone else is as addicted as I am to having a solid
> b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
James A. Dinkel wrote:
> I'm wondering if there has been any thought into extending
> the power of a Samba4 domain controller to apply policies
> to linux members?
Group Policy support needs a Unix/Linux agent. There
are several proprietary ones in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Smith wrote:
> So now I want to add my Linux desktop and have the
> same hostname setting happen... but I can't figure out
> how to get it to work. Most of the
There's new code in the svn tree for secure DNS updates
using the machin trust acco
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Toni Casueps wrote:
> I have set a "create mask" that works well for most
> uses, but there are some directories inside my shares
> where I need to make files read-only, and my create
> mask makes every new file world-writable. Is there a way
> to sp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Folks,
I've uploaded a new release key expiring 04-Feb-2008.
Available on keyservers (ID 6568B7EA)
and at http://www.samba.org/samba/ftp/samba-pubkey.asc.
Signed by myself (D83511F6) and the previous samba-bugs
(157BC95E) key.
$ gpg --fingerprint 656
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John Drescher wrote:
> On 2/4/07, Thomas Bork <[EMAIL PROTECTED]> wrote:
>> The online documentation is not complete, see
>>
> I saw that last week when trying to find out what a
> parameter does while trying to fix the read only
> problem with word a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
==
==
== Subject: Potential Denial of Service bug in smbd
== CVE ID#: CVE-2007-0452
==
== Versions:Samba 3.0.6 - 3.0.23d (inclusive)
==
== Summary: A logic error in the deferred op
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
==
==
== Subject: Buffer overrun in NSS host lookup Winbind
== library on Solaris
== CVE ID#: CVE-2007-0453
==
== Versions:Samba 3.0.21 - 3.0.23d (inclusive) running on
==
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
==
==
== Subject: Format string bug in afsacl.so VFS plugin.
== CVE ID#: CVE-2007-0454
==
== Versions:The AFS ACL mapping VFS plugin distributed
== in Samba 3.0.6 - 3.0.23
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
==
I can say 'no' in 4 different languages.
-- Jeremy Allison
==
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Aaron Kincer wrote:
> Is this why the "Explanation of each Parameter" section
> of the on-line smb.conf documentation is jacked
> and shows only ?
I replied yesterday that I would look in to this today.
It has nothing to do with the security release
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Hochreiter wrote:
> Hi!
>
> Since the upgrade from 3.23d to 3.24 I can't log into a XP machine
> (Domain controller not found or machine account not valid ...)
>
> Samba shows:
> eb 6 09:48:03 rk01 smbd[14115]: [2007/02/06 09:48:03, 0]
> rpc_
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Hochreiter wrote:
> Hi Jerry, hi John!
>
> The error occurs on 4 machines (all Suse - 9.3 and 10.1);
> all installed with Suse rpm's and all 4 machines
> Domain Controller with ldap backend.
> The rpm's (for 10.1) are from
> ftp://ftp.suse.com
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stefan G. Weichinger wrote:
> Now my next step would be to upgrade Samba to the
> latest available rpm from sernet.de, which would
> mean a straight upgrade from 3.04 to 3.0.23d.
>
> Is this breaking anything?
> Should I take care of something speci
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jordan Russell wrote:
> In recent versions of Samba (including 3.0.24), attempting
> to rename a file to a new name that differs only in
> case appears to have no effect:
If it did ever work, it was a fluke. Renaming
files to different case on a ca
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jordan Russell wrote:
> Gerald (Jerry) Carter wrote:
>> If it did ever work, it was a fluke. Renaming
>> files to different case on a caseless filesystem
>> (or filesystem protocol) doesn't make much sense.
>
> Erm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Hall wrote:
> 'pdbedit -r -u agrotera$ -G 515', produced:
>
> Unix username:agrotera$
> NT username:
> Account Flags:[W ]
> User SID: S-1-5-21-4211105910-4270789338-3787013593-1414
> Primary Group
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Folks,
I've posted a short summary of the bug bash from yesterday
at http://wiki.samba.org/index.php/Bugzilla_Day#8_Feb_2007.
I've also updated the suggested patches for 3.0.24 at
http://www.samba.org/samba/patches/. All of these are fixes
for proble
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Hall wrote:
> OK. I'm guessing that the real problem is that
> the passdb.tdb contains an entry for Primary Group SID at all.
> With the change to group handling in v3.0.23 the Group SIDs
> should be found by UNIX UID -> UNIX GID(s) -> Windows
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Davidson wrote:
> [EMAIL PROTECTED] sbin]# net groupmap list
> [EMAIL PROTECTED] sbin]#
>
> With and LDAP backend that is working properly
> for users, what could cause that?
Until you create mappings, you won't see any reported.
ch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
James A. Dinkel wrote:
> What is the difference between %u and %U? The
> documentation says they both return the value
> of the connected username, but will they return
> different values?
%u is based on the uid of the connected userand
is only ava
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Taylor, Marc wrote:
> I was trying to lookup some things in the
> online smb.conf man page on
> http://us4.samba.org/samba/docs/man/manpages-3/smb.conf.5.html
> find that a substantial portion of it is missing.
> On my windows box using Firefox, I se
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Davidson wrote:
> I was guessing that, but it will not let me create them:
>
> [EMAIL PROTECTED] os]# net groupmap add rid=512 unixgroup=cnrg
> ntgroup="Domain Admins"
> [2007/02/09 16:45:06, 0]
> passdb/pdb_ldap.c:ldapsam_add_group_mapping_ent
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Latrell Wang 王獻綱 wrote:
> Can anyone duplicate my problem?
Have you applied DFS patch for 3.0.24 listed at
http://www.samba.org/samba/patches/?
cheers, jerry
=
Samba
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rashid,
> When Samba joins to AD, net creates 'Computer' object in
> target AD. Object 'Computer' has attributes operatingSystem
> and operatingSystemVersion, which automatically setup
> in properly value, when native Windows join to AD.
> I offer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
simo wrote:
> Gerry, can;t we just 'try' to do optional stuff and
> simply gracefully fail (ignore) if we are not admin?
I really have fought this type of behavior because it
is inconsistent. I'd rather find another way to set the
OS attributes.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim McDonough wrote:
> At some point in the past (probably 3 years now) I
> found that even when we set these attributes, at some
> point, AD would decide to overwrite them. I never got
> down to the root cause of the behavior, but it seemed
> at th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
simo wrote:
> I guess you have to do these mods after the account
> is settled down, maybe you can even try to update
> these fields using the machine account password?
> Never checked the permission on those attributes, but
> it might be interesting
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark Proehl wrote:
> Hi,
>
> try
>
> net ads join createupn=host/foundry.example.local
Or just "kinit -k foundry$"
You can only gain a TGT using a UPN or sAMAccountame.
By default, computers do not have a user printcipal name.
cheers, jerr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark Nienberg wrote:
> On a Fedora Core 4 x86_64 system the following
> packages are installed: (These are the official
> Fedora packages, not the samba.org fedora
> packages)
>
> samba.x86_64
> samba-client.x86_64
> samba-common.x86_64
> samba-comm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark Nienberg wrote:
>> The samba-common.i386 will provide the 32bit nss and
>> pam libraries. If you are using any 32bit applications
>> on your x86_64, then it does not matter.
>
> Did you mean *not* using any 32bit apps?
Yeah. Sorry. I always
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
ZIGLIO, Frediano, VF-IT wrote:
> Very silly patch. I like the english joke :)
>
> type:
>
> Index: nsswitch/nss_info_template.c
> ===
> --- nsswitch/nss_info_template.c(revision
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
ZIGLIO, Frediano, VF-IT wrote:
> In source/nsswitch/nss_info_template.c templates (lp_template_homedir
> and lp_template_shell) are not parsed for substitution.
> All other function calls pass lp_template_homedir/shell to
> talloc_sub_specified.
>
> I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Just an fyi
We should be done in the next 8 hours at the latest.
cheers, jerry
=
Samba--- http://www.samba.org
Centeris
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Heads up everyone,
In an effort to cut down on SPAM in the wiki, we are
instituting a means of approving accounts before a user
can edit content. This will still be a fairly low bar to
entry but gives a means of preventing spammers from
registering n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dave Abouav wrote:
> Any idea why the 8.3 names are so weird? Is this typical
> for Samba now?
It is by design.You might want to look at the
mangling method option in smb.conf(5).
cheers, jerry
==
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Smith wrote:
> I'll have a play with the "net groupmap modify" and "net groupmap
> delete" commands after hours and will post back my findings. Thanks for
> your help.
I'm pretty behind on email so I'm just scanning, but you
know about 'net gro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
CC'ing back to list for archives.
Paul Smith wrote:
> As you can see, everything looks fine except from the two "parts" group
> mappings and the "users" mapping:
>
> parts (S-1-5-21-3597458131-155160113-1223051555-132073) -> parts
> parts (S-1-5-21-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Victor Medina wrote:
> FYI.
>
> from the Samba How-To
>
> "The privileges that have been implemented in Samba-3.0.11 are shown
> below. It is possible, and likely, that additional privileges may be
> implemented in later releases of Samba. It is also
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Adam Tworkowski wrote:
> Hi,
>
> I am receiving the following error message on Samba domain member
> (SLES9/3.0.24). Both PDC and BDC are Samba (smbldap) (SUSE 10.1 Samba
> 3.0.22):
>
> "User nobody with invalid SID
> S-1-5-21-3838309271-3077283710-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel,
> This is really getting frustrating. The exact message
> when joining the domain is "user name could not
> be found",
When joining a Samba domain usually this means that
the machine account could not be found.but I haven't
followed thi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
> How I can remove system share ADMIN$ on samba-3.0.24?
See 'enable asu support' in smb.conf(5)
cheers, jerry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.4 (MingW32)
Comment: Using GnuPG with Mozilla - http://enig
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stephen Carville wrote:
> Not for all users but for some.
>
> I'm using samba 3.0.20 running on Fedora Core 3. Security = ADS,
> winbind works and getent passwd returns local unix accounts plus the
> domain accounts as expected.
>
> It also returns
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
==
I'm sure there were some nice orcs in Mordor.
-- Don Marti
==
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
ZIGLIO, Frediano, VF-IT wrote:
> I want to thanks for improvements in winbindd. 3.0.25 is much faster.
> Now I can log in my machine very fast.
>
> I noted however that groups commands did not improve that much.
> I used tcpdump to log ldap activity.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alexander Menk wrote:
> Hello!
>
> I've integrated samba into an existing NT Domain managed
> by a windows 2003 server. Recently I'm have trouble
> to use the "groups" command get the group of domain
> users. It worked well for weeks (but perhaps aft
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gerald (Jerry) Carter wrote:
> ZIGLIO, Frediano, VF-IT wrote:
>> In source/nsswitch/nss_info_template.c templates (lp_template_homedir
>> and lp_template_shell) are not parsed for substitution.
>> All other function calls pas
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Harald Strack wrote:
> The worker is simple too busy... Is there a
> possibility to fork multiple workers
> for a domain trust? E.g. sth. like this in
So you basically want the apache prefork model to be able
to have a poll of children to answer app
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Volker Lendecke wrote:
> My guess is that your are hit by us not yet having a
> negative cache for idmapping. With 3.0.25 the id mapping
> has been rewritten, and it does include a negative cache.
> Maybe you could try the just released pre1 (not yet
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Harald Strack wrote:
> Hi Jerry & Volker,
>
> thank you for your tips!
>
> First I want to explain you my initial problem on Detail, so that you
> see what calls are causing timeouts when they appear in a huge amount.
>
> The following log output fr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark wrote:
> So after saying all of that, I'm having trouble creating a local group,
> local to the samba server. I'm getting the following error.
>
> [EMAIL PROTECTED] samba]# net rpc group add "DesktopSupport" -L
> -UAdministrator
> Password:
> a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jarle Thorsen wrote:
> I have a printer connected to a linuxbox running Samba and Cups. I have
> followed the instructions in the Samba-HOWTO to export the printerdriver a
> a machine running Windows XP. When I try to print to the printer Windows
> say
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rainer Weber wrote:
> Sorry,
> after the user mapping the nt_user_token is
>
> [2007/02/02 15:21:17, 10] auth/auth_util.c:debug_nt_user_token(454)
> NT user token of user S-1-22-1-10002
> contains 6 SIDs
> SID[ 0]: S-1-22-1-10002
> SID[ 1]:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alexander Menk wrote:
>
>> Seems like the DC dropping what it thinks are
>> idle connections. We should reconnect. Could you test
>> 3.0.25pre1 and let me know if that behaves any better?
>
> It's complicated for me to test this version on the same
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Schurter wrote:
> I'm using Debian Sid, and it seems like Iceweasel (aka Firefox) has been
> crashing a lot lately with "Bus Error" printed to stdout when it dies.
>
> I use mono/.net and python, so my C/C++ debugging skills are very
> lacking
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jason Baker wrote:
> I'm know enough to change the SID, but should I change
> the ROOT SID to S-1-5-21-1194936901-2368177035-684874509-0?
> The UNIX UID # for Root is 0. Could this also explain why I cannot
> join a machine to the domain using the cl
701 - 800 of 4112 matches
Mail list logo
