Link to home
Start Free TrialLog in
Avatar of gbnorton
gbnortonFlag for United States of America

asked on

windows 2003 logon scripts not running

We are having to manually map network drives because our logon scripts are not running.  I believe it is a permissions problem.  From a client pc I can browse to \\domaincontroller\netlogon and see the scripts.  But if I try to run one I get the error "Windows cannot access the specified file.  You may not have appropriate permission to access that item."

I think this has been going on for quite a while, but only recently have we been trying to resolve it.

Thanks,
Brooks
Avatar of Krzysztof Pytko
Krzysztof Pytko
Flag of Poland image

Can you run in command-line on your DC or any workstation

cacls \\domain.local\NETLOGON\<scriptname> >c:\perm.log

and attach it here, please?

Please also run on DC in command-line

dcdiag /c /v >c:\dcdiag.log

and post it here for analyze, please

Regards,
Krzysztof
1) what happens when you run the script when it's saved locally on your workstation?
2) what happens when you run the script directly from the domain/netlogon
3) what are the permissions on the SHARE
4) do users have access to NET.EXE (or whatever you use) to map the drive?
5) does it work when you run the script as an Admin?

It would also help if we can see what your script looks like...
Avatar of gbnorton

ASKER

iSiek:
On my computer, and I am a domain admin, when I ran the cacls \\domain.local... It worked.  The attached file is perm1.txt.
On another computer, logged in as a typical user, I got the error:Access denied. That attached file is perm2.txt
On the DC is perm3.txt
dcdiags.txt is also attached.

ThinkPaper, I'll respond to you tomorrow.

Thanks for your help.
perm1.txt
perm2.txt
perm3.txt
dcdiag.txt
ASKER CERTIFIED SOLUTION
Avatar of rhinoceros
rhinoceros

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
rhinoceros,
You are correct. The script itself did not have the Authenticated Users group.  But the folder itself did.  I added the  Authenticated Users group and it ran properly.
Thanks,
Brooks