similar to: prexec change between 3.0.24 to 3.0.25

I have a perl script that I'd like to use to create windows 9x login scripts at login time but I cannot get the process to work right. I have RedHat 7.3 (actually the k12ltsp v2.1.0 which is a modified RH7.3) set up as a domain controller which is working well. Manually created login scripts run fine on the workstations at login. I'm using a netlogon script I found at

Hi all, I am running Samba 3.0.20B on an AIX server with SECURITY=USER using an LDAP backend. I am looking for a way to capture the actual username(%USER_NAME%) that the client user is logged onto his individual workstation with and compare it with the user(%u) they are connecting with the share as. If they are different, I want to reject the user's connection. After doing some

Hi all, I had the following line in my smb.conf with which to log access to the home share when users logged in: preexec = /bin/echo \"%u logged in to %m at %T\" >> /var/log/samba/logons.log Since updating to LDAP however, it's stopped working and I suspect that smbldap cant handle the % substitutions for user, machine and time. Has anyone else run into this problem? If

Hi Rowland, thank you for your effort! However, this is entirely not what I am trying to achieve. What I am trying to achieve is to get the "prexec" method to work. The reason behind this is that I would like to have a zfs data set created per user in an automatic (scripted) way. The reason behind that is that if I do this by hand - from a domain admin account and with the ACL

I'm looking for a simple solution to log a single entry for each login to a Samba PDC. My current attempt(s) of using a root prexec script in either the [netlogon] share definition or the [global] section are working, but not exactly as expected. In [netlogon] I have an entry: root preexec = /path/to/script/makelogonscript.pl %g %u %m %I ...where makelogonscript.pl generates a

Hi. I have problems, when upgraded from samba sernet 3.0.24 to 3.0.25 (too early ?): 1) always must change password, when log in to windows XP professonall - samba 3.0.25 PDC - password expired 2) I can't browse widnows network on client machine - network broswer in WinXP don't respond - just hangs 3) I cann't priny any more to printers attached to another widnows machines

Gerry, It looks like 3.0.25 breaks "stand alone/no winbind/no domain" servers. This is remeniscent of the 3.0.23b SID/GID problem. The only thing that jumps out at me is that you can't access your home share and other shares just quit working. Looking at the log files, I see this: [2007/05/14 15:24:55, 10] smbd/open.c:share_conflict(389) share_conflict:

Rowland, I apologize: I have overlooked this answer of yours before my last post. >> I think you may still be missing the obvious, I was suspecting that. >> '[homes]' *does not work* on a DC. You mean in general or in my assumed use case? Am 21.10.2015 um 11:27 schrieb Rowland Penny: > On 21/10/15 10:07, Ole Traupe wrote: >> Hi Rowland, >> >>

Good morning, I have a working Offline Files setup w/Samba 3.0.24 (FreeBSD 6.2 host OS) and a Win XP SP2 client. Upon updating to Samba 3.0.25, the XP client's offline cache would show (as viewed via the Offline Files Folder) that synced files are write-only ('User W' in the Access column). When offline, theses files appeared to be available via Explorer and double clicking would

Running Samba 2.2.2, having troubles with preexec when it involves the path parameter: Log on to the samba server as kris, user "users". %U expands to kris, %G expands to users. [profile] path = /data/profile/%U preexec = /bin/mkdir -m 700 /data/profile/%U writable = yes create mode = 0600 directory mode = 0700 This fails to work, Samba reports that it could not

By mistake or by design membership in a Windows Primary Group seems to be mandatory! We are using printservers configured as member servers of Samba domains. with the following configuration security = DOMAIN password server = PDC encrypt passwords = yes map to guest = Bad Password The Samba PDCs use plain smbpasswd files. Since upgrading to 3.0.25 and

Hi, I make use of shadow_copy2 and root preexec. The vfs root preexec is responsible to auto create home directories which initially don't exist. The script behind it is well tested and works perfectly. Unfortunaltely shadow_copy2 seems to be called before root preexec and fails due to the missing ZFS home share which causes the session to fail completely before root preexec even has a

On 18/05/15 07:36, Daniel M?ller wrote: > Msdfs proxy is pointing to another instance of samba servers, it passes > through. > I think running preexec there on the other instance will do the trick. > > Greetings > Daniel > > > EDV Daniel M?ller > > Leitung EDV > Tropenklinik Paul-Lechler-Krankenhaus > Paul-Lechler-Str. 24 > 72076 T?bingen > Tel.:

Hi Steve, And thanks for your answer. Unfortunately it does not solve my problem. What I?m trying to do is to create two dirs using preexec in the same service. It works well as long as I?m only creating one directory, what I can?t figure out is how to create the second directory withing the same service. Eg. How would I continue after the last "fi" in the script to check for the second

One more time: root preexec does: run a command or script if the user hit the share. Now with msdfs proxy it need to be run on the linked host that carries the share. So you are better to set root preexec on the share of the linked host. I think there is no other way. Server1 [sharepointtoserver2] msdfs root=yes msdfs proxy =\server2\shareonserver2 Server2 [shareonserver2] Root

Hi, I was wondering if someone had any thoughts as to why "preexec" doesn't fire when "msdfs proxy" is used? Thank you, Greg Enlow -- Greg Enlow grenlow at hk.mailbox.de On 13 May 2015, at 11:18, Greg Enlow wrote: ok ok ... Names have been changed to protect the inoccent. This installation is being used to mitigate a server migration by providing read-only access

Hi everyone, I have a small home network with a Samba 2.2.3 server on Linux serving up my files and printers. However, from windows machines (win 98) connecting to a share takes an annoyingly long time (in the order of 10s of seconds) Connecting from a linux box is very quick. I have configured Windows 98 to fully reconnect the share on logon. If I don't, Windows Explorer hangs all

Looks like my nfsv4 kerberos and root access problem. In that case, root didnt have a kerberos ticket, and was not allowed to access the needed folder. I think this is a bit the same. Creating the users and profiles shares from ADUC is working fine for me but not scripted from user root. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at

hi i'm trying to solve this problem, i've came up with a solution, but i don't think that this is the best availibe method for this problem i read about that samba does provides a 'preexec' call that can prevent a share to be accessed, and i figured out, that with this i can reject access to a share if the user have already logged in from another maschine. and if i wrote the

I updated all my servers to 3.0.25 early this morning. Everything seems 100% A-OK except for the most surprising thing, all my Windows and Macintosh clients, no problems. But I'm having severe difficulty with the 3.0.25 smbclient. If I use smbclient from 3.0.24 it too can connect to my 3.0.25 servers without issue. Its bizarre. Before I go into it let me say, I've got some 3.0.25