-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andrew Bartlett wrote:
>> One of our devs at Centeris has code for performing
>> secure, dynamic DNS registration during domain join
>> that will be going into Samba 3.0.24. I'm currently
>> working on integrating it into the SAMBA_3_0 tree.
>
> Does
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mike Cauble wrote:
> I currently have in my slapd.conf:
>
> index sambaSID eq
>
> the release notes for 3.0.23 say I need
>
> index sambaSID sub
> can I use
> index sambaSID eq,sub
Yes. Make sure
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
FYI
Everything is back up and functioning now. Thanks to Scott
at JumpDomain (http://jumpdomain.com/) for doing the hardware
swap (and donating the bandwidth).
cheers, jerry
=
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
zdennis wrote:
> I got this error when kicking out my first response.
> I don't know if I should ignore this, or if this is
> an issue that is affected by the samba.org sites
> being down... but just in case..
It was a bad subscription and has been r
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Trimble, Ronald D wrote:
> I tried ext3 on another server... a fresh install of
> SUSE Linux 10.1. Another panic. Here are the details...
This has got to be the static group list bug. Do you
have users in more that say 20 - 25 groups in AD ?
Could
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Henrik Zagerholm wrote:
> Interesting! Looking forward to the implementation.
>
> Is there anyway to accomplish this in the meantime?
> E.g using nsupdate or similar? (I've tried nsupdate
> but never got it to work with a Windows DNS. I
> believe its
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Folks,
Just a heads up for everyone. We are aware of the problem
and are continuing to work on resolving it.
cheers, jerry
=
Samba--- http:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Henrik Zagerholm wrote:
> Hi list,
>
> I'm not sure if this is the right place to ask this
> question but I guess someone has probably don this before.
>
> I wonder how I can easily register my samba box's in
> my Windows DNS?
>
> It is quite easy
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gerard Seibert wrote:
> I am new at setting up Samba3. I had heard that the
> name share name is supposed to be limited to 8
> characters or less; i.e., [home] or [configs], etc.
> Is this correct, or can the name be longer? Also,
> are there any spe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Beschorner Daniel wrote:
> Can anyone confirm that SID -> name lookup with
> a trusted domain is broken?
Works fine for a Samba DC trusted Windows 2003 AD:
$ wbinfo -m
AQUA
COLOR
$ wbinfo -n 'COLOR\gcarter'
S-1-5-21-3493585492-4029240144-3226775320-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Guillermo Gutierrez wrote:
> (Blond-moment question) I take it then, that this
> bug doesn't apply to version 3.0.23?
Actually, you are the second person to ask me this. :-)
I thought that since both the security and release
announcement can from m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Don Meyer wrote:
> My question though is what are the ramifications of
> a similar situation: Where the CNAME might be
> dynamically moved to point to another system's base
> IP address in the case of a transfer of service/fail-over.
> Does this se
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Huntley wrote:
> netbios aliases = in your smb.conf
>
> Then setup the cname in DNS and point it to the correct
> A record.
HmmmThis would work for NTLM but I don;t see how it
would work for Krb5. The client has to request a service
ti
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gerald (Jerry) Carter wrote:
> ==
> ==
> == Subject: Memory exhaustion DoS against smbd
> == CVE ID#: CAN-2006-1059
> ==
> == Versions:Samba Samba 3.0.1 -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
==
==
== Subject: Memory exhaustion DoS against smbd
== CVE ID#: CAN-2006-1059
==
== Versions:Samba Samba 3.0.1 - 3.0.22 (inclusive)
==
== Summary: smbd may allow internal structur
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
==
You are standing in an open field west
of a white house, with a board front door.
There is a small mailbox here.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mann, Roy (RGMR) wrote:
> I have a RedHat Enterprise 3 server running SAMBA 3.0.10. The server
> has been joined to the Active Directory forest using its fully qualified
> domain name.
> Windows clients can successfully map drives using that fully
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Vogt wrote:
> On Mo, Juli 10, 2006 13:06, [EMAIL PROTECTED] wrote:
>> Hi,
>> I want to insert a static WINS entry into wins.dat.
>> How do I write an entry for 2 servers (dc01, dc02) for domain DCDOMAIN?
>
> Put them in /etc/samba/lmhosts on yo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Steve A wrote:
> As the second edition is a bit long in the tooth, I wrote
> to O'Reilly, and they said the 3rd edition of "Using Samba"
> is scheduled for release in November.
Yeah. I have just a few more chapters to finish up. I
guess since th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mariano Sokal wrote:
>>> Yes, we have 2 DC (darthsith and darthvader ;) )
>
>> Could be a replication issue. Sometimes the krb5 libs
>> don't always communicate with the same DC as smbd.
>> We're trying to fix this some in 3.0.23.
>
> So there´s no
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mariano Sokal wrote:
>> get_service_ticket: kerberos_kinit_password
> [EMAIL PROTECTED]@SYSTEMMASTER.COM.AR failed:
>> Preauthentication failed
>
>> Do you have more than one DC? I'm cleaning up this code some
>> right now actually. The failure is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eric Evans wrote:
> The documentation always refers to it in /etc/sama/.
> Alright, that does it, from now on I'm making all
> my smb.conf changes in BOTH places
:-) How about just running 'smbd -b | grep CONFIG' to
find out which one Samba is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mariano Sokal wrote:
> get_service_ticket: kerberos_kinit_password [EMAIL
> PROTECTED]@SYSTEMMASTER.COM.AR failed:
> Preauthentication failed
Do you have more than one DC? I'm cleaning up this code some
right now actually. The failure is coming w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alan Gibson wrote:
> Samba 3 does indeed use /etc/samba/smb.conf.
Not by default. When compiling with no tweaks to configure,
the default location is stil /usr/local/samba/lib/. /etc/samba/
is a packaging choice.
cheers, jerry
==
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
malcolm wrote
:
> My question: since I cannot be the only one to
> encounter such behaviour (google verifies that I am
> not alone), why don't the samba developers either
> fix this bug, or disable printing over samba and
> recommend the internet sol
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
andy liebman wrote:
> Note that rpc.statd also seems to be out of control.
> Don't know if it is related.
Are you re-exporting nfs file systems by chance?
ok. Steps to trouble shoot.
* Figure out what IP address is associated with that
smbd pro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Trimble, Ronald D wrote:
> Deleting that file seemed to have done the
> trick. What does that file do?
Cache information about users and groups in the domain.
> What made you suspect this?
The call to wcache_flush_cache(). I've seen this backtrac
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Volker Lendecke wrote:
> On Fri, Jul 07, 2006 at 10:17:13AM -0400, Trimble, Ronald D wrote:
>
>> ReiserFS is a problem? It's the default. I
>> would imagine you would be seeing tons of complaints
>> if it was due to the fs, don't you agree?
>
> Jus
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Trimble, Ronald D wrote:
> I have a server that has a smb_panic every time
> I start/restart the winbind service. How do I go about
> fixing this? Here is the output from the winbind log file.
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Masopust, Christian wrote:
> with the supplied Makefile(.in) I'm not able to make pam_winbind.so
> on Solaris (8 and 9).
>
> So i had a look at the Makefile and found out that there seem's to
> be some things missing :-))
Was fixed just after re
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alan Gibson wrote:
> for instance, will the following allow user2 to write to [share]?
>
> [share]
> read only = yes
> valid users = user1 user2
> read list = user1
> write list = user2
>
> thanks in advance for any info...
Yes. user2 will have wr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John Paul wrote:
> Greetings,
>
> I have recently installed SuSE 10 on a Dell PowerEdge 1800. Everything is up
> to date. I downloaded Samba 3.0.22, ran configure (with no options), make,
> and make install. I created a very skeleton smb.conf to test
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bruno,
> My samba print server joined sucessfully to ADS domain
> is very slow. 100% CPU usage.
>
> I did a strace in smbd process:
>
> # strace -p 4519 -cfqrT
> % time seconds usecs/call callserrors syscall
> -- --- --
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nguyen Anh Phu wrote:
> Hi all,
>
> I'm using Samba 3.0.14a on Debian Sarge. According to
> Samba HOWTO, I've set syslog = 0 to make extd_audit
> module writes to log.smbd instead of syslog, but in
> log.smbd only 1 line about creating new
> folder w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nanni X wrote:
> Ok Jerry,
>
> now the Last Question: my LinuxSambaBox has joined
> the domain or not??
if 'net ads testjoin' reports success it has joined,
although you might have some problems with DES
session keys.
cheers, jerry
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Doug VanLeuven wrote:
>> For the record, this is what WinXP does as well.
>> You cannot join a WinXP box to a domain using a non-admin
>> account if the client's FQDN is outside the AD domain.
>>
>> I agree this is a change from previous Samba version
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Henrik Zagerholm wrote:
>
> Just got a little curious on the "non-admin" part.
> I used the domain bultin Administrator account to join
> the domain. I know this account is member of both
> domain admin and enterprise admins.
>
> BTW Does this accou
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Henrik,
> You were right. ( as usual.. )
> I had the wrong FQDN on the samba server.
> After reconfiguring my network and I got the FQDN back
> from 'hostname' the join worked as planned.
For the record, this is what WinXP does as well.
You cannot j
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Henrik Zagerholm wrote:
> Hi list,
>
> I get this error when joining my samba server
> to the domain.
>
> Failed to set servicePrincipalNames. Only NTLM authentication
> will be possible. Please ensure that the DNS domain of
> this server matches th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Steve A wrote:
> The "Samba-3 by Example" instructs you to make a mapping,
> "root = Administrator". Is this absolutely necessary?
No. Not necessary. Read up on Samba's privilege model.
cheers, jerry
===
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rajesh Prabhu wrote:
> Hi
>
> Is there a way to have the security level
> in smb.conf as user and supress the
> authentication? or is there a way to read the
> authentication automatically from some file so
> that, my security mode remains at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Markus Fischer wrote:
> My first take was to map a windows group to a unix
> group. I tried
> net groupmap add ntgroup=WebDevelopment unixgroup=www-data
> but it didn't really changed anything. I could see my
> mapping with "groupmap list" but per
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
> Hi
>
> 3.0.23rc3 pam_winbind on SLES9/i386 with the provided RPMs doesn't work:
>
>PAM unable to resolve symbol: pam_sm_authenticate
>PAM unable to resolve symbol: pam_sm_setcred
>
> Is this a compile problem ? SLE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
J. Pilfold-Bagwell wrote:
> Hi All,
>
> I've found a script for migrating posix accounts
> to LDAP but does anyone know of a script for
> migrating tdbsam to LDAP?
See pdbedit -i ... -e
cheers, jerry
-BEGIN PGP SIGNATURE-
Version:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nanni X wrote:
> Hi people,
> I'm trying to join a linux SuSE 10.0+samba 3.0.20 box to an ADS-Win2003
> domain.
>
> As I configured /etc/krb5.conf, /etc/nsswitch.conf and
> /etc/samba/smb.conf, I try to join the ADS with:
>
> root # net ads join -U
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Komal Shah wrote:
>> I'd suggest reading up on Samba configuration
>> a little bit more. Look how details on how to
>> setup a guest accessible server using 'map to guest'
>> and 'username map'
>
> If I am correct guest directive is only applicable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
d.arun321 wrote:
> Thanks Jerry -- for your assistance.
>
> The solution was precise but i am facing
> an authentication issue. When I use the "use
> security = user" in the smb.conf then its promoting
> for a username and password.
>
> Is there any
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
==
> How do you set 'hide unreadable = yes' via the standard
> RPC calls? We need more than pure Win32 allows.
RegSetValue() :-)
-- sam
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stephen Boyd wrote:
> I'm the person who posted the bug about 2.2 kernels. I got
> past the compile errors but now smbd aborts as soon
> as you try to start it. That is why I am asking
> about minimum gcc & glib versions.
There's no documented. But
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stephen Boyd wrote:
> I have been unable to find anything that will tell
> me what the minimum system requirements are to
> build Samba 3.22. What version of gcc,
> glibc, etc. Can anyone tell me what they are?
It's pretty portable. I think there'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marco D'Ettorre wrote:
> I think that I should run an external script to create
> the LDAP entry before Samba can do the operation. But how
> can I do this? The script in "add machine script"
> smb.conf key is not executed during this operation,
> on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Steffen Kolbe wrote:
>>> Username DOMAIN\XP-CLIENT-NAME$ is invalid on this system
>>>
>> You don't seen to be using winbindd so the machine accounts
>> are not seen via nss.
>>
> What should I change? ..and how?
You can potentially change you nss_l
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Vitaly Protsko wrote:
> Hi!
>
> I have a problem with access to svcctl functions from MMC.
> It quickly (since 23pre1) shows list of services and
> statuses, but any operation ends with "Access denied".
Works fine for me. Sounds like you user is no
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
rich wrote:
> Hi when using samba version Version 2.0.5a (I didn't
> compile) I never had to explicitly set up
> samba users with smbpasswd -a. Since upgrading to
> version 3.0.22 I now have to add each user otherwise
> I get the following in the log
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Steffen Kolbe wrote:
> Can anybody tell me please, what isn't correct?
> What should I change in config?
>
> /var/samba/log/log.XP-CLIENT-IP:
>
> [2006/06/22 08:24:54, 1] smbd/sesssetup.c:reply_spnego_kerberos(303)
> Username DOMAIN\XP-CLIENT-NAME$
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
d.arun321 wrote:
> I am able to get print-outs and also able to Cancel, Pause
> and Resume the print-jobs but only when I issue them via
> a Win-2K client.
>
> If I try to manage the printing via Win-XP, I am able to only
> give a print-command .
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dan wrote:
> I see in the documentation that samba can use a
> mysql backend. I see an example for users tables but I am
> curious as to where it would store computer accounts
> and group accounts. Has anyone setup samba using
> mysql as a backend?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nicki Messerschmidt, Linksystem Muenchen GmbH wrote:
> We only have one printer but this one has several paper
> feeders. In cups I have configured three printers (one
> for each feeder). Using the cups driver I have three
> printers with three print
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jérôme Warnier wrote:
> In Debian Sarge (and I guess also with these packages), as explained
> here above, kernel oplocks are disabled by default at build time to make
> it work on 2.2 kernels. On Etch and above, 2.2 kernels are no longer
> officially
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stefan Pfetzing wrote:
> Hi,
>
> 2006/6/14, Gerald (Jerry) Carter <[EMAIL PROTECTED]>:
>> Stefan Pfetzing wrote:
>> > Currently its not clear to me whether its possible
>> > to do nested groups with samba at all
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 21 Jun 2006, Jér Warnier wrote:
> So the kernel oplocks are not activated by default? If not, may I
> request you do it? There are little chances someone willing to use the
> latest Samba packages for his Sarge is still running a 2.2 kernel.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jérôme Warnier wrote:
>> Any chance you could try the debs at
>> http://download.samba.org/samba/ftp/Binary_Packages/Debian/
>> ?
>
> Well, could you tell me what they change over the
> official packages?
There are newer :-) Check the WHATSNEW.txt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nicki Messerschmidt, Linksystem Muenchen GmbH wrote
:
> The problem is that I don't quite know how to
> upload the cups driver via the windows gui. It is not
> as easy as using the apw...
Why use the cups driver ? You can use a Win32 driver
on a raw
Daniel Carmo Olops wrote:
> - What's about the --with-fhs option? In raw words,
> does it configures Samba to install configuration
> files in /etc/, var files in /var, and so on?
Basically, but i would suggest looking at the
RHEL spec file in packaging for an example
of how to use it.
> - What
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jérôme Warnier wrote:
> I finally found out the following logs in my log.winbind:
> [2006/06/18 06:26:38, 0] lib/fault.c:fault_report(36)
> ===
> [2006/06/18 06:26:38, 0] lib/fault.c:fault_
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tom Haerens wrote:
> Hi,
>
> A couple of weeks ago, we moved from a Samba 2.2x to a
> 3.0.x server. Everything works fine, except our svn.
What is the 'x' in 3.0.x? Out of curiousity, have you
tested against 3.0.23rc2?
> The smb.conf looks like t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Logan,
> However, I've noticed something odd: /etc/samba/smbpasswd
> on 2.2.7 doesn't contain any RIDs or SIDs. And yet, if I run
> rpcclient and do "lookupnames lshaw" against the 2.x server,
> I can see that my (lshaw's) SID is formed of the domai
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nicki Messerschmidt, Linksystem Muenchen GmbH wrote:
> I have a strange problem with samba (3.0.23), cups (1.2.1),
> windows 2k (all patches up2date) and the printer drivers
> (cups 5, cups 6). I setup samba to share the printers
> configured in cups
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
malcolm wrote:
> When I print from windows, which I can from
> various situations --- i.e. Firefox, Excel, etc, printing
> is very slow (up to 2 minutes).
>
> But I cannot print at all from WinWord.
Did you initialize the printer data as outlined
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stephen Boyd wrote:
>> You could open a bug report. Is that a linux 2.2 kernel ?
>>
>
> It is linux 2.2.13. How do I open a bug report?
Go to https://bugzilla.samba.org/ and follow the link to "New"
cheers, jerry
-BEGIN PGP SIGNATURE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
> I am trying to build samba 3.0.22 on an older Slackware system.
>
> gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)
>
> The error I'm getting is
>
> smbd/statvfs.c: In function `linux_statvfs': smbd/statvfs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Benoit Callebaut wrote:
> Hello,
> I have set up a samba server 3.1.2.
> I want to run it as a PDC.
> Final target is to use it with LDAP and Kerberos.
You should be using the production releases here. Trunk
(a.k.a v3.1.x) is for experiments and on g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andres Tarallo wrote:
> A good place to find up to date packages for solaris is
> http://www.sunfreeware.com
If you don't need ADS support, you can get pkg files
from download.samba.org as well.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2 (GN
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stefan Pfetzing wrote:
> Hello List,
>
> I'm evaluating a migration from Windows NT 4.0
> to Samba 3.0.
>
> Currently its not clear to me whether its possible
> to do nested groups with samba at all. AFAIK its
> possible to have Samba resolve neste
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ryan Suarez wrote:
> 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-m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ryan Steele wrote:
> I'm not sure. The production environment still experiences
> this issue, it's just that I have trouble duplicating
> it in a test environment. However, the traffic in that
> production environment is significantly heavier so it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ryan,
> A good suggestion, but unfortunately the smbd
> daemon still continues to run on the server end. However,
> I've run across the problem of no longer being able
> to duplicate the problem consistently. I'm not sure
> what exactly causes some
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Edmundo Valle Neto wrote:
> I didnt found any explanation on WHY this is
> needed. It is really needed?
Two reasons:
(a) If you want to support NTLM authentication via
pam_winbind or ntlm_auth
(b) supported trusted users & groups from other
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Henrik Zagerholm wrote:
> Hi list,
>
> I need to be able to enumerate all users on a client machine.
> I've been using NET RPC USER/GROUP command but it doesn't
> display some builtin users/groups like NT INSTANCE\SYSTEM
> (S-1-5-18) and Everyone (S-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Craig Jackson wrote:
> Hi,
>
> Everything I can find about using the ldapsam
> backend seems to imply that samba will be used
> as a domain controller. Is it possible to use
> ldapsam as the backend and have just a user level
> security workgroup?
Y
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
==
It was during the jra vs. vl code reformatting wars.
Somewhere around the time of the 80 column massacre.
-- coffeedude
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Giulio Orsero wrote:
> https://bugzilla.samba.org/show_bug.cgi?id=3794
>
> Basically spnego fails with vista and you have somehow force to downgrade to
> ntlmssp.
>
> To samba devels:
> I see the bug submitter sent 2 emails to samba-technical that we
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Collins, Kevin wrote:
> So my question is this: Can I bring up a Windows 2k3
> machine as a member server in the Samba domain. Promote it
> to become an AD Domain Controller in mixed mode - retaining
> the domain SID, user and machine accounts and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Beast wrote:
> Henrik Zagerholm wrote:
>> Hi list and sorry if this is not a specific Samba issue.
>>
>> I just wonder if it is possible to determine if a SID belongs to a
>> User or a Group?
>>
> No you can't. Its same as uid vs gid number.
You can't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
S. J. van Harmelen wrote:
> Thanks for your help! I just couldn't seem to find
> any useful parameters. Can you tell me where I
> can lookup (in documentation) what this parameter does
> and maybe what more acl parameters I could use?
The smb.conf m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
S. J. van Harmelen wrote:
> What goes wrong is that when a user creates a file,
> the Admin can't change the ACL but get's a access
> denied error.
Set these in the shares:
dos filemode = yes
acl group control = yes
cheers, jerry
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wagener, Harald wrote:
> [2006/06/09 13:14:28, 5] auth/auth_util.c:debug_unix_user_token(454)
> UNIX token of user 105593
> Primary group is 10 and contains 2 supplementary groups
> Group[ 0]: 10
> Group[ 1]: 100492
> [snip]
>
> so,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Cameron wrote:
> Using Samba 3.0.22 as a domain controller, Windows XP Pro
> as the client. When a user changes their
> password, all their certificates stop working.
>
> Found:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;331333
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Christopher Johnson wrote:
> All -
>
> While trying to copy a directory containing a
> large number of files (~600 1-5 mb files ) from
> my samba server to a client machine ( either
> mac or windows ) my samba server crashes
> paralyzing my server m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Giulio Orsero wrote:
> So, is there a way to have smbclient wait a bit
> longer before giving up? I'd like to avoid having
> to do pings before calling smbclient or calling
> smbclient multiple times.
You could add a retry loop in smbclient. But yo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gerald (Jerry) Carter wrote:
> wpc wrote:
>>> i get a big problem with authentication popups (with
>>> squid) when the connection to my AD dies.
>>>
>>> what options do i have to ensure less downtime when my
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
wpc wrote:
> i get a big problem with authentication popups (with
> squid) when the connection to my AD dies.
>
> what options do i have to ensure less downtime when my
> AD backend dies ?
> i would like something that for example caches the
> users
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Wood wrote:
> This patch fixes all the incorrect uses of "then" that I could
> find on the whole SAMBA_4_0 branch.
>
> i.e. it is relative to
> svn://svnanon.samba.org/samba/branches/SAMBA_4_0 at revision
> 16046.
Hey Michael,
I you could re
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Aurélien Bras wrote:
> Hi,
>
> All is working fine, I just wondering why if I delete
> my tickets kerberos, "net ads join " is still
> working, kerberos isn't needed ??
>
> I typed these command :
>
> net ads leave
> kinit destroy
>
> and "net ads
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gautier, B (Bob) wrote:
> Looks like it might be: the DS_DOMAIN_IN_FOREST flag
> has been dropped from the rpccli_ds_enum_domain_trusts
> call in winbindd_ads.c (but not from the call in
> rpcclient/cmd_ds.c, where the symbolic value is not
> used, b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Warren Beldad wrote:
> I have created a user with a password of 15 characters...
> then disable:
> -bash-3.00# smbpasswd -d user1
> Disabled user user1.
>
> Enable:
> -bash-3.00# smbpasswd -e user1
> New SMB password:
>
> Why is this happening? Is t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Carlos Eduardo Pedroza Santiviago wrote:
> Hi,
>
> I'd like to know if samba offers any way to audit
> user/group management tasks. I need to audit those events.
> AFAIK, i can change the smbldap-tools scripts to do some
> debugging, but doing it fro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ephi Dror wrote:
> Hi,
>
> Regarding "change share command" option in smb.conf.
>
> I am not using it by I am wondering how it can ever
> work if input parameters don't include existing share name.
> I mean if you want to change existing share n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark Johnson wrote:
> I think something is broken in 23rc1 with LDAP as
> the backend. "testparm" did not reveal any issues with
> my config file, but all I get is hundreds of messages
> in the smbd.log file that it couldn't connect to
> the LDAP se
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
> I have a problem with my printing setup of a windows XP
> client with a samba server.
>
> The windows driver seems to use different ways of
> smb/printer communication for printing in normal/duplex
> mode and for printing
901 - 1000 of 4112 matches
Mail list logo
