It is attached, I hope. To explain what used to happen; when a user logs in, their batch file is run, in this case sharon.bat. It, in turn, calls net-log.bat which is the actual login script. sharon.bat is never called the way it used to.
Here is [global] and [netlogon]. The comments are different things I've tried:
[global]
comment = Linux based server
server string = Samba Server
netbios name = OciCat
workgroup = CRANDELL
security = user
encrypt passwords = yes
preferred master = yes
domain logons = yes
domain master = yes
local master = yes
# logon drive =
# logon home =
# logon path =
logon script = %U.bat # Win9x needs this
# logon script = logon.cmd # WinNT needs this
log file = /var/log/samba.log
max log size = 50
debug level = 2
printcap name = /etc/printcap
load printers = yes
# use client driver = yes
printing = bsd
guest account = pcguest
# nt status support = no
os level = 64
preserve case = yes
short preserve case = yes
oplocks = no
level2 oplocks = no
kernel oplocks = no
write cache size = 262144
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
[netlogon]
available = yes
path = /home/samba
writable = no
comment = Network Logon Service
public = yes
admin users = admin, bob
write list = admin, bob
Thanks
David W. Chapman Jr. ([EMAIL PROTECTED]) wrote*:
>
>On Mon, May 27, 2002 at 09:33:44PM +0000, Bob Crandell wrote:
>> Yes, the login script runs manually. I have it in the Startup group until this
is
>> resolved. This is true of the admin also and admin can edit the login scripts.
>
>You'll have to load smbd with the -d10 flag and check the logs when
>someone logs on to see what the problem is.
>
>
--
Bob Crandell
Assured Computing
When you need to be sure.
Cell 541-914-3985
FAX 240-371-7237
[EMAIL PROTECTED]
www.assuredcomp.com
Eugene, Or. 97402
samba.log
Description: Binary data
