search for: bhuntsman

So, if I read this right, Samba4 should be able to participate as a domain controller, if I specify the option --with-ads, right? I'm using the following options: --with-winbind --with-swat --with-ads --with-ldap --with-acl-support --with-dnsupdate --with-aio-support --prefix=/opt/samba-4.0.0 --sysconfdir=/etc/samba-4.0.0 --localstatedir=/var/samba-4.0.0 The configure script pukes at the

On 19/02/15 05:42, Craig Green wrote: > Benjamin Huntsman <BHuntsman <at> mail2.cu-portland.edu> writes: > >> So, if I read this right, Samba4 should be able to participate as a domain > controller, if I specify the option >> --with-ads, right? >> >> I'm using the following options: >> >> --with-winbind >>...

Benjamin Huntsman <BHuntsman <at> mail2.cu-portland.edu> writes: > > So, if I read this right, Samba4 should be able to participate as a domain controller, if I specify the option > --with-ads, right? > > I'm using the following options: > > --with-winbind > --with-swat > --with-ads...

I'm getting killed this morning, since we did a Samba upgrade to one of our production servers this weekend and didn't expect this one. I have one share that I need unauthenticated access to from a few named workstations. Here's the config: # Samba config file created using SWAT # from UNKNOWN (x.x.x.x) # Date: 2013/03/18 14:25:33 [global] encrypt passwords = No map to guest =

So, I have "working" builds of Samba 3.6.10, and 4.0.2 using the traditional build system on AIX, both built with XLC. For historical reasons, we're needing to use 'encrypt passwords = no', so that Samba uses the OS password. The odd thing, is, the 3.6.10 Samba works just fine, but the 4.0.2 doesn't allow connections. Here's the Samba config I'm using on both:

Helpp! :) We didn't catch this in testing and now it's killing me in production! I'm getting stuck with my fresh build of Samba 3.6.10. It isn't honoring groups specified in the valid users clause of the share configuration. I'm running in security = SHARE mode, and user authentication is working just fine. Even if I specify individual users on the valid users = line, it

Hi all! I''m hoping someone here might be able to help. I''m familiar with several UNIX''es, though farily new to Linux... I''m running RHEL 5.2. I''ve got the RHEL kernel headers installed, etc, and compiled xen-3.3. Once that was built, I rebuilt libvirt, etc, the kernel, and all the modules. The whole mess boots and runs fine... mostly. My hardware

Hi all! I''m hoping someone here can help me out. I''ve got a "fresh" install of OpenSolaris 2009.06 and xVM as downloaded by pkg. I haven''t upgraded to the latest development branch, so my kernel is still 111b, and xVM is 3.1.4-xvm. I''ve created a vm, and is starts and boots off the iso, etc just fine. However, if I go into "Virtual

Ok, now I'm stuck... We have several stand-alone UNIX (AIX) systems that we need to share a few SMB shares from. None of these are joined to our domain. We want the end-users to be able to map these shares to their Windows systems using the username in the form of AIXSERVER\username, and using the password from their local AIX account on the server. Asking the end-users to understand that

Yet another odd one... I've got it set up now so that swat uses pam_smbpass.so, and once a user logs into swat at least once, it'll update their password in the passdb backend configured for Samba. But, I also need to ensure that when a user changes their password via passwd, it also gets updated. I added the following in /etc/security/login.cfg: usw: auth_type = PAM_AUTH and

Hi there! We're trying to compile Samba 4.0.0 on a fresh install of AIX 6.1 (6100-02-01-0847), with Python RPM's from perzl.org installed into /opt/freeware. We're also using XLC 12.1. Unfortunately, we can't even run ./configure, as we're getting errors from the waf system. Here's what we get: bash-4.2# pwd /admin/tst/build/samba-4.0.0 bash-4.2# ./configure --help

Hi all! Perhaps someone here could tell me if this has been seen before. We're trying to build samba-3.3.4 for IBM AIX with support for PAM, Active Directory, and Kerberos. The end goal is to be able to join the AIX system to our Active Directory domain so that users can log in via their AD username/password, and have access to their home directory via the Windows pass-through authentication

Has anyone tried building Samba 4.0 on AIX with XLC? I'm moving right along, but tripping up on some bugs in source3/utils/net_rpc.c, source3/utils/net_rpc_printer.c, and source3/utils/net_cache.c where there is an invalid use of the ":" operator. According to some other posts on the PostgreSQL forum, this shouldn't compile anywhere, even though GCC apparently allows it??