similar to: net rpc rights command

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, I've written a HowTo for 'Samba domain with LDAP back end' and am looking for people to test it and tell me the stupid things I did. I also wanted to put the HowTo out there in case others wanted to do something similar and because I know you've got nothing better to do on your weekend than play with Linux ;) I'm by no

I have a share which a group write list. That group is mapped to a Linux group in /etc/group. That group in Linux has two users. The first user listed is suddenly unable to write, but the second one is. With the affected user logged in to Win2K, ifmember /list shows they are a member of the group, as does the working account. I am guessing one of those .tdb files or something got scrambled on the

I am testing out Debian Etch, and ran into an issue granting SeMachineAccountPrivilege to an account... which granting that permission had been troublesome in the past. The command I am issuing is: net rpc rights grant LDS-DEMO\\ldsinst SeMachineAccountPrivilege And I try running the command with an account that is a member of the "Domain Admins" group. The command returns: Failed to

I found the solution, or at least a work around, for my posting: "Can not grant SeMachineAccountPrivilege on Debian Etch" I ended up: 1) ssh to Debian Etch as root 2) smbpasswd -a root 3) issue the "net rpc rights grant ..." command SUCCESS!!! So, that raises the question that what MUST be executed as user root verses a member of ntgroup="Domain Admins"? I suspect

I am logged into a new test Linux server with my personal admin account. It is a member of a Linux group which has been mapped to Domain Admins. When I issue 'net rpc rights grant auserid SeMachineAccountPrivilege' and enter the password for my personal admin account, I am returned that it failed with NT_STATUS_NO_SUCH_PRIVILEGE. 'auserid' is both a Linux account and has been

We have bumped into a most odd problem. Server: Debian Etch and their Samba 3.0.24-2 Client: WinXP SP2, MSI v3, all hot fixes The following settings are in place on the server: #!/bin/bash # # initGrps.sh # Map Windows Domain Groups to UNIX groups net groupmap add ntgroup="Domain Admins" unixgroup=domadmin rid=512 type=d net groupmap add ntgroup="Domain Users"

Greetings- I have not found discussed / documented what to do with machine accounts when moving a Samba PDC to new hardware. I have seen that uid/gid numbers must match between the old/new system. I am thinking to use adduser to accomplish that, then make the numbers on the new server match, using a text editor. After that, can I simply enter the machine account entries by hand with a text

Hey all, I'm coloring outside the lines a little bit here but I would like to automate the install of a samba pdc. Within that script to install I would like to assign rights to a group. Here is an example of a few steps: # Create Unix group: groupadd domadmins # Map unix group to samba groups: net groupmap add ntgroup="Domain Admins" unixgroup=domadmins rid=512 type=d # Assign

Greetings- I am wondering if anyone from the Samba team would happen to have interest in creating official builds for Ubuntu? To add a twist, unfortunately I would not be fishing for 7.10 packages, but rather 7.04 as we ran into too many issues with 7.10 whereas 7.04 seems rock solid stable. Or, are there packages built of Samba releases for Ubuntu external to samba.org? Thanks, -- Michael

I'm running Samba 3.0.20b with XP and DOS clients. I have zero issues with WindowsXP clients but if I have a XP client accessing a file then try to get a DOS client to access (ro and rw) the same file I'm met with a sharing violation. I've tried all sorts of combinations of the following parameters: strict locking, oplocks, level2 oplocks, defer sharing violations, locking, and

Color me stupid! I have set up a small SAMBA network using a Caldera Systems eServer 2.3 implementation of Linux with a AMD K-6/2 and 128 meg RAM. It works great from one computer, and one user id, but I am unable to login as any other user. The one user is set up in such a way that it would create a serious security hole (member of group root). The server shows up in the network neighborhood,

Dear all I have install samba + ldap and it is successfully joing the domain but problem is when i login in XP machine with Administrator account of samba i cannot change anything in XP even not system time so is it problem of privileges ?? $ cat ~/satish/url.txt http://www.linuxbug.org

<rant>Every time I set up a new test Samba server, the step to "net rpc rights grant..." ALWAYS fights me tooth and nail... ALWAYS with a different error message. I've even created little scripts to run so I am not typing commands incorrectly... but NNNOOOOOO, the script to grand rights to one stink'n account always has to complain!</rant> OK, this time it is...

When ubuntu 14.04 went from samba 4.1.6 to 4.3.8 it killed my setup. Before the change I was able to run wbinfo -u and get a list of users. Now when I run wbinfo -u it returns nothing. I tried dis-joining and rejoining the domain with no luck, Here is my complete smb.conf [global] security = ads realm = SUBDOMAIN.DOMAIN.TOP workgroup = SUBDOMAIN idmap config * : backend = tdb idmap config * :

We use MS DOS 7 ala Win98 SE and the M$ client for DOS to logon to Samba 3.0.13 Debian Stable package from samba.org. Also one other unique thing, we have XCOPY32.EXE copied as XCOPY.EXE thus it is really XCOPY32.EXE we are executing, just as XCOPY.EXE. ;-) Example of failing line of code... echo f|xcopy u:\foo\bar.txt h:\file.txt where U: is the drive mapped to the server and H: is a local RAM

Greetings- I am working through coming up with a Linux client integration to Samba PDC's. I mount several shares with this sort of syntax: /bin/mount -t cifs -o credentials=/home/userid/.smbcredentials,uid=userid,gid=userid,dmask=0777,fmask=0666 //ldslnx01/data /mnt/ldslnx01/data/ However when I create new files/dirs on the Samba share from the Linux workstation, the perms are not 0666/0777

I am somewhat confused... I understand that the preferred method to mount a Samba share with a Linux client is to use "mount -t cifs" rather than "mount -t smbfs". I get the impression that smbfs is samba.org developed code where as cifs is from elsewhere. Thus the point of confusion. Why is samba.org not developing the preferred code in this case? A sub question to that

One of the servers we admin has countless such errors in log.smbd: [2007/05/07 14:17:08, 0] tdb/tdbutil.c:tdb_log(783) tdb(/var/cache/samba/printing/HPLJ3600.tdb): rec_read bad magic 0x443810ec at offset=28412 The only thread I saw regarding "rec_read" stated: <><><><><> If this really happens often to you, then you have some basic problems with your

Recent list messages got me thinking... Is there a way to support both local and roaming profile with one server / domain? As I understand it, the "magic" line that tells Samba not to do roaming profiles is the smb.conf line: logon path = Which the line must exist, and must be set to null. But that is in the global section. So is there a way to support both local and roaming...

Hi list, after upgrading our ldap server, the Domain Admins group doesn't work anymore. Members of the domain admins group don't have any special rights on the workstations (for example, they cannot even change the date of a machine in the domain anymore). When I lookup the group members I get: