Hello MWave,
If you got the info from David Shen it will be correct. For your error message
check your policies under computer configuration, windows settings,security
settings, local policies, user rights assignment, "Impersonate a client after
authentication". By default the "local system" is not in the policy setting.
Check the policy description.
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!!
http://www.blakjak.demon.co.uk/mul_crss.htm
> Hi Meinolf,
>
> Actually we had some trouble with the Network Connections service
> shortly after doing the dcpromo on the initial 2003 R2 server.
>
> David Shen from MS Online Support gave several suggestions. What
> solved the problem is to switch the logon authority for Network
> Connections from "NT Authority" to "Local Account". This put it in
> agreement with the "RPC Service" logon account. Apparently, these need
> to be synchronized for Network Connections to work. As soon as we made
> this change, all of our network connections and interfaces again
> became available.
>
> Is it OK to use "Local Account" instead of "NT Authority" for these
> services or should I attempt to make them both work off of "NT
> Authority"?
>
> I have heard mention of "impersonation levels" to work around these
> issues. Any idea on the recommended practice?
>
> Thanks,
> Tom W.
> PS - I will look into your previous suggestions, but I wanted to
> explain the history further.
>
Similar Threads
Linear Mode
