[Samba] Samba/GPFS/GlusterFS

[François Legal]

  

Hello, 

sorry for this little OT post. 

In my company, we have 2
distant facilities, with people at each facility working on the same
files. 

The 2 facilities are connected through MPLS with about
10MBytes/s BW. 

Saving the work files to servers located at one or the
other facility has became a pain for the people accessing the files from
the remote site. 

Trying to improve files availability, I was wondering
if a setup based on GPFS/GlusterFS plus samba for serving the file would
be a good reply to this problem. 

Does anybody have experience with
this ? 

Thanks. 

François 
  
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

[Samba] Fwd: Re: Can't add users to well known groups...

[François Legal]

  

Forgot to CC the list. 

 Original Message 


SUBJECT:
Re: [Samba] Can't add users to well known
groups...

DATE:
Mon, 12 Sep 2011 15:51:31 +0200

FROM:

    François Legal 

TO:
Linda Walsh 

Not sure if this is relevant,
but if (first case shown down here) "Domain Admins" is not so much a
group but a map to unix group, I'm not surprised that you can't add
users to this using sambe. I would rather use /etc/group or whatever to
add users to the unix group mapped. 

François 

On Sat, 10 Sep 2011
12:08:32 -0700, Linda Walsh wrote: 

> Harry Jede wrote:
> 
>> On
15:48:09 wrote Linda Walsh: 
>> 
>>> I created the well known group
Domain Admins pointing to a local group, but I am not able to add users
to the group -- it claims I can only add users to local or global
groups... But I only see local, domain ,well-known, builtin. There are
no global groups unless one would include all groups that are not local
(i.e. domain, well-known, and builtin) So why doesn't it want to let
me add to my domain admins group when it is defined as a well known
group (which it is, according to MS)...
>> Nobody may be able to answer
your questions, if you dont give us some background information!
something like: which samba version which sam, ldapsam or tdbsam do you
use winbind your global section of samba conf the commands you have used
which well knwon groups you have cureently ---
> 
> Sorry...
> running
with latest 3.5.x: 3.5.11 as of this writing.
> Using Tdb & winbind.
>
Since I as having problems with Domain Admins, tried deleting
> it and
recreating it as a domain group (so it doesn't show, below, as a
> 'well
known group, but a domain group (even though it should be both)).
>
--
> 
>> sudo net -l groupmap list
> 
> Domain Users
> SID :
S-1-5-21-3-7-3-513
> Unix gid : 513
> Unix group: Domain
Users
> Group type: Well-known Group
> Comment : Wellknown Unix group
>
man
> SID : S-1-5-21-3-7-3-1028
> Unix gid : 62
> Unix
group: man
> Group type: Domain Group
> Comment : Unix Group man
>
Domain Controllers
> SID : S-1-5-21-3-7-3-516
> Unix gid :
516
> Unix group: Domain Controllers
> Group type: Well-known Group
>
Comment : Wellknown Unix group
> Backup Operators
> SID : S-1-5-32-551
>
Unix gid : 551
> Unix group: Backup Operators
> Group type: Well-known
Group
> Comment : Wellknown Unix group
> Power Users
> SID :
S-1-5-32-547
> Unix gid : 547
> Unix group: Power Users
> Group type:
Well-known Group
> Comment : Wellknown Unix group
> Cert Publishers
>
SID : S-1-5-21-3-7-3-517
> Unix gid : 517
> Unix group: Cert
Publishers
> Group type: Well-known Group
> Comment : Wellknown Unix
group
> Replicators
> SID : S-1-5-32-552
> Unix gid : 552
> Unix group:
Replicators
> Group type: Well-known Group
> Comment : Wellknown Unix
group
> Domain Admins
> SID : S-1-5-21-3-7-3-544
> Unix gid
: 512
> Unix group: Domain Admins
> Group type: Domain Group
> Comment :
Domain Unix group
> Juno
> SID : S-1-5-21-3-7-3-1005
> Unix
gid : 231
> Unix group: Juno
> Group type: Domain Group
> Comment : Juno
Printer Group
> media
> SID : S-1-5-21-3-7-3-1017
> Unix gid
: 20001
> Unix group: media
> Group type: Domain Group
> Comment : Unix
Group media
> Administrators
> SID : S-1-5-32-544
> Unix gid : 544
>
Unix group: Administrators
> Group type: Well-known Group
> Comment :
Wellknown Unix group
> Domain Guests
> SID :
S-1-5-21-3-7-3-514
> Unix gid : 514
> Unix group: Domain
Guests
> Group type: Well-known Group
> Comment : Wellknown Unix group
>
Trusted Local Net Users
> SID : S-1-5-21-3-7-3-50002
> Unix
gid : 50002
> Unix group: trusted_local_net_users
> Group type: Domain
Group
> Comment : Trusted Local Net Users
> Account Operators
> SID :
S-1-5-32-548
> Unix gid : 548
> Unix group: Account Operators
> Group
type: Well-known Group
> Comment : Wellknown Unix group
> Schema
Admins
> SID : S-1-5-21-3-7-3-518
> Unix gid : 518
> Unix
group: Schema Admins
> Group type: Well-known Group
> Comment :
Wellknown Unix group
> RAS Servers
> SID : S-1-5-32-553
> Unix gid :
10123
> Unix group: BUILTINras servers
> Group type: Local Group
>
Comment :
> scan
> SID : S-1-5-21-3-7-3-1006
> Unix gid :
232
> Unix group: scan
> Group type: Local Group
> Comment : Local Unix
group
> Users
> SID : S-1-5-32-545
> Unix gid : 1
> Unix group:
BUILTINusers
> Group

Re: [Samba] Problem of: Trust relationship between 2 linux domains

[François Legal]

  

Maybe you can describe a little more your setup
(NET->DOMAINS->DC->machines) 

Do you have Winbind up and running ? Does
wbinfo -t show that the truted domain is OK ? Can you see the trusted
domain users/group with wbinfo -u/-g ? 

I think that I had resolution
problems even with using the same WINS. I had to create an LMHOST files
on both DCs. 

François 

On Thu, 31 Mar 2011 16:34:39 +0700, bình lê
thanh wrote: 

> Hi François,
> 
> Thanks for answering, I've setup 2
domains used one WINS server (DOM1), but still the same error:
> 
> The
user of DOM2 can not log on DOM1 by WinXP!
> 
> I send you the pictures
that I capture from the screen. Can you tell me what I should do or show
me a step by step congiguration?
> 
> Thanks a lot for paying attention!
:)
> 
> --
> Lê Thanh Bình
> AICT, HCMC, VietNam
> 0985 302 524
 
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

Re: [Samba] strange issue with xerox printer: unable to configure driver

[François Legal]

Hi,

I've been having the same problem on a 7328 if I remember well.

The problem is that the Xerox driver uses some proprietary print
processor. Under windows, the print server is expected to run the print
processor (which is not possible with samba as the print processor is a
w32
exec).

You have (as far as I know) 2 options here :
- Setup the printer in samba without specifying the driver (samba will
then only be used as a spooler for win clients). Point and print can then
no more be used
- Buy the postscript option from Xerox and use the print driver from cups
for the win clients

François



On Fri, 27 Nov 2009 18:32:58 +0100, Guillaume Rousse
 wrote:
> Hello list.
> 
> I've a strange issue with a samba 3.4.3 print server. Everything is fine

> with most printers, meaning drivers are assigned on server side and 
> automatically distributed to the clients as expected. However, I fail to

> configure a Xerox document center 7435 the same way.
> 
> When I attempt to assign a driver to the printer, from a windows client 
> with admin privileges,  I get an 'unexpected error occured in the print 
> driver, close this windows and retry' error message, twice. More 
> precisely, I can see initial renaming of the printer according to the 
> driver name, then the error occurs, then the printer get renamed to '' 
> (which is a bit painful :P)
> 
> I previously had a slightly different model (document center pro c2636) 
> which was working fine. The other working printers are not xerox ones.
> 
> The driver is OK: it works fine when accessing the printer directly, and

> also when used from a windows print server. Also, I tried other variants

> (such as PCL driver instead of PS one), without success.
> 
> When configuring the same printer from a Windows system, I had to 
> configure it with raw socket connection, because IPP connection didn't 
> allowed me to share it at all, and CIFS connection to the print queue 
> caused me some troubles (the printer didn't appeared in the 'fax and 
> printers list' of the server from remote hosts).
> 
> The underlying printing system, cups, works perfectly. I've tried to 
> switch from IPP to raw socket connection, because of the behaviour 
> changes found with windows server, it didn't change anything.
> 
> I performed a network capture both on server and client side while 
> triggering the error. The result is available as:
> http://www.zarb.org/~guillomovitch/server.pcap
> http://www.zarb.org/~guillomovitch/client.pcap
> 
> I can see some suspicious messages such as:
> WINREGOpenKey response, Error: WERR_BADFILE
> SPOOLSS   GetPrinterData response, PrintProcCaps_NT EMF 1.008, File not 
> found (pathname error)
> SPOOLSS   SetPrinterDataEx response, Access denied
> 
> But nothing really useful.
> 
> I'm joining my samba configuration file. I'm using mandriva 2009.0 as 
> server, and windows XP enterprise as client.
> 
> Any hint appreciated.
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

Re: [Samba] winbind causes Linux to lockup when connectivity to AD is lost (subject line edited for clarity)

[François Legal]

I don't know if it helps, but I ran through similar problems with one
samba DC trusting another domain connected via a VPN.
Each time the VPN went down, I had to hard reboot the server (no I did not
have an open session all the time to kill winbindd).

As far as I remember, this was with self built versions 3.2.4 through
3.2.6.
After that, I decided to surrender with trusting another domain with
samba.

François

On Fri, 16 Oct 2009 13:59:45 -0600,  wrote:
> Ok I am not hearing replies back - I dont want this issue to be swept
under
> the rug. 
> 
> 
> It has been a issue for me since SuSE 10.1 + samba-3.0.30-0.1.112 even..
> I know now that the commands I was telling you all access UN/PW info
such
> as LS or MAN etc, to see if you have permission to run them? IDK I am
> guessing.
> 
> BUT - if winbind is really caching and the connection is lost, then this
> should be a non-issue as you say.
> 
> Well here is my nsswitch.conf:
> 
> 
> cat /etc/nsswitch.conf
> 
> 
> passwd: compat winbind
> group:  compat winbind
> 
> networks:   files dns
> 
> services:   files
> protocols:  files
> rpc:files
> ethers: files
> netmasks:   files
> netgroup:   files
> publickey:  files
> 
> bootparams: files
> automount:  files
> aliases:files
> 
> hosts:  files dns
> shadow: compat
> 
> 
> Isn't this set up right? ;-)
> 
> 
> So, famously when DNS is down, crap like SSH and NFS take unreasonable
> amounts of time and cause system hangs in linux. This is what I've been
> told, and I can accept that.
> Since DNS is hosted on the AD server, when that server goes down, SSH,
and
> even local login hang for extremely long amounts of time - im talking
more
> than 10 minutes... then fail.
> 
> In Windows (im sorry Im about to compare 2 operating systems) this is a
non
> issue and you can use the machine even if the networking is hosed or you
> cant talk to the AD.
> 
> So...
> 
> BUMP! :-)
> 
> 
> 
> 
> 
> On Wed, 14 Oct 2009 16:51:10 -0600,  wrote:
>> Hopefully that isn't a bad thing! haha 
>> Thanks! 
>> 
>> 
>> On Wed, 14 Oct 2009 15:44:54 -0700, Jeremy Allison 
wrote:
>>> On Wed, Oct 14, 2009 at 04:02:41PM -0600, ad...@ateamonsite.com wrote:
 Hi Jeremy,
 
 
 > Sorry, didn't look too closely at your winbindd issue.
 > winbindd will cache all information to allow disconnected
 > operation (we made this work perfectly at SuSE), so there
 > certainly shouldn't be a problem with a loss of connection to a DC.
 
 I am sorry to report that I am in fact using SuSE, and this problem
is
 very
 easy to reproduce if I power off my AD domain, then wait (I guess) 10
 minutes - then try and ssh to my Linux box. There is no way to log
into
 the
 box. 
>>> 
>>> Ok, then I'm going to hand you over to the SuSE Samba Team
>>> maintainers on this list (sorry :-).
>>> 
>>> Jeremy.
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

[Samba] MS Access 2007 files corrupted with 3.3.2

[François Legal]

Hello, 

I'm having a case here where MS Access 2007 databases get corrupted while
trying to open with samba 3.3.2. 

I'm not sure wether this problem is related to the one with MS Word/excel
2007 with 3.3.0 and 3.3.1. 

Franois 

 
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

[Samba] Trustdom not working if trusted smbd > 3.2.4

[François Legal]

I'm trying (for a while now) to upgrade to 3.3.x my samba PDC, but I've
troubles with the trusting PDC. 

While using samba > 3.2.4 on the trusted side, the trusting side can no
more enumerate users and groups from the trusted PDC. 

Winbind raises the error NETWORK_ACCESS_DENIED while trying to connect
with NTLMMSP. I saw this behaviour with 3.2.6, 3.3.0 and now 3.3.2 on the
trusted end. The trusting end work ok with 3.3.2. 

Can anybody help ? 

Thanks 

Franois 

 
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

Re: [Samba] Can't modify ms word files with samba 3.3

[François Legal]

> Ok, looking in the log I've found the problem. The application
> is asking for an access mask of 0x102, which maps to
> 
> READ_CONTROL_ACCESS (which we grant) and SEC_RIGHT_SYSTEM_SECURITY
> (ie. access to the system security ACL - the audit ACL) on the
> file.
> 
> From this page: 
> 
> http://msdn.microsoft.com/en-us/library/aa379321(VS.85).aspx
> 
> "SACL Access Right
> 
> The ACCESS_SYSTEM_SECURITY access right controls the ability to get or
set
> the SACL in an object's security descriptor. The system grants this
access
> right only if the SE_SECURITY_NAME privilege is enabled in the access
token
> of the requesting thread."
> 
> We do not support the SE_SECURITY_NAME privilege and don't
> allow setting SACLs (we don't support them).
> 
> Someone else has already raised this previously. Do your
> users have the SE_SECURITY_NAME privilege in their local
> tokens (ie. are they allowed to set SACLs on their local
> filesystem). Does this happen to non-privileged users ?
> 
> A suggestion has been made to ignore the SEC_RIGHT_SYSTEM_SECURITY
> request (just mask it out) for filesystem access while
> we don't support SACLs, but I'm concerned as to why the
> application is trying to request it ?
> 
> Jeremy.

To be honnest, I did not really understand what SACL is. Are you talking
about file and directories ACLs ?

How do I know if my users have the SE_SECURITY_NAME  priviledge. My users
(especially the one who is accessing the file in the log) are normal users
without any specific priviledge (not even doamin admins nor local
workstation admin). However, they're not prevented from setting files and
directories ACLs neither on local nor network drives (they're welcome to as
our filesystems are XFS).

About the application requesting something specific, I don't know. The
file was created with that same version of MS Word (2007) by that same user
(the one trying to modify it as in the log) but with another samba version
(one of 3.2.0 3.2.2 or 3.2.4)

Where should I go from here?

Thank youfor helping

François


-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

[Samba] Can't modify ms word files with samba 3.3

[François Legal]

Hello, 
I tried this week to upgrade my samba 3.2.4 (2 PDCs one trusting the
other) to samba 3.3.0 then samba 3.3.1, and apart from the problem
with winbindd and trusted domain, my users are not able to modify any
ms word document (excel does the same). 

You can open the file correctly, modify it, and when saving it, it
pops up "Access denied" 

If you try to save the file in the same directory with another name,
it does not work either (sam "access denied" message). 
I tried to set og level to 10, but could not find anything pointing
me to the right direction. 
Can anybody help ? 
François
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

Re: [Samba] Changing LDAP userPassword fails: Internal (implementation specific) error

[François Legal]

Well, you usually have some specific acl in ldap for the userPassword
attribute, that restrict access to only the owner of the entry and an
administrator. You should make sure that the dn used by samba to bind the
directory (ldap admin dn) has access to the userPassword attribute.
Also, you should check that ldap is not setup with smbpasswd overlay, in
which case you should change the ldap sync parameter to only.

François

On Sun, 22 Feb 2009 14:02:15 -0500, Adam Tauno Williams
 wrote:
> openldap-2.3.27-8.el5_2.4,samba3-3.2.8-38
> 
> An smbpasswd by root to change a user's password fails with:
> 
> [r...@littleboy samba]# smbpasswd adam
> New SMB password:
> Retype new SMB password:
> ldapsam_modify_entry: LDAP Password could not be changed for user adam:
> Internal (implementation specific) error
>   password hash failed
> Failed to modify entry for user adam.
> Failed to modify password entry for user adam
> 
> This changes the Samba password but fails to change the user's
> userPassword (LDAP sync) password.  But I can "manually" change the
> password using the DC's bind DN and password:
> 
> # ldappasswd -S -H ldapi://%2fvar%2frun%2fldap2.4%2fldapi -v -x
> -W   -D "uid=CIFSDC,ou=System,ou=Entities,ou=SAM,o=Morrison
> Industries,c=US"   "cn=Adam
> Williams,ou=People,ou=Entities,ou=SAM,o=Morrison Industries,c=US"
> New password: 
> Re-enter new password: 
> Enter LDAP Password: 
> ldap_initialize( ldapi://%2fvar%2frun%2fldap2.4%2fldapi )
> Result: Success (0)
> 
> Samba LDAP configuration:
> passdb backend = ldapsam:ldapi://%2fvar%2frun%2fldap2.4%2fldapi
> ldap ssl = no
> ldap admin dn = uid=CIFSDC,ou=System,ou=Entities,ou=SAM,o=Morrison
> Industries,c=US
> ldap suffix = o=Morrison Industries,c=US
> ldapsam:trusted = yes
> ldap passwd sync = Yes
> 
> Oddly, attempting to change the password AS THE USER fails with a
> different error message, either via smbpasswd or via the password change
> dialog on a Win32 workstation:
> 
> bash-3.2$ smbpasswd -U adam
> Old SMB password:
> New SMB password:
> Retype new SMB password:
> machine 127.0.0.1 rejected the (anonymous) password change: Error was :
> Wrong Password.
> Failed to change password for adam
> 
> It always just says the user's password is wrong,  although the user can
> login, navigate, etc...
> 
> Is this https://bugzilla.samba.org/show_bug.cgi?id=5886 ?
> 
>

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

Re: [Samba] LDAP Migration problem

[François Legal]

You should check your directory for the sambaHomePath and sambaHomeDrive
attributes.
These should be respectively set to the UNC path a each user home
directory, and to x:

François

On Thu, 19 Feb 2009 09:23:29 +, Gerard Hooton  wrote:
> Hello all,
> I am using Samba version 3.2.5 configured for Windows Domain login.
> It was working fine until I moved over to ldapsam.
> Now when I login to the XP client I don't see the logon drive (X: in my
> case)
> Any debug tips?
> 
> //Ger
> 
> 
> 
> -- 
> 
> Gerard Hooton
> 
> Systems Administrator
> 
> Blarney Boy's National School,
> 
> Blarney.
> 
> Co. Cork
> 
> 
>

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

[Samba] Fwd: Winbindd crash with 3.3.0

[François Legal]

Hello, 
I thought it would be better to make a new thread on this specific
point though it is related to the other thread I opened yesterday
(Trustom not working after upgrade to 3.3.0) 
So this crash occurs at least in 3.2.6 and 3.3.0 (I raised bug 6034
on 3.2.6 but it also applies to 3.3.0) but not in 3.2.4. I did not
check with the intermediate versions, but I guess this must be present
since 3.2.6 to current. 

This crash happens when the remote DC present domain groups with non
domain users members (in my case, this was a badly configured trusted
samba PDC), and winbindd tries to enumerate the group members. 
I'd be glad to track this down to the code, but so far I've been
unable to build binaries with debug synbols useables by gdb. 
François
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

Re: [Samba] Trustom not working after upgrade to 3.3.0

[François Legal]

So it seems I was wrong when stating "reverting trusted PDC to 3.2.4 fixes
the problem".
When I do that, then I fall in what seem to be a bug that I raised on 3.2.6
(Bug 6034)

I will try to do more research on that, since when I raised the bug, I
could not get a valid backtrace in gdb.

On Mon, 16 Feb 2009 23:05:30 +0100, François Legal 
wrote:
> 
> 
> Hello, 
> I was running 3.2.4 successfully with trustdom relationship (one way
> only) working perfectly. 
> 
> I'm trying now to upgrade to 3.3.0, but the relationship seems to be
> down now. Revoking and re establishing did not help. I had the same
> issue while trying to update to 3.2.6 
> By checking the logs, it seems that trusting domain PDC is not
> sending the correct password to trusted domain PDC when connectiong to
> the Samr pipe. 
> 
> Reverting trusted domain PDC to 3.2.4 fixes the problem. 
> I can provide level 10 logs of both PDCs (smbd for trusted and
> winbindd for trusting). 
> Anybody can help ? 
> Thanks 
> François
>

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

[Samba] Trustom not working after upgrade to 3.3.0

[François Legal]

Hello, 
I was running 3.2.4 successfully with trustdom relationship (one way
only) working perfectly. 

I'm trying now to upgrade to 3.3.0, but the relationship seems to be
down now. Revoking and re establishing did not help. I had the same
issue while trying to update to 3.2.6 
By checking the logs, it seems that trusting domain PDC is not
sending the correct password to trusted domain PDC when connectiong to
the Samr pipe. 

Reverting trusted domain PDC to 3.2.4 fixes the problem. 
I can provide level 10 logs of both PDCs (smbd for trusted and
winbindd for trusting). 
Anybody can help ? 
Thanks 
François
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

Re: [Samba] Winbind dumps core after upgrade to 3.2.6

[François Legal]

Could file the bug : Bug 6034

Thanks

François

On Tue, 16 Dec 2008 17:31:33 +0100, Michael Adam  wrote:
> Hi François,
> 
> yes, please file a bug report with this issue,
> providing configuration detais and log files.
> 
> 
> If possible, a more meaningful backtrace would be helpful:
> 
> * Be sure to compile with debugging symbols (cflag "-g").
> * add 'panic action = "/bin/sleep 9"' to your smb.conf
> * restart winbindd
> * reproduce the panic. "ps axf" shows the sleep process as
>   a child process of the panicing process
> * attach gdb to the process with "gdb --pid" and do a "bt"
> 
> Cheers - Michael
> 
> François Legal wrote:
>> 
>> 
>> Hello, 
>> I was running 3.2.4 since yesterday evening, when I decided to
>> upgrade to 3.2.6 
>> 
>> I did recompile from the sources (with the same configure options I
>> used for 3.2.4) then shutdown samba, replace the binaries and libs,
>> then start again. 
>> 
>> Everything then went fine until this morning when a user from a
>> trusted domain made a connection to the DC. I took a look and saw that
>> winbindd dumped core yesterday evening by the time I disconnected from
>> the machine 
>> 
>> [2008/12/15 22:35:04,  0] lib/fault.c:fault_report(40)
>>   ===
>> [2008/12/15 22:35:04,  0] lib/fault.c:fault_report(41)
>>   INTERNAL ERROR: Signal 11 in pid 19111 (3.2.6)
>>   Please read the Trouble-Shooting section of the Samba3-HOWTO
>> [2008/12/15 22:35:04,  0] lib/fault.c:fault_report(43)
>>   From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
>> [2008/12/15 22:35:04,  0] lib/fault.c:fault_report(44)
>>  
>> ===
>> [2008/12/15 22:35:04,  0] lib/util.c:smb_panic(1663)
>>   PANIC (pid 19111): internal error
>> [2008/12/15 22:35:04,  0] lib/util.c:log_stack_trace(1767)
>>   BACKTRACE: 18 stack frames:
>>#0 /usr/local/samba/sbin/winbindd(log_stack_trace+0x1a)
>> [0x5566fdd7]
>>#1 /usr/local/samba/sbin/winbindd(smb_panic+0x5b) [0x5566fee7]
>>#2 /usr/local/samba/sbin/winbindd [0x5565d24a]
>>#3 /lib/libc.so.6 [0x2b1862ac6110]
>>#4 /usr/local/samba/sbin/winbindd(strlower_m+0xd) [0x55666b1a]
>>#5
>> /usr/local/samba/sbin/winbindd(fill_domain_username_talloc+0x33)
>> [0x55
>> 5d3ee8]
>>#6 /usr/local/samba/sbin/winbindd [0x555f06b0]
>>#7 /usr/local/samba/sbin/winbindd [0x555f2985]
>>#8 /usr/local/samba/sbin/winbindd [0x555dcad2]
>>#9 /usr/local/samba/sbin/winbindd [0x555d0e0f]
>>#10 /usr/local/samba/sbin/winbindd [0x555d3248]
>>#11 /usr/local/samba/sbin/winbindd [0x555fd735]
>>#12
>> /usr/local/samba/sbin/winbindd [0x555f784c]
>>#13 /usr/local/samba/sbin/winbindd [0x555f6e9b]
>>#14 /usr/local/samba/sbin/winbindd [0x555cb566]
>>#15 /usr/local/samba/sbin/winbindd(main+0xea7) [0x555cc4a4]
>>#16 /lib/libc.so.6(__libc_start_main+0xda) [0x2b1862ab34ca]
>>#17 /usr/local/samba/sbin/winbindd [0x555ca06a]
>> [2008/12/15 22:35:04,  0] lib/fault.c:dump_core(201)
>>   dumping core in /var/log/samba/cores/winbindd 
>> 
>> Shall I raise a bug report ? 
>> François 
> 
>

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

[Samba] Winbind dumps core after upgrade to 3.2.6

[François Legal]

Hello, 
I was running 3.2.4 since yesterday evening, when I decided to
upgrade to 3.2.6 

I did recompile from the sources (with the same configure options I
used for 3.2.4) then shutdown samba, replace the binaries and libs,
then start again. 

Everything then went fine until this morning when a user from a
trusted domain made a connection to the DC. I took a look and saw that
winbindd dumped core yesterday evening by the time I disconnected from
the machine 

[2008/12/15 22:35:04,  0] lib/fault.c:fault_report(40)
  ===
[2008/12/15 22:35:04,  0] lib/fault.c:fault_report(41)
  INTERNAL ERROR: Signal 11 in pid 19111 (3.2.6)
  Please read the Trouble-Shooting section of the Samba3-HOWTO
[2008/12/15 22:35:04,  0] lib/fault.c:fault_report(43)
  From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
[2008/12/15 22:35:04,  0] lib/fault.c:fault_report(44)
 
===
[2008/12/15 22:35:04,  0] lib/util.c:smb_panic(1663)
  PANIC (pid 19111): internal error
[2008/12/15 22:35:04,  0] lib/util.c:log_stack_trace(1767)
  BACKTRACE: 18 stack frames:
   #0 /usr/local/samba/sbin/winbindd(log_stack_trace+0x1a)
[0x5566fdd7]
   #1 /usr/local/samba/sbin/winbindd(smb_panic+0x5b) [0x5566fee7]
   #2 /usr/local/samba/sbin/winbindd [0x5565d24a]
   #3 /lib/libc.so.6 [0x2b1862ac6110]
   #4 /usr/local/samba/sbin/winbindd(strlower_m+0xd) [0x55666b1a]
   #5
/usr/local/samba/sbin/winbindd(fill_domain_username_talloc+0x33)
[0x55
5d3ee8]
   #6 /usr/local/samba/sbin/winbindd [0x555f06b0]
   #7 /usr/local/samba/sbin/winbindd [0x555f2985]
   #8 /usr/local/samba/sbin/winbindd [0x555dcad2]
   #9 /usr/local/samba/sbin/winbindd [0x555d0e0f]
   #10 /usr/local/samba/sbin/winbindd [0x555d3248]
   #11 /usr/local/samba/sbin/winbindd [0x555fd735]
   #12
/usr/local/samba/sbin/winbindd [0x555f784c]
   #13 /usr/local/samba/sbin/winbindd [0x555f6e9b]
   #14 /usr/local/samba/sbin/winbindd [0x555cb566]
   #15 /usr/local/samba/sbin/winbindd(main+0xea7) [0x555cc4a4]
   #16 /lib/libc.so.6(__libc_start_main+0xda) [0x2b1862ab34ca]
   #17 /usr/local/samba/sbin/winbindd [0x555ca06a]
[2008/12/15 22:35:04,  0] lib/fault.c:dump_core(201)
  dumping core in /var/log/samba/cores/winbindd 

Shall I raise a bug report ? 
François 

 
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

Re: [Samba] Printer upload problem

[François Legal]

I don't know of this particular WorkCenter model, but I had a similar issue
with a 7328 and samba 3.2.X

The problem is that Xerox drivers install a print processor (other than the
ones natively available in Windows like WinPrint) which requires a windows
machine to be run.

I think (I don't know what is possible with samba 4 but I doubt this could
be possible) that setting up point'n print for this kind of printer with
samba is not possible. You require a Windows machine.

I don't know if you have any kind of support services available by Xerox
(that may help you solving the issue) but the only answer I could get from
their support is "Buy the PostScript option first, then we'll see".

I finally decided to not have the drivers uploaded to the server, and use
the server only as a print queue and select the right driver when
installing the printer on the client machine (with all the drawbacks that
come along with this method like having to setup the printer parameters and
options each time on each machine) which, I guess, is not an option to you.

If you can get this to work with (maybe) the help of Xerox, I'm interested
in the solution.

François

On Tue, 09 Dec 2008 15:25:15 +0100, Nicolas HAHN <[EMAIL PROTECTED]>
wrote:
> 
> 
>Hi there,
> 
>We have 4 samba print servers we use for our 3000 users. they're  
> configured to automatically distribute printer drivers to our windows  
> clients.
> 
>Recently, we have added a Xerox WorkCenter 5638 monster.
> 
>But we're unable to upload the driver to the samba server throught  
> print wizzard as windows admin. We've tried PCL, PCL 6, and PS drivers  
> available on Xerox web site, without success. It is still the same:  
> various alert boxes appears, some with very strange numbers (ie:  
> 040:000:0466). In samba logs, I can see several STATUS_BUFFER_OVERFLOW  
> messages.
> 
>I've tried with samba version 3.0.22 and 3.0.27, on RHEL 5.1  
> installed on x64 architecture.
> 
>Furthemore, we experiment printer wizard crashes with various  
> printer drivers, and for most of them (we have almost 300 printers!),  
> we found a combination PRINTER MODEL <-> PRINTER DRIVER which finally  
> works, but it's not the panacee because the drivers don't really  
> correspond to the printer (ie: we use HP LJ 8050 driver for a HP LJ  
> 9550 printer to have things working).
> 
>We really need help about this problem, and we'd like to thank by  
> advance for any help provided (or bug fix!) as this is a kind of  
> emergency for us.
> 
>Thanks a lot :-)
> 
>--
> Nicolas HAHN
> X-Itools project manager
> 
> 
> This message was sent using IMP, the Internet Messaging Program.
> 
>

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

[Samba] Samba hangs after WAN link to trusted domain is cut

[François Legal]

Hello, 
Wondering if this is a known behaviour in samba. 

I have 2 domains (say DOM_A and DOM_B) with DOM_B trusting DOM_A (one
way relation). DOM_A and DOM_B are located in two different nets (and
locations) and are connected through a VPN. 
What happens is that if the VPN goes down, samba PDC at DOM_B seems
to be hung (can't provide auth to clients anymore), and this remains
even after the VPN link is restored. 

I don't have so much data to add to this threads, except this : 

After the VPN went down, I did try to start a service on one client
(being connected on the PDC console) by using the net -U admin -W
DOM_B rpc service start MyService, and the command failed indicating
no domain controller was available. 

By checking the nmbd logs, I could notice some browsing issue as both
PDCs are configured with : 

remote browse sync = Address of the other domain PDC 

remote announce = Address of the other domain PDC 
After I commented out both line at DOM_B PDC, the failure
disappeared
(as far as I could test). 
So now my question is : is this kind of a feature (implied by remote
browse sync) of did I misconfigured something. 
Thanks 
François
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

Fwd: Re: [Samba] Samba 3.2.4 and alternate data streams

[François Legal]

To be honest, I'm not sure wether these alternate data stream files were
created under 3.2.0 3.2.2 or 3.2.4.
I just noticed that they are here and report.

How can I make sure that these files will not be created again (some kind
of test case that records alternate data streams) ?
Is there any possibility to disable this alternate data stream feature ?

François

 Original Message 
Subject: Re: [Samba] Samba 3.2.4 and alternate data streams
Date: Wed, 24 Sep 2008 19:51:00 -0400
From: "James Kosin" <[EMAIL PROTECTED]>
To: François Legal <[EMAIL PROTECTED]>

- Original Message - 
From: "François Legal" <[EMAIL PROTECTED]>
Newsgroups: linux.samba
Sent: Wednesday, September 24, 2008 6:10 PM
Subject: [Samba] Samba 3.2.4 and alternate data streams


>
>
> Hello,
> I just upgraded to 3.2.4, and today I observed in one of my share
> that some of the file where being kind of duplicated with a trailing
> ":Zone.Identifier:$DATA" at the end of filename.
>
> I think this has to do with alternate data streams, but the point is
> the share runs out of an XFS filesystem which is supposed to support
> the xattr.
>
> Why are these files created, and is there any way to prevent this
> creation ?
> Thanks
> François

I thought this was fixed in 3.2.2 ???

James 

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

[Samba] Samba 3.2.4 and alternate data streams

[François Legal]

Hello, 
I just upgraded to 3.2.4, and today I observed in one of my share
that some of the file where being kind of duplicated with a trailing
":Zone.Identifier:$DATA" at the end of filename. 

I think this has to do with alternate data streams, but the point is
the share runs out of an XFS filesystem which is supposed to support
the xattr. 

Why are these files created, and is there any way to prevent this
creation ? 
Thanks 
François
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

Re: [Samba] Samba + NFS + APACHE + PHP5 + Symfony

[François Legal]

I think this is not so much samba related. Can't you just manage to make
the webserver user a member of a group, which samba users accessing the
files would also be member of ? Then you could only set the setgid bit on
directories, and that would do the trick.

On Wed, 10 Sep 2008 11:32:34 -0300, "Fabio da Silva Junior"
<[EMAIL PROTECTED]> wrote:
> Hello All, I'm new here so I expect to learn a lot using this mail list.
>  
> Let's directly to my problem.
>  
> I have here 2 servers, one running Apache + php5 + Symfony, and other
> server with Samba and nfs.
>  
> The web-server mount the data from the samba-server by nfs. there are
> developers that create and edit the data on the samba-server, but the
> Apache and Symfony create and edit data too, and i'm having serious
> troubles with permission.
>  
> The developers access de data by samba, with a single user. the
> web-server, when mount the data, have permissoin to write, but when he
> writes, the owner of the file is different from the owner in the samba
> server.
>  
> In other words, when the apache user write some data, the samba user
> cannot edit this data and vice-versa.
>  
> It's a little hard to explain, so i tried to make as easy as possible to
> show the problem.
>  
> I apreciate some help to solve this problem. 
>  
> Thanks for your atention
>  
> Att.
>  
>  
> Fábio da Silva Júnior - [EMAIL PROTECTED]
> Laboratório de Computação Aplicada - G10
> Laboratório de Redes
> UNIVALI - Universidade do Vale do Itajaí
>

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

Re: [Samba] Inexistant file displayed by samba

[François Legal]

I took some time to check the files in that share, and I finally found a
thumbs.db:encryptable file.
I guess this is a thumbnail cache file generated by Windows clients, but
what is this :encryptable part in the file name ?

After google through, it appears that this would be an alternate data
stream. Do I need this if I serve files only for non-macos clients ?
Can I disable this feature then ?

Thanks.

François

On Fri, 05 Sep 2008 07:50:55 +0800, Michael Heydon <[EMAIL PROTECTED]>
wrote:
> Oops, I should probably cc the list :(
> 
> 
>> You should look on your Samba server to see if there are funny looking
>> three letter files named "con" or "com" or such.
>>   
> It's not necessarily three letters, anything with a ":" or "\" in it's
> name will do the same thing.
> 
> *Michael Heydon - IT Administrator *
> [EMAIL PROTECTED] 

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

[Samba] Inexistant file displayed by samba

[François Legal]

Hello, 
Running 3.2.0, and in one of my share, a file named TABAFK~V
appeared, but is not present on the underlying filesystem. 

The file can't be removed from a windows client (even a member of
domain admins). 

Not that it is distrubing, but you know... 
François
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

Re: [Samba] created user picks up machine accounts

[François Legal]

How do you create the user account in your domain, and how did you create
the machine accounts ?

Can you check that (in your directory) the uidNumber of this user is not
the same as (or in the range of) the uidNumbers used for your machines
accounts. If the uidNumbers overlapn, then you've got your problem.

On Fri, 22 Aug 2008 17:36:26 +0300, "Mugo Martin" <[EMAIL PROTECTED]>
wrote:
> Hi all,
> 
> Have come across a strange error when setting up my samba users.
> 
> Set up a samba primary domain controller with an ldap backend and
migrated
> user profiles from another server
> 
> the process went well apart from a single user who after being created on
> samba authenticates OK but upon creation, gets immediately mapped onto an
> existing machine account on the server.
> 
> If I run su - user and smbclient -U user //host/user
> it goes fine but on asking whoami returns a machine account like 23-43$.
> 
> I have tried everything including deleting the account, profile and
> restarting the computer but everytime I recreate the account, it picks
> qualities of a machine account at random
> 
> Therefore, logging onto a profile always fails
> 
> I'm baffled, help...
> 
> Regards,
> Mugo
>

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

Re: [Samba] Samba 3.2 and MS Client 3.11 for DOS

[François Legal]

I don't know which previous version you used, but since 3.2 (I think),
samba defaults to replying only (maybe negotiating is more correct here)
protocol level starting with NTLM (whereas ms client 3.11 probably only
support lanman). Checking smb.conf manual... the 'lanman auth' parameter
now defaults to no, and that may cause your problem.
Try reverting it to yes, and that may help.

François

On Fri, 22 Aug 2008 22:39:02 +0800, imacat <[EMAIL PROTECTED]>
wrote:
> Dear all,
> 
> Sorry that this question might seem to be stupid.  Can MS Client
> 3.11 for DOS connect to Samba 3.2, and connect the network drive? It
> worked before, but not now.
> 
> Thank you very much in advance.
> 
> --
> Best regards,
> imacat ^_*' <[EMAIL PROTECTED]>
> PGP Key: http://www.imacat.idv.tw/me/pgpkey.asc
> 
> <> News: http://www.wov.idv.tw/
> Tavern IMACAT's: http://www.imacat.idv.tw/
> TLUG List Manager:
http://lists.linux.org.tw/cgi-bin/mailman/listinfo/tlug

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

[Samba] trustdom station can no more connect after upgrade to 3.2.0

[François LEGAL]

Hello,

I just upgrade from a 3.0.29 PDC that was trusting another domain, and since 
then, the TRUSTED domain users can no more access the shares on this server 
(nor browse users list or group list).
I did increase the log level to 4 and found the following entries :

[2008/07/22 11:48:46,  3, pid=9849, effective(0, 0), real(0, 0)] 
smbd/password.c:register_existing_vuid(314)
  register_existing_vuid: User name: TRUSTEDDOM\trusteduser Real name: 
Delphine Heslot
[2008/07/22 11:48:46,  3, pid=9849, effective(0, 0), real(0, 0)] 
smbd/password.c:register_existing_vuid(326)
  register_existing_vuid: UNIX uid 3010 is UNIX user TRUSTEDDOM\trusteduser, 
and will be vuid 100
[2008/07/22 11:48:46,  1, pid=9849, effective(0, 0), real(0, 0)] 
smbd/session.c:session_claim(112)
  Re-using invalid record
...
[2008/07/22 11:48:46,  0, pid=9849, effective(0, 0), real(0, 0)] 
libsmb/smb_signing.c:srv_check_incoming_message(754)
  srv_check_incoming_message: BAD SIG: seq 2 wanted SMB signature of
[2008/07/22 11:48:46,  0, pid=9849, effective(0, 0), real(0, 0)] 
libsmb/smb_signing.c:srv_check_incoming_message(758)
  srv_check_incoming_message: BAD SIG: seq 2 got SMB signature of
...
[2008/07/22 11:48:46,  3, pid=9849, effective(3010, 3012), real(3010, 0)] 
smbd/service.c:make_connection_snum(1190)
  trustedmachine (1.1.2.3) connect to service IPC$ initially as user 
TRUSTEDDOM\trusteduser (uid=3010, gid=3012) (pid 9849)
[2008/07/22 11:48:46,  3, pid=9849, effective(3010, 3012), real(3010, 0)] 
smbd/sec_ctx.c:set_sec_ctx(324)
  setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
[2008/07/22 11:48:46,  3, pid=9849, effective(0, 0), real(0, 0)] 
smbd/reply.c:reply_tcon_and_X(727)
  tconX service=IPC$
[2008/07/22 11:48:46,  3, pid=9849, effective(0, 0), real(0, 0)] 
smbd/process.c:smbd_process(2027)
  receive_message_or_smb failed: NT_STATUS_END_OF_FILE, exiting


while having a trusted user trying to connect to a share.

Any idea where this comes from ?





--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba