Hello, this is not really a WPKG problem, but maybe one of you has experienced this problem before and can help me. Short Summary: Cannot access wpkg share on domain controller prior to user logon Detailed situation: We have set up a Samba Domain Controller with a backup domain controller working as the primary file server. PDC - Server A BDC/Fileserver - Server B Now for a long time the server containing the packages for WPKG was a third Samba Server, which was only a domain member but provided some shares to the workstations as well. This was all good but came from a grown environment where diskspace was rare. So the third Samba Server got deconfigured and the share holding the WPKG packages was moved to the BDC/fileserver (Server B). In our setup there are severals scripts involved, which are invoked via Policy, one finally calling wpkg.js, which is also on the fileserver (Server B). I have the share configured as following: [wpkg] comment = WPKG Images path = /export/wpkg create mask = 0660 directory mask = 2770 force group = administratoren browsable = yes writable = no write list = @administratoren guest ok = yes share modes = no inherit permissions = yes map archive = no This is mostly the same as our netlogon shares, I believe "guest ok" is the most essential option here. Too bad I don't have a copy of the old share setup on the deconfigured server though, the transition wasn't made by me. What I see now is that while booting there seems to be a brief connect to the fileserver using the username of the logon user. The samba server logs this: [2009/09/17 14:01:31, 0] smbd/service.c:make_connection_snum(850) make_connection: connection to wpkg denied due to security descriptor. The script output itself is: "Software install from \\host\wpkg\software / \\host\wpkg\software" Microsoft (R) Windows Script Host, Version 5.7 Copyright (C) Microsoft Corporation 1996-2001. Alle Rechte vorbehalten. Eingabefehler: Die Skriptdatei "\\host\wpkg\wpkg.js" wurde nicht gefunden. Which mainly means, wpkg.js wasn't found in the specified location. After the login is complete, opening the share still doesn't work, but that seems to be Windows related, as there was a connection attepmpt as another user from the same machine. If I disable the script execution at boot time using the share is of course no problem. Alternatively one can just wait for some time and then the share will work: Samba log entry: [2009/09/17 14:05:12, 1] smbd/service.c:make_connection_snum(1033) xppro-testpc (ip) connect to service wpkg initially as user username (uid=695, gid=1000) (pid 17946) Executing wpkg.js as Administrator then works fine as well. Regards, Dennis -- .............................................................. Riege Software International GmbH Fon: +49 (2159) 9148 0 Mollsfeld 10 Fax: +49 (2159) 9148 11 40670 Meerbusch Web: www.riege.com Germany E-Mail: kuhlmeier at riege.com --- --- Handelsregister: Managing Directors: Amtsgericht Neuss HRB-NR 4207 Christian Riege USt-ID-Nr.: DE120585842 Gabriele Riege Johannes Riege .............................................................. YOU CARE FOR FREIGHT, WE CARE FOR YOU -------------- next part -------------- A non-text attachment was scrubbed... Name: kuhlmeier.vcf Type: text/x-vcard Size: 306 bytes Desc: not available URL: <http://lists.wpkg.org/pipermail/wpkg-users/attachments/20090917/de72b2cf/attachment.vcf> |