David,
Recently we have seen a few reports of this as a problem. It has been my
experience that intermittent failure to exec a logon script is related to
a name ersolution problem.
Are you using a WINS server? ie: Is samba your WINS server with in
smb.conf [globals]:
wins support = yes
_OR_ an MS Windows NT4/2000 Server that has the WINS server installed and
configured.
Also, do all your MS Windows machine TCP/IP settings having the IP
addresss of the WINS server correctly set?
- John T.
On Sat, 19 Apr 2003, David van Geyn wrote:
> Hi,
>
> I've been searching through the list archives on marc.theaimsgroup.com,
and
> haven't found many suggestions relating to this problem. What's
happening,
> is that maybe 5 out of 100 network logons the logon script does not
> execute, and none of my drives are mapped. This happens on both NT 4.0
> Workstations as well as Windows 2000. It's been happening as long as I
can
> remember (since several years ago when I started using Samba) and I've
> never found a way to solve this problem. I can't find any links between
the
> times this happens and anything else. It just seems to happen at random.
> Does anyone else have this problem, or have any suggestions for trying to
> solve it?
>
> I'm using Samba 2.2.8 on a FreeBSD 4.5 server, but, as I said it's
been
> happening for a long time using all kinds of versions of Samba. The server
> itself has very little load on it; usually the load averages hover around
> 0.04 or less.
>
> In the global section of my smb.conf, I have
> logon script = %U.bat
>
> And the [netlogon] share is like so:
> [netlogon]
> comment = Network Logon Service
> path = /usr/local/samba/lib/netlogon
> admin users = dataiv
> read only = No
>
> Thanks for any help or suggestions,
>
> David van Geyn
>
>
>
--
John H Terpstra
Email: jht@samba.org