Re: scheduled task logon failure
From: Karl Levinson [x y] mvp (levinson_k@excite.com)
Date: 11/05/02
- Next message: Michael Bednarek: "Re: windows messenger spam"
- Previous message: Karl Levinson [x y] mvp: "Re: Can disabling NetBT on a NIC prevent firewalls from seing hits on port 137?"
- In reply to: David Rodman: "scheduled task logon failure"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "Karl Levinson [x y] mvp" <levinson_k@excite.com> Date: Mon, 4 Nov 2002 20:19:19 -0500
Consider enabling auditing of failed logon events on the computer. If
auditing has already been enabled, you'd see something in the windows
security event log. The fix is probably running MMC, adding the Group
Policy MMC, and granting the account log on locally and/or possibly run as a
batch process. Local policy changes get overwritten by any group policy
settings that are made in Windows 2000 Active Directory [it should be
obvious within the MMC if this is happening], so you may need to get
assistance from the network administrator that locked down the PC.
"David Rodman" <david.rodman@pec.com> wrote in message
news:60f701c28453$03546610$36ef2ecf@tkmsftngxa12...
> I have a scheduled task that I can schedule and
> successfully run as another user on a one time basis. But
> when I schedule it to run every night I get an event
> viewer log entry that says : Logon failure, user has not
> been granted the requested logon type at this machine
> (logon type 4)
>
> The environment is a win2k domain and win 2k workstations.
> The system has been locked down fairly hard...
> Any ideas on where to start looking?
>
>
- Next message: Michael Bednarek: "Re: windows messenger spam"
- Previous message: Karl Levinson [x y] mvp: "Re: Can disabling NetBT on a NIC prevent firewalls from seing hits on port 137?"
- In reply to: David Rodman: "scheduled task logon failure"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|