-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matthias Schündehütte wrote:
> Hi Jerry,
>
> On 2006-08-23 21:10:56 +0200, "Gerald (Jerry) Carter" <[EMAIL PROTECTED]>
> said:
>
>> In that case, would you test this patch against 3.0.23b?
>> http://samba.o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brian D. McGrew wrote:
> I'm also seeing the following in my syslog when I try
> and map from a Windows machine to one of my samba shares:
...
> Aug 24 07:35:49 mustang smbd[19060]: create_local_nt_token: Failed to
> create BUILTIN\Administrators gr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brian D. McGrew wrote:
> I'm not sure that the problem is with net ads join but I'm in desperate
> need of help either way.
>
> Using smb Version 3.0.23a-1.fc4.1
>
> I do a net ads join I get the below error:
>
> [EMAIL PROTECTED] tmp]# net ads join
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hansjörg Maurer wrote:
> the Patch compiles and installs fine here.
...
> But we still have the behavior described in the
> thread "New approach to the valid user fix"
Yup. I haven't forgotten. Just still trying to figure
out a clean fix for that.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Rankin wrote:
> Patch went fine...
>
> [EMAIL PROTECTED] source]$
> ./configure --prefix=/usr --infodir=/usr/share --mandir=/usr/share --with-co
> nfigdir=/etc/samba
>
> ...went fine... But, it looks like a compile error
> in rpc_parse/pa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Shapiro wrote:
> What can we do if we have the 3.0.0.23c
> version already as far as the patch goes?
I doubt any one has the full patch. This includes
some changes I made last night at 9pm GMT-6 as well
as all the other svn commits to the SAM
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matthias Schündehütte wrote:
> Hi Jerry,
>
> On 2006-08-21 23:09:05 +0200, "Gerald (Jerry) Carter" <[EMAIL PROTECTED]>
> said:
>
>> Does your username map use a ! to stop the parsing.
>> See the man page fo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matt London wrote:
> Hi,
>
> We've recently upgraded a network from Win2k to 2k3 SBS.
> We were using samba with security = domain (which
> I believe stopped working - I was on vacation at the
> time the upgrade was done) and are now using security =
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
M. D. Parker wrote:
> -Original Message-
> From: M. D. Parker [mailto:[EMAIL PROTECTED]
> Sent: Thursday, August 10, 2006 9:02 AM
> To: 'samba@lists.samba.org'
> Subject: HELP -- Problem with access list on samba 3.0.23b but not on
> 3.0.20c P
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
ML Samba wrote:
>> > I'm trying to upgrade from Samba 3.0.14a to 3.0.23b. Using the exact
>> > same config file that I did in the older version, and using the exact
>> > same share directory and file permissions as I did with the old
>> > version, a s
nded Attributes data.
* Fix nmbd crashes caused by miscalculation in pushing
announcements.
o Gerald (Jerry) Carter <[EMAIL PROTECTED]>
* RHEL4 and Fedora packaging updates.
* Remove RID algorithm support for unmapped users and groups
when using an smbpasswd backend.
* Extend
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
dovecot auth wrote:
> request_len_recv: Invalid request size received: 1840
Make sure you upgrade the nss_winbind.so lib as well and restart
all impacted process.
cheers, jerry
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
J J Urich wrote:
> Checked http://www.software.hp.com and did a
> search for kerberos, and turns out HP has a new
> client and server version available for 11.23.
...
> Installed it, rebuild samba and now net ads join works
> on a test hpux system.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stephen Carville wrote:
> I am using Samba 3.0.20a with winbindd on FC3 and all
> the shares except one are working. I keep getting a
> permison denied error for non-local users in certain
> directories.
...
> And I have mapping between Windows and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
werner maes wrote:
>
> hello
>
> when I try to install samba 3.0.23b I get this error
>
> error: Failed dependencies:
> perl(Unicode::MapUTF8) is needed by samba-3.0.23b-1
>
> is this perl module required since 3.0.23b?
What platform ?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
User 1 wrote:
> Dear Expert,
>
> I need to log user's activities (ie. Create, Delete, remove
> .. etc) .. I have already configured /etc/samba/smb.conf to:
Look at the vfs_full_audit.so plugin.
ciao, jerry
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andrew Bartlett wrote:
> On Tue, 2006-08-22 at 17:19 -0700, Chuck Forsberg WA7KGX N2469R wrote:
>> Is there a way to force the Samba server to ignore
>> mounted CIFS file systems? I can't see anything
>> in the smb.conf documetation to do this general
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Poil wrote:
> Hello,
> My PDC is working but I have some errors on my log, I'm searching since
> some days but I cannot find why.
>
> In log.smbd I have
> [2006/08/22 16:30:22, 0] lib/util_sock.c:get_peer_addr(1229)
> getpeername failed. Error was No
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
J J Urich wrote:
> Have been running samba successfully authenticating to a windows 2003
> domain since 3.0.1. Starting in 3.0.23 and 3.0.23b I can't do a "net
> ads join" on a HPUX itanium server running 11.23 ia64. I can kinit just
> fine w/ this u
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Shapiro wrote:
> What do you put in the file to map an ad user to a unix
> user? If I have an ad user MYDOMAIN+joe, do I put
> in user.map file:
>
joe = MYDOMAIN+joe
If you are not runnign winbindd and using 'security = ads',
you need
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robert Mortimer wrote:
>> Henrik Zagerholm wrote:
>>> If I look at the security tab in windows I always
>>> see the Everyone entry. I think this is because the POSIX "other"
>>> entry in the FS on the debian box, correct?
>>>
>>> Can I remove it? If so
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joel Franco wrote:
> I think the release notes for the 3.0.23b has
> the response:
W00t! Someone did release the release notes ! :-)
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.4 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigma
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Shapiro wrote:
> I need to nfs share the samba home directory of a
> user on the samba server over to another server,
> but the uid it is giving is for example
> 10 instead of the standard uid for the user on all
> the other servers. How
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matt Sellers wrote:
> Hello again :-)
>
> So my understanding is that somehow the pam library throws this flag to
> pam_winbind for some reason thus even if the account is not expired. I do
> not have direct access to the DC that we are doing authent
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Christian,
> I have been trying for hours to make a Windows 2003
> Server R2 SP1 join a Samba PDC.
> It does not work, and I simply get an error "Invalid
> Parameter" on the 2003 side.
Check the smbd logs (at level 10) and see why that error
code i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Davies, Gareth wrote:
> I have a problem configuring my install of samba on solaris, version 3.0.22
> which was downloaded from the link below. It appears to install correctly
> when running the 'pkgadd -d ' command, but i wish to be able to
> confi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Henrik Zagerholm wrote:
> If I look at the security tab in windows I always
> see the Everyone entry. I think this is because the POSIX "other"
> entry in the FS on the debian box, correct?
>
> Can I remove it? If so how?
Can't remove it. That's by
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jörg Horchler wrote:
> 'winbind nss info' from 'sfu' to 'rfc2307' everything
> worked as expected in the first look. Winbind resolved
> our Windows-Users and groups correct. (wbinfo and
> getent work perfect!)
>
> But when I try to connect to a shar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matthias Schündehütte wrote:
> Ticket name is [EMAIL PROTECTED]
> Mapped user WW004\SchuendeMa to matthias
> Mapped user WW004\matthias to smb
Does your username map use a ! to stop the parsing.
See the man page for details.
cheers, jerry
==
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeremy Allison wrote:
>> *** glibc detected *** winbindd: free(): invalid pointer: 0x0018edb0 ***
>> === Backtrace: =
>> /lib/libc.so.6[0xa72124]
>> /lib/libc.so.6(__libc_free+0x77)[0xa7265f]
>> /lib/libcom_err.so.2(remove_error_table+0x4b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Schlomo Schapiro wrote:
> Hi,
>
> I installed a fresh server (SLES9 SP3) with Samba
> 3.0.23b as an ADS member server.
>
> It all seems to work fine, but it doesn't create
> the builtin accounts (only complains about it).
The Builtin group support
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
david rankin wrote:
> Any headway on incorporating the patches into a 3.0.23c release that
> will help all of us that are running stand-along, no-winbind, simple
> smbpasswd setups?? I was never able to get the patches to apply properly
> and my manu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Edmundo Valle Neto wrote:
> Sorry, I made a little confusion (as the printed version of TOSHARG is
> in the 2nd edition too), Using Samba 2nd Edition covers Samba 2, so
> everything will be new.
>
> I readed "Using Samba 2nd edition" from O'Reilly and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Edmundo Valle Neto wrote:
> Hi.
>
>Some time ago I bought the first edition, and
> followed some changes reading the online version of
> the documentation (but I really like to read books
> as books). Can you point what will be included in the 3r
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Shawn Wilson wrote:
> 5. how far is current cvs from being samba4-stable?
> (estimated date and feature set)
This is a blurb I put in the upcoming 3rd edition of "Using Samba"
(O'Reilly). Hope it helps clarify things.
cheers, jerry
-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Franz Sirl wrote:
> v2 of the patch still works fine, but the list
> of working syntaxes changed. These work:
>
> valid users = +users
> valid users = +"Unix Group\users"
> valid users = S-1-22-2-100
>
> These didn't work:
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
> "Gerald (Jerry) Carter" <[EMAIL PROTECTED]> writes:
>
>>> It seems something has suddenly chagned whereby I
>>> cannot access any linux shares from windows.
>> Yup.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
> Setup: Running Gentoo linux 2.6X kenel
>Samba 3.0.23
I would recommend you start by getting
3.0.23b + the lookup_name_smbconf_v2.patch
file from http://www.samba.org/~jerry/patches/
> It seems something has suddenly
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
david rankin wrote:
> [EMAIL PROTECTED] samba-3.0.23b]# patch -p1 <
> ../samba-3.0.23b-lookup_name_smbconf_v1.patch
> patching file source/auth/auth_util.c
> Hunk #1 FAILED at 1052.
> 1 out of 1 hunk FAILED -- saving rejects to file
No idea. I doubl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
david rankin wrote:
> OK, Help, what am I doing wrong with the patch?? How do is
> get the patch installed? Here is what I did that didn't work.
>
> [EMAIL PROTECTED] src]# ll
> total 36072
> drwxr-xr-x 9 david david 4096 Jul 21 11:26 samba
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Franz Sirl wrote:
> the patch fixes the valid users problem for me. Or,
> to come back to the list of different syntaxes,
> these work:
>
>valid users = +users
>valid users = S-1-5-21-1540046517-542637695-1028676802-1201
>
> These d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Franz Sirl wrote:
> the patch fixes the valid users problem for me. Or, to
> come back to the list of different syntaxes, these work:
>
>valid users = +users
>valid users = S-1-5-21-1540046517-542637695-1028676802-1201
>
> These did
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jacky Chan wrote:
> [finsvcs]
> comment = Financial Service Files
> path = /data/finsvcs
> valid users = %G
> read only = No
This makes no sense. It says to only allow whatever the user's
primary group is. What are you trying to achieve?
cheers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gerald (Jerry) Carter wrote:
> Hey folks,
>
> Please try the attached patch (samba-3.0.23b-lookup_name_smbconf_v1.patch).
Once more with feeling (and the attachment)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Rankin wrote:
>> From: "Gerald (Jerry) Carter" <[EMAIL PROTECTED]>
>>
>> ok. Found the problem. It's smbpasswd. If you use tdbsam
>> everything is fine. Patch forthcoming shortly. Sorry.
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Adam Williams wrote:
> I'm not sure what you mean by user private groups. in
> /etc/group I have groups like:
>
> executive:x:743:usera,userb,userc
>
> and then in smb.conf in my shares i'll have valid
> users = @executive and it used to work fine
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Franz Sirl wrote:
> I have the same problem with a simple security = user,
> non-LDAP, non-windbindd etc. setup. I can workaround
> this for gid=100/groupname=users with:
>
>valid users = S-1-5-21-1540046517-542637695-1028676802-1201
>
> My
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Komal Shah wrote:
> What is the status of https://bugzilla.samba.org/show_bug.cgi?id=3204 ?
>
> I am using latest available version of Samba from samba.org and
> it seems that this issue is not solved.
Are you on FreeBSD as well ? I can't reproduce
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jurriaan Kalkman wrote:
> I know the 'print command' directive is disabled
> when printing via CUPS, the man page says so.
Technically the print command is disabled when linked
against libcups.so and you have printing = cups in a
printer section.
Y
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lewis Shobbrook wrote:
> Either the build options have changed or the
> guest operative has issues.
Please read the release notes and have the debian folks
fix their default configs. guest was never considered to
be a real passdb name. It was buil
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
LouArnold wrote:
> OK, I set the lohlevel to 10 in the smb.conf file. Then I deleted current log
> files for smbd and nmbd. I ran both and then I checked the smbd log file.
> The only sense of an error message is at the very end of the file:
> "smbd: s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
david,
>HELP! On mandriva, I compiled samba from source
> and got it running, but I cannot connect from windows.
> (see my post from earlier "[Samba] Compiling and
> Configuring Samba for Mandrival")
> [EMAIL PROTECTED]:~> smbclient //bonza/offi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Adam Williams wrote:
> ok I did a google search, and no I'm not using user
> private groups.
So can you send me a level 10 debug log from smbd ?
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.4 (MingW32)
Comment: Using GnuPG with Mozilla - http:/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Anni Evanoff wrote:
> "Printers and Faxes" applet view seems to constantly
> refresh every five seconds..and with a list of about
> 2500 printers, it is nearly impossible to scroll down
> to a specific printer and connect to it before the refresh.
T
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
M. D. Parker wrote:
> I am using samba with NO windbind and a configuration file
> that has worked for years stopped working at 3.0.23b.
> The affect was that my [netlogon] area was not being
> executed. I do have an access list for this share, but
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Adam,
> Can I ask, why the change, and why do I have to
> execute that command for each group instead
> of samba just getting who's in the group from
> /etc/group?
>
This doesn't make sense to me but there's not enough
information to comment. Are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ben Lentz wrote:
> FYI... downgrading to samba 3.0.21b fixed the
> problem, upgrading again to 3.0.23a makes it break,
> and downgrading one last time to 3.0.21b
> fixes it.
You did read in the release notes that winbind enum users/groups
is disabled
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Logan Shaw wrote:
> So, I'm building 3.0.23b for Slackware (since they don't have
> it out yet[1]), and I've noticed these two lines in the script
> that Slackware uses to build Samba 3.0.23 from source (which
> I'm modifying to build 3.0.23b):
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bill Greene wrote:
> So everything works except when an account with an old
> password tries to log in, even though "never expires" is
> set. I've tried a number of alternatives in the
> pam and samba config files to no avail.
It's our bug. We're
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hansjörg Maurer wrote:
> Hi
>
> I have updated a samba AD member server to 3.0.23b
> in an environment, where all Usernames are available
> in the AD and in NIS.
>
...
> To make it work with samba-3.0.21b
> we had this setting in smb.conf (winbindd
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Peter Daum wrote:
> Hi,
>
> when trying to upgrade my smb servers from older 3.x
> versions to samba 3.0.23, I discovered, that (already
> in 3.0.22), the "--with-ldapsam" option has been removed.
> According to the corresponding entry in the
> relea
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
samid wrote:
>
> Hi,
> Am trying to add some Debug statement to smbd, for
> example in service.c. But problem is when I
> recomplile and make install, smbd doesnt get updated
> with that code. problem here is this smbd
> executable(usr/sbin/smbd)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael,
>> Since Samba 3.0.8, it has been recommended that all domain
>> accounts listed in smb.conf on a member server be fully
>> qualified with the domain name. This is now a requirement.
>> All unqualified names are assumed to be local to the Un
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Gasch wrote:
> hi again :)
>
>> It's a variant of the same problem but has been
>> exacerbated by the change from string comparisons
>> to token based access checks for smb.conf parameters.
>
> stupid question: so why did you change to token b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nolan Garrett wrote:
> Anton N. Breusov wrote:
> It appears that we are experiencing the same problem - after upgrade to
> 3.0.23 I cannot access any shares on my Linux systems except for the
> home and printer shares. My configuration has
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gary Dale wrote:
> There error you are getting could be because you
> don't have cifs installed. As for the ip address
> vs. hostname, just make sure the host is defined
> in /etc/hosts.
Just a note
According the kernel change log, cifs didn't g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
==
"Where does he get those wonders toys?"
-- The Joker (Batman 1989)
==
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
werner maes wrote:
>> This is a systemic problem with this list. No one seems
>> to pay any attention until the release is done and over.
>
> off course you're right. but I don't think that one
> man could change this evolution. to be honest, I've
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
werner,
> anyway I still find it regrettable that multiple
> backends are no longer possible since we have our
> users stored in LDAP and the machine-accounts
> on the local PDC.
No offense, but it's too late to bring that up now. 3.0.23
was in dev
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Steve1 Boothright wrote:
> Hi
>
> A security update for samba 3.0.1 - 3.0.22 was
> posted on samba.org on the 10th July. Does anyone
> know how to apply to update?
See http://www.samba.org/samba/patches/ for details.
cheers, jerry
===
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Steven Rice wrote:
> Many questions goes in,
> Very few answers come out.
Maybe it's the ratio of people asking questions
vs. people answering them :-)
ciao, jerry
=
Samba
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Gasch wrote:
> i thought this would never get fixed, because i think
> i hit the same problem already last year.
>
> jerry said:
>>
>> Windows won't allow a user and groupw ith the same name.
>> Not much we can do about that. However, if yo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wisu wrote:
> Hi all,
>
> I setting up a new BDC (192.168.2.200 -> ubuntu dapper) assisting a
> PDC(192.168.1.195 -> debian sarge) to manage MYDOMAIN a separate
> Building.
>
> The problem I come up with is trying to apply printer
> drivers, I can u
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
werner maes wrote:
>
> hello
>
> the passdb backend no longer accepts multiple backends in a chaining
> configuration since samba 3.0.23a .
>
> question:
>
> will the following confi still work?
>
> passdb backend = ldapsam://ldapserver1 ldaps
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
éric le hénaff wrote:
> hello
>> I'd recommend dropping valid users from [profiles]
>> altogether.
>
> ah! it's interesting since the valid users line is
> recommended in idealx's linux samba-openldap howto.
> could u explain why u'd drop it ?
I thou
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Josh Kelley wrote:
> Since upgrading to Samba 3.0.23a, mounting a Samba
> share using mount.cifs generates the following errors
> in the Samba server's logs:
>
> Aug 7 17:45:08 pccentos4 smbd[5345]: [2006/08/07 17:45:08, 0]
> libsmb/smb_signing.c:s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John Mason wrote:
> [profiles]
> # chmod 1777 /home/%U/.msprofile
> path = /home/%U/.msprofile
> read only = no
> profile acls = yes
> create mask = 0600
> directory mask = 0700
> browseable = No
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Roshan Sembacuttiaratchy wrote:
> I'm trying to configure my Samba server to support
> Point-and-install driver installation of a CUPS
> printer (the printer works with Samba when
> Point-and-install is not configured, and the
> driver is installed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Peter Rindfuss wrote:
> I think I read somewhere that 'ldap machine suffix'
> is used only if winbindd is used as well.
Nope. The problem was more likely the fact that
nss_ldap was not searching the DIT for machine accounts.
cheers, jerry
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stephen Thomas wrote:
> 1. Does ntforms.tdb only store certain standard settings
> (page size, orientation, whatever) or can it hold
> anything a Windows printer driver cares to throw at it?
ntforms only stores paper sizes. ntprinters store the pe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Adam Wenner wrote:
> Okay guys, Im trying to get samba 3.0.23a to join a Windows Domain (no
> suprise right)
>
> Anyways, i ran "net rpc join -U [adminaccount]", it asked for the password to
> [adminaccount] and said the domain was joined.
>
> Then
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lee Baker wrote:
> Using Samba 3.0.23a-1.fc5.1
>
> When I try to add XP workstation to the domain using
> Network ID wizard (from XP) it fails.
>
> add machine script is: /usr/sbin/useradd -d /dev/null
>-g 500 -s /bin/false -M %u
>
> What hap
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Guido Lorenzutti wrote:
> When a do "net rpc list trustdom" I must provide a username and password
> for the domain admin.
> But if I want to revoke a trustdom I don't have to provide
> anything. Not a passowrd, not a user. Is this OK?
> Im using samb
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Josh,
> We have a Linux user and group with the same name
> (username prox, group name prox) and a Samba share
> with "force user = prox" set. Since upgrading from Samba
> 3.0.21b to Samba 3.0.23a, that share no longer works.
> smbclient gives the fo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Komal,
> Is there a way to control the number of times a file
> can be open concurrently? Either with Samba or with RHEL4?
> Maybe this is a good control measure. Limit the number
> of concurrent opens for any file. This
> way, if more than 20 people
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alexander Skwar wrote:
> Hello.
>
> When I run smbpasswd from samba 3.0.23a on a MIPSEL system running
> Linux 2.4.20 as root, I'm NEVER asked for a password. Even when I
> create a new user in smbpasswd, I'm not asked:
Please file a bug an attach th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris wrote:
> On Friday 04 August 2006 14:24, Chris wrote:
>> If not, why might members of the domadm group (as in the second
>> example) not have admin priveleges when logging onto the domain?
>
> I figured this part outspecific RID's are needed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joseph Holtgrefe wrote:
> I am currently running the latest build of samba-3.0.23a with a tdbsam
> backend. I have noticed for sometime now when I use pdbedit -c [X] username
> it sets the Account Flag X for password never expires but does not modify
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Peter Trifonov wrote:
> Dear Jerry,
>
>
>>> log.winbindd contains a lot of messages like
>>> [2006/07/24 15:12:19, 0] nsswitch/winbindd.c:request_len_recv(517)
>>>request_len_recv: Invalid request size received: 1836
>> This can only be a misma
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gerald (Jerry) Carter wrote:
> Jeremy Allison wrote:
>>> On Fri, Aug 04, 2006 at 04:47:34PM +0200, Franz Strebel wrote:
>>>> Hello,
>>>>
>>>> Yes, same problem with @"DOMAIN+name with spaces"
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Peter Trifonov wrote:
> Hello everyone,
>
> I have raised this question some time ago, but the solution still was not
> found.
>
> The FreeBSD 6.1 server is a member of ADS domain. There is a
> directory named test with write permissions granted to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeremy Allison wrote:
> On Fri, Aug 04, 2006 at 04:47:34PM +0200, Franz Strebel wrote:
>> Hello,
>>
>> Yes, same problem with @"DOMAIN+name with spaces".
>
> It's probably the 'remove " character at end of line' trim_string
> code. I'll take a look (b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nanni X wrote:
> Did you follow step-by-step the guidelines explained in
> the HowTo to join ADS?
>
> We too have a W2K3 server updated to last sp and post-sp
> updates by Windows' automatic update and we
> encountered no problems following the How
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Breen wrote:
> I just installed Samba 3.0.23a from the sources on a Slackware 10
> server kernal version 2.4.26. I didn't get any errors during
> installation. When I try to start the Samba daemon by smdb -D nothing
> happens. Here is a snippet
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sean R. Hanson wrote:
> passdb/pdb_smbpasswd.c:build_sam_account(1202)
> build_sam_account: smbpasswd database is corrupt! username COMPUTER$
> with uid ### is not in unix passwd database!
>
> The previous version has not troubles. I'm not sure wh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ephi Dror wrote:
> Hi all,
>
> I have a situation in which my SAMBA 3.0.14a could not join
> the a very large windows 2003 AD domain with tens of
> domain controllers all over the world. With an error I
> have never seen before. The kinit part went
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Griffith wrote:
> Just one last question in regards to rid_algorithm can
> I assume the following?
>
> return False if we don't generate our own rid - let
> Samba handle return True if we generate our own rid -
> let our rid function handle
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kirk Henry wrote:
> Good Day:
>
> I have been trying all week to install the 23a version of Samba on a
> Fedora core 5 distribution. When I try to start smbd, the log indicates
> that the demon wont start because of an undefined symbol. Here is the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Peter,
> Dear Jerry,
>
>
>> wok. Couple of questions. Sorry if you already provided
>> this information but I can't remember.
>>
>> * Is this 3.0.23 ? or 3.0.23a ?
> It is 3.0.23.
Please test 3.0.23a. I made some changes to the winbindd
request
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Peter Trifonov wrote:
> FreeBSD's nsswitch seems to be able to look in /usr/local/lib.
> I have tried to create symlink to those libraries in /lib,
> but this did not change anything. These libraries were located in
> /usr/local/lib for previous Samba
701 - 800 of 4112 matches
Mail list logo
