search for: ingeominas

...ion defined in smb.conf: encrypt passwords = yes ldap passwd sync = Yes passwd program = /usr/local/sbin/smbldap-passwd -u %u passwd chat = "Changing password for*\nNew password*" %n\n "*Retype new password*" %n\n" passdb backend = ldapsam:ldap://ldapserver.ingeominas.gov.co/ and this is the setup in smbldap.conf: # Unix password encryption (CRYPT, MD5, SMD5, SSHA, SHA, CLEARTEXT) hash_encrypt="CRYPT" So, I don't know why windows is changing the password in SSHA format. I appreciate your help. Pablo Chamorro -- Tel: +57 (2) 7314752/3222/2595...

Hello! Accidentally deletes the file daemon, / usr / lib / samba / classic / smbd. Now I can not start Samba, Samba reinstalling again in the newer version I would lose my settings? It will overwrite existing files or just bring back the excluded? I use a distribution derived from Suse, when I try to install the yast he asks that some libraries are installed: *libstdc + + **libstdc + +-devel

We are in the point of change our samba 3.0.5 PDC setup in order to make it authenticate its users against openldap 2.3.11. We already have the openldap server working with all the PDC users data and we also have already tested the wanted scenario using an identical PDC setuped up with the same SID and its netbios name changed and some PCs for testing as domain clients (we outsourced this

My samba PDC is working very well. I only have an 'theoretical' question (I think). When I run 'net getlocalsid my-pdc', it fails (see below). I think this is because someday the name of my pdc was other! In fact 'net getlocalsid my-old-pdc-name' works! and that output is the same output obtained from running 'net getlocalsid my-domain' (as written on the

Could somebody please tell me how can I know what computers of one local network are setuped up as master browsers for a local workgroup? I mean, is it possible to use nmblookup or other command for this? what parameters are needed? I'm having problems with a workgroup for which smbclient -L server gives different results every certain time, e.g. from one week to another the results

We are considering to update our Samba 3.0.5 PDC to 3.0.21 using samba-3.0.21b-1.i386.rpm, and rpm -Uvh --test works. Whe have openldap 2.3.11 as passwd backend with samba.schema taken from samba-3.0.14 but reading the docs (Samba-3 to Samba-3 Updates on the Same Server) it states: "it is necessary only to update the LDAP schema". How the LDAP schema updated and the ldap databases

We have samba 3.0.21c + openldap working ok. Some weeks ago I got this answer (http://marc.theaimsgroup.com/?l=samba&m=113164752004902&w=2) to my question about whether it's better to have one or multiple windows domains, in favor of having only one domain. Now, we're gonna put into production a NAS box (one Windows Storage Server) for our main domain and for our whole

I installed a PDC some days ago for some 15 users/PCs (w98,2000,xp), with samba 3.0.23b-1 and valid users wasn't working. I'm going to update to 3.0.23c which solves that problem. I'm using smbpasswd passdb backend. In /etc/group I have only two groups. I don't understand very well the changes related to primaryGroupSID and RID commented in previous posts. Please, is it

I was trying to join a windows xp machine to a new domain's PDC setuped with samba 3.0.23c and openldap 2.3.11 as backend but I noted that only the posix acount part is created, not the sambaSamAccount: [root]# pdbedit -a -m -u sistemas-33$ -d10 -- snip -- error: Object class violation (object class 'sambaSamAccount' requires attribute 'sambaSID') -- snip -- I understand

Some days ago we were able to add machines to our Samba+OpenLDAP domain, but after we decided to update samba from 3.0.5a to 3.0.21c now we can't do that anymore!. In adding a machine, the "wellcome to domain XXX" message appears, but after rebooting the machine it doesn't works!. Looking the openldap entries, now we are having these kind of entries: sambaSID:

In the headquarter of my Institution we have some 300 windows PCs, distributed like this: domain1: 100 clients in a consolidated samba 3.0.5-2 domain (RH 9.0) domain2: 20 clients in an incipient samba 3.0.14a-2 domain (FC4) 80 clients to be joined to domain2 without domain: 150 clients beloging to some three workgroups We outsourced the deployment of a LDAP server and we are in the

I installed samba4wins on two of my Fedora Core 3 servers (from src rpm), on one PDC (samba 3.0.21c) and on one standalone server without samba, in order to test samba4wins. I think I managed to install and to setup properly the software but it seems nmblookup is not working on the PDC samba: [user]$ nmblookup '*' querying * on 192.168.19.255 name_query failed to find name *

I have four domains in my LAN. I set up trust relationships for the domains, having each PDC working as wins server for each domain but I hd not set up winbind. I have samba3-3.3.12 + ldap (openldap 2.4.21) as users backend. I mean, I have wins support = yes for each PDC, and I can access to the shared folders of each PDC from any windows computer from my LAN. The problem is accessing to