Windows Forum

Ask something
Discussion Locked

NT clients stop exuting login scripts

0 helpful
8 replies

by jkearns

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

This is so bizarre, I'm not sure how to even ask it!

I had a login script set up, and all my clients, NT, XP, 98, 2000, used it. All of a sudden, the script stopped executing on my NT clients!

When I browse to the PDC\NetLogon from a user/machine where the script did not execute, and double-click the script, I get the message "You do not have access to the resource ..". I added a "pause" as the first statement in the script to rule out anything within the script, and even that did not execute.

I thought there was some sort of permissions problem. Why it would start happening all of a sudden, I have no clue. I tried (temporarily) changing the script's permission so that Everyone had Full Access. (This is an NT 4.0 Server, SP6.) Still didn't work.

Then I tried logging on the same user to a 98 machine. Script executed. Same on 2000 and XP.

What's the deal? I thought permissions are by user, not by user/machine ???!??

Thanks a lot in advance!

Jerry

8 replies

by gigelul

I don't have any other ideea in this momment.
Check permission for:
\\Computer\C$\WINNT\system32\Repl\Import\Scripts
Everyone must have read and execute rights and also you must have here a copy of your login script.

by jkearns

Permissions are correct, or else it wouldn't work on the other clients. Also, I changed permissions to Everyone, Full Control, and it didn't change anything.

by gigelul

To continue the dialogue post comments only. Rate the answers when you will close the question.

I speak about permissions on NT machine not on Server.

by gigelul

Is not imperative but is possible if you have many servers (PDC,BDC), than the client is authenticate by a server which don't have the logon script.
Enable directory replicator service on all workstations and also on Servers and you will have the logon script in right place for all your clients and automaticaly updated if you change it.

by jkearns

I've actually run into that problem before, but that's not it. I said that "When I browse to the PDC\NetLogon from a user/machine where the script did not execute, and double-click the script, I get the message "You do not have access to the resource . "

What the problem turned out to be was that the permissions on cmd.exe on the NT machines were wrong! Even though the users weren't executing cmd.exe directly, running their login script invokes cmd.exe, I guess.

by jkearns

I'll check ... I need to have a copy of login script on every client machine ??!!?

This discussion is closed to new replies.