similar to: samba 3.4.3 DC breaks Windows groups

I have the following setup: PDC: Samba 3.0.37 on Solaris 10 BDC1: Samba 3.0.37 on Solaris 10 BDC2: Samba 3.4.3 on Solaris 10 Samba 3.0.37 is the bundled version of Samba. Samba 3.4.3 is compiled from source. BDC2 is a recent addition to the network. All machine use LDAP as the backend for everything. They use winbind to handle a domain trust with another domain, but otherwise

Hello, hello I'm writing you this email because when i want to set up a password policy with LDAP, this one isn't recognize by samba. In the log i've got this : ldapsam_getgroup: Did not find group, filter was (&(objectClass=sambaGroupMapping)(sambaSID=S-1-5-11)) ldapsam_getgroup: Did not find group, filter was (&(objectClass=sambaGroupMapping)(sambaSID=S-1-5-2))

I am running Samba 3.5.5 on Solaris 10. I have one machine as a PDC, one as a BDC. If I logon to the domain from a Windows 7 Pro (64-bit) laptop, hibernate the machine, unplug the network cable and wake the machine, I can not unlock the screen. I will get the message "There are currently no logon servers available to service the logon request." Other users have reported this.

I am running Samba ver 3.0.33 on Solaris 10 (sparc.) Initially I had the server configured as a domain controller with the "passdb backend = tdbsam" option. The underlying unix accounts were stored in LDAP (Sun Directory Server.) Those accounts are also used for non-Samba services. Since I have domain trusts with NT domains, I am using winbind and idmapping. The idmap data was

I don't have an AD backend for this domain. The DC's are "classic" domain controllers, Samba 3.6 , with LDAP backend for all accounts. Would this still be an option? I tried adding idmap config MYDOMAIN:schema_mode = rfc2307 idmap config MYDOMAIN:backend = ad idmap config MYDOMAIN:range = 100-300 Didn't seem to work. Thanks On 12/18/14 11:57, Rowland

I have a samba domain with a Samba 3.4.x PDC (compiled from source on Solaris 10) and two Samba 3.0.x BDC's (Sun-bundled Samba on Solaris 10.) XP clients use DHCP. When on the LAN, DHCP includes WINS server (the WINS server is one of the Samba 3.0.x machines.) We also have a VPN for remote client access for Windows XP machines. XP machines could include home PC's (not in the domain)

I think IDMAP_RID would not be the appropriate solution for me. Not only do I want consistent IDMapping across all servers - which this could do - but I want them to match the the existing unix uidNumber in LDAP. Thanks for your help. On 12/18/14 04:29, Rowland Penny wrote: > On 17/12/14 22:01, Gaiseric Vandal wrote: >> I have two Samba 3.6.24 domain controllers (Solaris

> > > Adding pdc1 to the hosts file (c:\windows\system32\drivers\etc\hosts) > did > not make a difference. After adding pdc1 to lmhosts, "net use > \\pdc1" did > work. So in the case of pdc1 one, the name is being resolved as a > netbios > name (i.e. via lmhosts) not a tcp/ip type name (i.e. via dns or hosts) > > But then why does "net

I have two Samba 3.6.24 domain controllers (Solaris 10.) On all machines unix accounts and groups are in the LDAP as well as idmap entries for trusted domains. Samba accounts on domain controllers are in LDAP so there is problem with consistency unix/windows id and group mapping on the domain controllers. The domain controllers are the main file servers as well. I am configuring a

Hi all, I've been using samba for a few years now on a couple of file servers with a tdbsam backend for our user accounts. We use openldap for the vast majority of our identity management, so I would love to be able to tie into this. We recently started using sambaNTPassword in openldap for radius authentication, so this is populated for most of our users now. >From reading through

I am running Samba ver 3.0.37 on Solaris 10 (sparc) as a PDC with LDAP for the backend for both samba and unix accounts. Assume the samba SMBPDC is called "PDC." I have also set up a trust with an Windows domain- lets call it WINDOMAIN- (the PDC for the Windows domain is Win 2003 but is in mixed mode for backwards compat.) The SAMBA domain trusts the WINDOWS domain, not not vice

Good Morning I am looking to download the Samba 3.0.23d binary for Solaris. When I go to the area that is set up for binaries, there is nothing under the Sparc folder. Is there another place I can get the binary? Thanks in advance for your help. Barb Fair Lockheed Martin Valley Forge, PA 610-531-5442

Hi, we are using SAMBA 3.6.1-1 (updating this archlinux machine is tooo ugly) and 3.6.6-1 on archlinux with the LDAP (Server version is 2.4.26-3) backend and manage the users, groups and computer by using the smbldap-tools. Currently we are experiencing the following problems: 1. changing the passwords takes longer than 30 seconds <- That's bad because we are using a gigabit ethernet

Samba 4.x, DC. Em 16/01/2015 16:37, "Gaiseric Vandal" <gaiseric.vandal at gmail.com> escreveu: > Is this samba 3.x or 4.x? DC or member server? > > I found for samba 3.x it was better to not explicitly define any ports in > smb.conf. > > > > > > > On 01/16/15 13:25, Thiago Ten?rio wrote: > >> Hi, >> >> I need to enable smb

When I run check_multiple_LDAP_entries.pl script I get the following message: # perl check_multiple_LDAP_entries.pl -h localhost -b dc=w3,dc=lan -D cn=root,dc=w3,dc=lan -w 1234567 -l testing for multiple sambaSids No multiple sambaSids found in your system -------------------------------------------------------------------------------- testing for multiple gidNumbers No multiple gidNumbers

If this is an NT4-style domain, then DNS is not essential. Things like SRV records aren't relevant since a lot of the NT4 is back from the NetBios days. It looks like your Win 10 machine thinks it is trying to join an AD domain. Windows clients machines typically are using DNS to resolve server names to IP addresses. However DNS does not provide info on locating PDC's

When I enable server signing in Samba (server signing = mandatory), I can still join a Window 7 machine to the domain but I am no longer able to log on into the domain using a domain user. Is this normal? I am using Samba 3.6.3 on Linux 12.04. Is there anything that needs to be configured on the Windows machine? Thanks, Ali

I have the following PDC: Samba 3.0.37 on Solaris 10 BDC1: Samba 3.0.37 on Solaris 10 PDC is configured to be the WINS server for everything, including XP Pro clients and other Samba machines. PDC# testparm -v | grep master Load smb config files from /etc/sfw/smb.conf ... Server role: ROLE_DOMAIN_PDC ... Press enter to see a dump of your service definitions preferred

I currently have several fresh installs of XP that will connect to shares, but will not reconnect after a workstation reboot. These are workstations that are not joined to the domain. Only accessing shares from a local profile, but using the same user/pass to login as to connect to Samba. I get various errors at that point. Upon reboot, attempting to access the share generates: "An error

I prepared samba PDC and not able to join windows 10 clients. Please suggest any windows 10 registry settings.