Re: [Samba] Upgraded samba, mostly still works, but have one issue

[Dale Schroeder]

On 12/12/2011 1:25 PM, Mark Casey wrote:

Dale,

That fixed it. Thanks very much for your time in looking at this 
issue! That leads to another question though. I don't get why 'winbind 
use default domain' did not cover the issue, since I have it set to 
yes. I assumed I could leave off the "DOMAIN\" portion and it would 
add it for me...but more specifically, even using DOMAIN\camera 
wouldn't work. I should clarify though that nowhere in my config am I 
actually typing "DOMAIN\"; I'm only swapping that in on the mailing 
list as a redaction. When I tried the fully qualified user account in 
the IP camera's config the domain matched the one that this samba 
server is joined to.


I did note this part in smb.conf's man page about 'winbind use default 
domain':
*"While this does not benifit Windows users, it makes SSH, FTP and 
e-mail function in a way much closer to the way they would in a native 
unix system.*"


This would all make more sense if that line means that 'winbind use 
default domain' excludes not only Windows users but *all* smb/cifs 
authentication attempts. Then, it wouldn't apply the the IP cameras at 
all. However even if that were the case I still can't explain the 
failure when I tried the user DOMAIN\camera.


Would you (or anyone) be able to provide any insight? Regardless, 
thanks again for your help thus far as I can now get this out of the 
urgent section of my list!


Thank you,
Mark


I don't know that I can explain it sufficiently, but I'll try.  
Essentially, "map untrusted to domain" was a new parameter to make Samba 
perform as it did prior to 3.4.  "winbind use default name" refers to 
something completely different.  As the man page indicates, I can ssh 
into the system as "valid_user" instead of DOMAIN\valid_user.  This 
applies to a valid user on a domain host.  On the other hand, since the 
cameras are not able to join the domain, the new parameter maps 
HOSTNAME\camera to DOMAIN\camera.


Others have explained "winbind use default domain" this way:

http://wiki.samba.org/index.php/Samba_&_Active_Directory
|winbind use default domain = Yes| removes the domain prefix from 
usernames, so you can login as /Username/ instead of /DOMAIN\Username/ 
or in some cases /DOMAIN+Username/ (see next explanation).


http://www.justlinux.com/forum/archive/index.php/t-118512.html
This winbind parameter eliminates the need to use the domain name with 
the user/group name. The domain name plus the separator will 
automatically be prepended to the user name.


Not perfect, but I hope it helps.

Dale



On 12/12/2011 12:23 PM, Dale Schroeder wrote:

On 12/12/2011 10:14 AM, Mark Casey wrote:

Hello list,

I recently upgraded an Ubuntu 8.04 LTS samba server to 10.04 LTS 
which took the installed version of samba from version 3.0.28a to 
version 3.4.7. The server is an AD member using idmap-rid. I have 
updated the idmap directives in the config and it mostly worked 
(winbind works, Windows users can get to their shares with their 
correct permissions, etc.). The only thing that got broken is the 
ability of our IP security cameras to store data directly to the 
server through samba. I believe this may have been caused by a 
change to a default setting, such as the  allowed authentication 
methods or possibly something like 'allow trusted domains', since 
these cameras are not capable of actually joining the domain. I've 
looked at some of the in-between release notes but no changes have 
jumped out at me.


The cameras are configured to connect to the given smb/cifs server 
and share (which exists and can be mapped from Windows if you use 
the right user). The share ('camshare') has share-level permissions 
set such that DOMAIN\camera should have full access. I have winbind 
set to use the default domain so the cameras are configured to 
connect as 'camera' instead of 'DOMAIN\camera' (but I've tried both 
anyway, to no avail). I have checked the password on the 'camera' 
account repeatedly.


However you can see that something isn't right when the cameras try 
to mount the share:

root@server:~# tail -f /var/log/samba/log.smbd | grep camera
  check_ntlm_password:  Authentication for user [camera] -> 
[camera] FAILED with error NT_STATUS_NO_SUCH_USER
  check_ntlm_password:  Authentication for user [camera] -> 
[camera] FAILED with error NT_STATUS_NO_SUCH_USER
  check_ntlm_password:  Authentication for user [camera] -> 
[camera] FAILED with error NT_STATUS_NO_SUCH_USER


If I use that username with the password when mapping the share from 
Win7, it works and the correct permissions are there.


Here is the smb.conf:

[global]
server string = File Server
workgroup = DOMAIN
realm = DOMAIN.COM
security = ADS
password server = *
#password server = dc1.domain.com
username map = /etc/samba/smbusers
obey pam restrictions = Yes
enable privileges = Yes
map to guest = Bad User
client NTLMv2 auth = Yes
log le

[Samba] Fwd: Upgraded samba, mostly still works, but have one issue

[Mark Casey]

Forgot to cc list. Sorry

Sent via mobile

Begin forwarded message:

> From: Mark Casey 
> Date: December 12, 2011 1:25:34 PM CST
> To: Dale Schroeder 
> Subject: Re: [Samba] Upgraded samba, mostly still works, but have one issue
> 

> Dale,
> 
> That fixed it. Thanks very much for your time in looking at this issue! That 
> leads to another question though. I don't get why 'winbind use default 
> domain' did not cover the issue, since I have it set to yes. I assumed I 
> could leave off the "DOMAIN\" portion and it would add it for me...but more 
> specifically, even using DOMAIN\camera wouldn't work. I should clarify though 
> that nowhere in my config am I actually typing "DOMAIN\"; I'm only swapping 
> that in on the mailing list as a redaction. When I tried the fully 
> qualified user account in the IP camera's config the domain matched the one 
> that this samba server is joined to.
> 
> I did note this part in smb.conf's man page about 'winbind use default 
> domain':
> "While this does not benifit Windows users, it makes SSH, FTP and e-mail 
> function in a way much closer to the way they would in a native unix system."
> 
> This would all make more sense if that line means that 'winbind use default 
> domain' excludes not only Windows users but all smb/cifs authentication 
> attempts. Then, it wouldn't apply the the IP cameras at all. However even if 
> that were the case I still can't explain the failure when I tried the user 
> DOMAIN\camera.
> 
> Would you (or anyone) be able to provide any insight? Regardless, thanks 
> again for your help thus far as I can now get this out of the urgent section 
> of my list!
> 
> Thank you,
> Mark
> 
> 
> On 12/12/2011 12:23 PM, Dale Schroeder wrote:
>> 
>> On 12/12/2011 10:14 AM, Mark Casey wrote:
>>> 
>>> Hello list, 
>>> 
>>> I recently upgraded an Ubuntu 8.04 LTS samba server to 10.04 LTS which took 
>>> the installed version of samba from version 3.0.28a to version 3.4.7. The 
>>> server is an AD member using idmap-rid. I have updated the idmap directives 
>>> in the config and it mostly worked (winbind works, Windows users can get to 
>>> their shares with their correct permissions, etc.). The only thing that got 
>>> broken is the ability of our IP security cameras to store data directly to 
>>> the server through samba. I believe this may have been caused by a change 
>>> to a default setting, such as the  allowed authentication methods or 
>>> possibly something like 'allow trusted domains', since these cameras are 
>>> not capable of actually joining the domain. I've looked at some of the 
>>> in-between release notes but no changes have jumped out at me. 
>>> 
>>> The cameras are configured to connect to the given smb/cifs server and 
>>> share (which exists and can be mapped from Windows if you use the right 
>>> user). The share ('camshare') has share-level permissions set such that 
>>> DOMAIN\camera should have full access. I have winbind set to use the 
>>> default domain so the cameras are configured to connect as 'camera' instead 
>>> of 'DOMAIN\camera' (but I've tried both anyway, to no avail). I have 
>>> checked the password on the 'camera' account repeatedly. 
>>> 
>>> However you can see that something isn't right when the cameras try to 
>>> mount the share: 
 root@server:~# tail -f /var/log/samba/log.smbd | grep camera 
   check_ntlm_password:  Authentication for user [camera] -> [camera] 
 FAILED with error NT_STATUS_NO_SUCH_USER 
   check_ntlm_password:  Authentication for user [camera] -> [camera] 
 FAILED with error NT_STATUS_NO_SUCH_USER 
   check_ntlm_password:  Authentication for user [camera] -> [camera] 
 FAILED with error NT_STATUS_NO_SUCH_USER 
>>> 
>>> If I use that username with the password when mapping the share 
>>> from Win7, it works and the correct permissions are there. 
>>> 
>>> Here is the smb.conf: 
 [global] 
 server string = File Server 
 workgroup = DOMAIN 
 realm = DOMAIN.COM 
 security = ADS 
 password server = * 
 #password server = dc1.domain.com 
 username map = /etc/samba/smbusers 
 obey pam restrictions = Yes 
 enable privileges = Yes 
 map to guest = Bad User 
 client NTLMv2 auth = Yes 
 log level = 2, vfs:1 
 syslog = 0 
 max log size = 0 
 load printers = No 
 preferred master = No 
 local master = No 
 domain master = No 
 dns proxy = No 
 disable netbios = yes 
 ldap ssl = no 
 host msdfs = No 
 template shell = /bin/false 
 winbind enum users = Yes 
 winbind enum groups = Yes 
 winbind use default domain = Yes 
 winbind refresh tickets = Yes 
 
 idmap backend = tdb 
 idmap uid = 10-19 
 

Re: [Samba] Upgraded samba, mostly still works, but have one issue

[Dale Schroeder]

On 12/12/2011 10:14 AM, Mark Casey wrote:

Hello list,

I recently upgraded an Ubuntu 8.04 LTS samba server to 10.04 LTS which 
took the installed version of samba from version 3.0.28a to version 
3.4.7. The server is an AD member using idmap-rid. I have updated the 
idmap directives in the config and it mostly worked (winbind works, 
Windows users can get to their shares with their correct permissions, 
etc.). The only thing that got broken is the ability of our IP 
security cameras to store data directly to the server through samba. I 
believe this may have been caused by a change to a default setting, 
such as the  allowed authentication methods or possibly something like 
'allow trusted domains', since these cameras are not capable of 
actually joining the domain. I've looked at some of the in-between 
release notes but no changes have jumped out at me.


The cameras are configured to connect to the given smb/cifs server and 
share (which exists and can be mapped from Windows if you use the 
right user). The share ('camshare') has share-level permissions set 
such that DOMAIN\camera should have full access. I have winbind set to 
use the default domain so the cameras are configured to connect as 
'camera' instead of 'DOMAIN\camera' (but I've tried both anyway, to no 
avail). I have checked the password on the 'camera' account repeatedly.


However you can see that something isn't right when the cameras try to 
mount the share:

root@server:~# tail -f /var/log/samba/log.smbd | grep camera
  check_ntlm_password:  Authentication for user [camera] -> [camera] 
FAILED with error NT_STATUS_NO_SUCH_USER
  check_ntlm_password:  Authentication for user [camera] -> [camera] 
FAILED with error NT_STATUS_NO_SUCH_USER
  check_ntlm_password:  Authentication for user [camera] -> [camera] 
FAILED with error NT_STATUS_NO_SUCH_USER


If I use that username with the password when mapping the share from 
Win7, it works and the correct permissions are there.


Here is the smb.conf:

[global]
server string = File Server
workgroup = DOMAIN
realm = DOMAIN.COM
security = ADS
password server = *
#password server = dc1.domain.com
username map = /etc/samba/smbusers
obey pam restrictions = Yes
enable privileges = Yes
map to guest = Bad User
client NTLMv2 auth = Yes
log level = 2, vfs:1
syslog = 0
max log size = 0
load printers = No
preferred master = No
local master = No
domain master = No
dns proxy = No
disable netbios = yes
ldap ssl = no
host msdfs = No
template shell = /bin/false
winbind enum users = Yes
winbind enum groups = Yes
winbind use default domain = Yes
winbind refresh tickets = Yes

idmap backend = tdb
idmap uid = 10-19
idmap gid = 10-19
idmap config DOMAIN:backend = rid
idmap config DOMAIN:range = 10 - 50
idmap config DOMAIN:default = yes

hosts allow = 10.0.1.0/255.255.255.0 10.1.1.0/255.255.255.0 
10.2.0.0/255.255.255.0 10.0.8.0/255.255.255.0 10.1.8.0/255.255.255.0 
10.2.8.0/255.255.255.0 172.10.0.0/255.255.255.0 172.11.0.0/255.255.255.0

map acl inherit = No
hide special files = Yes
map archive = No
map readonly = No
map system = No
map hidden = No
force create mode = 707
force directory mode = 707
ea support = No
store dos attributes = No
wide links = No
follow symlinks = No
dos filemode = No
add share command=/etc/samba/command.pl
delete share command=/etc/samba/command.pl
change share command=/etc/samba/command.pl

[camshare]
comment = Camera data share
path = /home/camshare
read only = No
writeable = Yes
inherit owner = Yes
guest ok = No

[mainshare]
comment = Main Fileshare
path = /home/mainshare
read only = No
writeable = Yes
inherit owner = Yes
guest ok = Yes

vfs objects = recycle extd_audit
recycle:repository = Recycle Bin
recycle:directory_mode = 707
recycle:keeptree = yes
recycle:versions = no
recycle:touch = yes
recycle:touch_mtime = no
recycle:maxsize = 209715200
recycle:exclude = *.tmp *.temp ~$* *.~??


I've left off some other shares that don't seem relevant.

I can provide other info and or more logs if needed. Thanks in advance 
for any assistance you may be able to provide.


Thank you,
Mark



Mark,

Try adding the parameter "map untrusted to domain = Yes"


 map untrusted to domain (G)

   If a client connects to smbd using an untrusted domain name, such as
   BOGUS\user, smbd replaces the BOGUS domain with it's SAM name before
   attempting to authenticate that user. In the case where smbd is
   acting as a

[Samba] Upgraded samba, mostly still works, but have one issue

[Mark Casey]

Hello list,

I recently upgraded an Ubuntu 8.04 LTS samba server to 10.04 LTS which 
took the installed version of samba from version 3.0.28a to version 
3.4.7. The server is an AD member using idmap-rid. I have updated the 
idmap directives in the config and it mostly worked (winbind works, 
Windows users can get to their shares with their correct permissions, 
etc.). The only thing that got broken is the ability of our IP security 
cameras to store data directly to the server through samba. I believe 
this may have been caused by a change to a default setting, such as the  
allowed authentication methods or possibly something like 'allow trusted 
domains', since these cameras are not capable of actually joining the 
domain. I've looked at some of the in-between release notes but no 
changes have jumped out at me.


The cameras are configured to connect to the given smb/cifs server and 
share (which exists and can be mapped from Windows if you use the right 
user). The share ('camshare') has share-level permissions set such that 
DOMAIN\camera should have full access. I have winbind set to use the 
default domain so the cameras are configured to connect as 'camera' 
instead of 'DOMAIN\camera' (but I've tried both anyway, to no avail). I 
have checked the password on the 'camera' account repeatedly.


However you can see that something isn't right when the cameras try to 
mount the share:

root@server:~# tail -f /var/log/samba/log.smbd | grep camera
  check_ntlm_password:  Authentication for user [camera] -> [camera] 
FAILED with error NT_STATUS_NO_SUCH_USER
  check_ntlm_password:  Authentication for user [camera] -> [camera] 
FAILED with error NT_STATUS_NO_SUCH_USER
  check_ntlm_password:  Authentication for user [camera] -> [camera] 
FAILED with error NT_STATUS_NO_SUCH_USER


If I use that username with the password when mapping the share from 
Win7, it works and the correct permissions are there.


Here is the smb.conf:

[global]
server string = File Server
workgroup = DOMAIN
realm = DOMAIN.COM
security = ADS
password server = *
#password server = dc1.domain.com
username map = /etc/samba/smbusers
obey pam restrictions = Yes
enable privileges = Yes
map to guest = Bad User
client NTLMv2 auth = Yes
log level = 2, vfs:1
syslog = 0
max log size = 0
load printers = No
preferred master = No
local master = No
domain master = No
dns proxy = No
disable netbios = yes
ldap ssl = no
host msdfs = No
template shell = /bin/false
winbind enum users = Yes
winbind enum groups = Yes
winbind use default domain = Yes
winbind refresh tickets = Yes

idmap backend = tdb
idmap uid = 10-19
idmap gid = 10-19
idmap config DOMAIN:backend = rid
idmap config DOMAIN:range = 10 - 50
idmap config DOMAIN:default = yes

hosts allow = 10.0.1.0/255.255.255.0 10.1.1.0/255.255.255.0 
10.2.0.0/255.255.255.0 10.0.8.0/255.255.255.0 10.1.8.0/255.255.255.0 
10.2.8.0/255.255.255.0 172.10.0.0/255.255.255.0 172.11.0.0/255.255.255.0

map acl inherit = No
hide special files = Yes
map archive = No
map readonly = No
map system = No
map hidden = No
force create mode = 707
force directory mode = 707
ea support = No
store dos attributes = No
wide links = No
follow symlinks = No
dos filemode = No
add share command=/etc/samba/command.pl
delete share command=/etc/samba/command.pl
change share command=/etc/samba/command.pl

[camshare]
comment = Camera data share
path = /home/camshare
read only = No
writeable = Yes
inherit owner = Yes
guest ok = No

[mainshare]
comment = Main Fileshare
path = /home/mainshare
read only = No
writeable = Yes
inherit owner = Yes
guest ok = Yes

vfs objects = recycle extd_audit
recycle:repository = Recycle Bin
recycle:directory_mode = 707
recycle:keeptree = yes
recycle:versions = no
recycle:touch = yes
recycle:touch_mtime = no
recycle:maxsize = 209715200
recycle:exclude = *.tmp *.temp ~$* *.~??


I've left off some other shares that don't seem relevant.

I can provide other info and or more logs if needed. Thanks in advance 
for any assistance you may be able to provide.


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

Re: [Samba] PDC & file server on same machine?

[Gaiseric Vandal]

Windows clients will give preference to a BDC (if available) when 
selecting a logon server over a PDC.


On 12/08/2011 08:36 AM, Aaron E. wrote:
I have a s3.4 pdc with a bdc,, pdc is serving around 80 users on 
terminal services and another 50 fat clients,,, acts as the file 
server.. roaming profiles etc... I have no issues other than the 
network card only being 100mb,, I do have a throughput issues.. but 
that is on the table..


On 12/07/2011 06:03 PM, John Heim wrote:

How much of a resource hog is a PDC? My understanding is that
authentication is done vs a BDC if available. I configured my new file
server as the domain PDC because I figured it would already have to run
samba. I have two other machines configured as BDCs to serve as logon
servers.

I'm looking for opinions on whether I'm asking for performance problems
by making my file server the PDC. Actually, this machine is already
serving as PDC but its not in production yet as a file server. So right
now, its just the domain PDC. When I log into the domain and "echo
%logonserver%", it shows that one of the BDCs was the logon server, not
the PDC. It doesn't look like the PDC has to do anything but handle
joining machines to the domain.








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

[Samba] print queue document count never resets

[Joe]

Running 3.5.8 on Ubuntu 11.04.

I have lpr set up and here is my print command...
lpr -r -P'%p' %s

The document count as shown in the windows "printers and faxes" never
resets back to zero after the documents are printed.  Even when the
queue is empty it will show 1000's of jobs.  I have to right click on
the printer and "cancel all documents" then press F5 to refresh the
view.  F5 will not do it alone.  Is there some way to change this
behavior?
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

[Samba] Allow a machine account to access a share?

[Zsombor Nagy]

Hi!

There was a mail with a very similar problem recently. I have a samba PDC with 
one share, and a win2003 machine (which is in the samba's domain) where a 
service is running, which for some reason tries to access this share as the 
system account, which maps as guest on the samba side, and gets rejected.

I can see this line in the log:

[2011/12/12 11:47:14.959209,  3] libsmb/ntlmssp.c:747(ntlmssp_server_auth)
Got user=[] domain=[] workstation=[ABC] len1=1 len2=0

So samba knows about that this is the machine called ABC.

Is it possible to allow this empty user from the ABC machine to access the 
share?

This is the share part of my config:


[abcdata]
path = /path/to/abc
valid users = abcuser
read only = No


I have not much control over this service, so I cannot make it use a proper 
username/password. And I don't want to open this share for guests.



Any help or hint would be very appreciated!

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

Re: [Samba] sambaMungedDial

[Adam Tauno Williams]

On Mon, 2011-12-12 at 11:22 +0100, Alexander Födisch wrote:
> Hi,
> 
> does anybody know how to decode/recode sambaMungedDial attribute? I need to 
> store the terminal server profile path in it 
> but can not find any documentation.

There are a couple of applications that decode/encode sambaMungedDial.
Looking at their source(s) might help.

For example

-- 
System Administrator / OpenGroupware developer: awill...@whitemice.org


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

Re: [Samba] (no subject)

[Adam Tauno Williams]

On Mon, 2011-12-12 at 09:53 +0100, Molo CoC wrote:
> iam using samba 4 (apt -get -> Ubunt 11.04) and did the provision with 
> --ldap-backend-type=openldap .
> It generates a slapd file and included a modul called: rndval
> which can not be located.
> it tryed it again with compiling samba 4 from source, and the same, no module 
> rndval for ldap.

The Samba4 LDAP backend no longer works; it hasn't worked for some time
and is not longer expected to work.  



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

[Samba] Samba 4, can't logon

[steve]

Hi everyone

I have Samba 4 running with this:

smb.conf

[global]
server role = domain controller
workgroup = HH3SITE
realm = hh3.hh1.site
netbios name = HH3
passdb backend = samba4

[netlogon]
path = /usr/local/samba/var/locks/sysvol/hh3.hh1.site/scripts
read only = No

[sysvol]
path = /usr/local/samba/var/locks/sysvol
read only = No

[home]
path = /home/HH3SITE
read only = No

I created a Samba 4 user called lynn:
wbinfo -i lynn
HH3SITE\lynn:*:309:100::/home/HH3SITE/lynn:/bin/false

I created the directory 309:100 /home/HH3SITE/lynn


Samba can see the shares:

smbclient -L hh3 -Uadministrator
Password for [HH3SITE\administrator]:

   Sharename   Type   Comment
-      ---
netlogonDisk
sysvol  Disk
homeDisk
IPC$IPCIPC Service
REWRITE: list servers not implemented

But lynn can't logon:

 smbclient //localhost/home -Ulynn
Password for [HH3SITE\lynn]:
Connection to \\localhost\home failed - NT_STATUS_INTERNAL_ERROR

The administrator can't logon either:
smbclient //localhost/netlogon -Uadministrator
Password for [HH3SITE\administrator]:
Connection to \\localhost\netlogon failed - NT_STATUS_INTERNAL_ERROR

I tried changing permissions to 0777:

ls -la /home/HH3SITE
total 12
drwxrwxrwx 3 rootroot  4096 Dec 11 17:42 .
drwxr-xr-x 4 rootroot  4096 Dec 12 11:01 ..
drwxrwxrwx 2 309 users 4096 Dec 11 17:42 lynn

But still no logon.

What am I doing wrong?
Thanks
Steve

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

[Samba] sambaMungedDial

[Alexander Födisch]

Hi,

does anybody know how to decode/recode sambaMungedDial attribute? I need to store the terminal server profile path in it 
but can not find any documentation.



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

Re: [Samba] (no subject)

[Matthieu Patou]

On 12/12/2011 10:55, Molo CoC wrote:

thanks for your answer.
that mean, the whole replication process works inside Samba4.
i am currently learning ldap for lpic 301, an there are 15 pages which descripe 
how to replicate via ldap ->  samba users and setup a secondary dc controller.

what about samba 3.5 can i still use ldap as backend there, or same as samba 4, 
not longer supported 'ldap'
It's two different things, samba 3.x as a NT domain controller can use 
openldap because the constraints on the schema are not the same as the 
constraints for a AD domain controller.

and if so, what is the recommend backend type yet ?
When using samba4 as AD domain controller you have the option for using 
just the ldb backend and using the standard DRS for DC to DC replication.



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

Re: [Samba] (no subject)

[Matthieu Patou]

On 12/12/2011 09:53, Molo CoC wrote:

Hey all,

iam using samba 4 (apt -get ->  Ubunt 11.04) and did the provision with 
--ldap-backend-type=openldap .
It generates a slapd file and included a modul called: rndval
which can not be located.
it tryed it again with compiling samba 4 from source, and the same, no module 
rndval for ldap.

Do not use the openldap backend we don't support this configuration anymore.

unfotunatly i cannot find the Modul inside the system or somewhere else to 
download
i hope you can give me an advice

Matthieu.

--
Matthieu Patou
Samba Team
http://samba.org

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

[Samba] (no subject)

[Molo CoC]

Hey all,

iam using samba 4 (apt -get -> Ubunt 11.04) and did the provision with 
--ldap-backend-type=openldap .
It generates a slapd file and included a modul called: rndval
which can not be located.
it tryed it again with compiling samba 4 from source, and the same, no module 
rndval for ldap.

unfotunatly i cannot find the Modul inside the system or somewhere else to 
download
i hope you can give me an advice

thanks
___
SMS schreiben mit WEB.DE FreeMail - einfach, schnell und
kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba