search for: dataroid

Hello list, I'm running a samba server in AD domain, with some AD users explicitly mapped into local users by "username map = sambauser.map", which is a text file. Problem is found with explicitly mapped user, I can only access home share by //server/<ADusername>, not //server/homes (using windows explorer). This feels wrong because I also tried those AD users not listed in

Hello list, Accidentally I found that when network is down "smbclient -L localhost -U%" became slow however it still succeeded after like half a minute. This is weird because my Samba server is running inside AD, Q1. How can smbclient authenticate without talking to AD controller? I think in this case smbclient at least tried to (reach AD controller), otherwise shouldn't take it

Hello list, I've got a question from reading Using Samba 3rd, where it puts: ... the final permission is caculated by below filters in the order used by Samba: 1. Apply any DOS attribute mapping options << I take this as either map DOS attributes to execute bits, or store DOS attributes in extended attributes. Correct? 2. Apply the create mask settings 3. Apply the force

Is there an option to the net command to not have it update DNS in AD? We are joining servers using the net ads join command and it's changing our static DNS entries to dynamic ones which then get deleted when AD does its DNS scavenging. It seems that dynamically updating DNS is the default. The command we're running is: net ads join -U adminuser%adminpasswd Thanks - Mike Mike

When adding a domain user to a samba 3.6 PDC I found that the [homes] share was not created. It turns out there was no home directory specified in /etc/password for this user. Once a linux home directory was added the [homes] share worked, but I would expect this to work anyway since a different path is being used for windows home directories than for the linux users. Is this expected behavior

Greetings list, I just upgraded to samba 3.6.0 trying SMB2. Though Windows 2008 R2 can work with SMB2 shares just fine, I'm unable to access SMB2 shares with mount.cifs or smbclient, even with "-m smb2" specified -- I get this "Unrecognised protocol level smb2", whereas smbclient comes with samba-client-3.6.0-63.1.rpm. So is this supported yet (from client side) or I

Hello, I have Samba server running version 3.0.33-3.29.el5_5.1. The Samba server is a member server of a Windows 2003 domain. Winbind provides authentication. We have a physical directory named hr that is shared as "hr" and is accessible to the HR department. A subdirectory of the hr directory named hrshared is shared as "hrshared" and should be accessible to specific users

Hello all, I have a Samba 3.5 server running in an AD domain and domain users can access nonpublic shares with their credentials. Good since this is what I want. However accidentally I found that local users (of the server itself) could also access nonpublic shares with their credentials. Is this a bug or Samba works this way, accepting both local and domain users? Is there anyway I can make the

Greetings list, Have a situation that doesn't fail but with inconsistent results: With a Samba 3.5.4 running as AD member, and map an AD user into a local user on Samba server, configurations are like below: smb.conf: username map = /usermap.txt usermap.txt: foo = MYDOM\bar Then try to access AD user bar's home directory via 1) smbclient //localhost/bar -U

Hello list, The issue is as the topic says, following are details: the Samba server running as ADS member, NBT enabled on Windows machines, no WINS. Windows machines can find each other by 'nbtstat -a' but cannot find the Samba server. The Samba server can't find neither Windows machines nor itself by 'nmblookup -a <netbios-name>', error message is "could not open

Greetings list, This sounds sort of twisted but in its essence Windows ADS has an LDAP server too, so here is what I do hoping it'll work: 1. Install Utilities and SDK for UNIX-based application and Identity Management for UNIX on Windows server 2003, create a new OU named "idmap". 2. Configure smb.conf as per Samba HOWTO chapter 14 "IDMAP storage in LDAP using winbind"

Hello list, I'm running a samba 3.5.3 CTDB cluster, found the output is different Q1: What does the "0:" mean in pid column? There was no such stuff in non-CTDB smbstatus output. <snip> samba_01:~ # smbstatus -S 2>/dev/null Service pid machine Connected at ------------------------------------------------------- ben 0:21363 samba Mon Oct

Hello everyone, Got a weird ACL issue: First of all, my Linux host is fully ACL enabled (kernel support, file system support, mount with xattr, library support, samba compilation support, all set). Then a share is created with vfs acl_xattr and ea support on, got mounted on a Windows client as administrator, and a directory created right under the drive. The issue is when I was checking out the

Greetings list, I was looking at the wiki "samba and clustering" and a ctdb.pdf, admittedly both are quite old (2006 or 2007) and I don't know how things change over years, but I just have two questions about LMASTER: < this is from pdf > LMASTER fixed ? LMASTER is based on record key only ? LMASTER knows where the record is stored ? new records are stored on LMASTER Q1.