Wednesday 7 December 2011

Samba refuses to run batch file on login

Samba refuses to run batch file on login

Hello, all.

I am attempting to configure Samba 3.5 under CentOS 5.5 so that certain shares will be mapped to drive letters automatically when a user logs in. As far as I can tell, I have everything in smb.conf configured correctly, and the batch file works fine when I execute it locally on the Windows machine after logging in. Here is my smb.conf file:
Code:

[global]
        workgroup = SAMBA       
        interfaces = 127.0.0.1 eth0
        interfaces = 192.168.1.253 eth0
        bind interfaces only = true
        printing = cups
        printcap name = cups
        hosts allow = 192.168.1. 127.
        load printers = yes
        domain master = yes
        domain logons = yes
        preferred master = yes
        logon script = logon.bat
        security = user

[netlogon]
        comment = Network Login Service
        path = /home/netlogon
        guest ok = yes
        writeable = no
        share modes = no
        valid users = %u
        read only = no

[public]
        path = /home/public
        public = yes
        browseable = yes
        only guest = yes
        writeable = yes
        printable = no

[private]
        path = /home/private
        browseable = yes
        public = no
        only guest = no
        writeable = yes
        printable = no

[shared]
        path = /home/shared
        browseable = yes
        public = yes
        only guest = yes
        writeable = yes
        printable = no

And the logon.bat file, which is in /home/netlogon:
Code:

net time \\turnbowsrv /set /yes
net use h: \\turnbowsrv\%u
net use i: \\turnbowsrv\shared
net use j: \\turnbowsrv\public
net use k: \\turnbowsrv\private

I have tried replacing the logon.bat file with one containing a simple "pause" command, which should leave a DOS window open and waiting for a keystroke on login. This does not appear. I cannot for the life of me figure out why my login script is not being executed. Thanks in advance for any insights.

No comments:

Post a Comment