RPC Service fails to start after DCPROMO unless..

David · Guest

upon rebooting after completing dcpromo on server 2k3 sp2 R2 (adding dc to
existing 2k domain.. followed all latest procedure durring which no errors
were received) strange things started happening.. first, I went to uninstall
a particular program that I no longer wanted running on the server since
it's now a DC and windows installer would not run... forget the specifc
error, then when going to web to download windows installer to reload I
realized I had no network connectivity... then looking in my network
connections I see they are all gone!

I followed instructions from the below 2 links and it *did* fix *all* the
issue's I was having BUT, the last step is to change the RPC service back to
run under the NetworkService account and reboot... after doing that it all
broke again. Again, everything was working when RPC service was running
under local system account.

so, I just repeated the fix, and the server is currently rebooting....
however my current theory is that my RPC service won't run under
networkService account anymore? anyone run into this before?

http://www.bensingerconsulting.com/support/helpdesk/issue_view.asp?ID=10&CATE=0

http://blogs.orcsweb.com/rick/default.aspx (Loss of Network Connectivity and
Local Area Connection)

side note: the first link has you add aspnet among others to the DC security
policy, user right: 'impersonate a client after authentication'. The other
2, (administrator and service, I think) are listed in the description as
defaults, so I did add them (I had nothing listed), but I did not add
aspnet. Anyone know if it's ok for aspnet to have this right? necessary if
machine not a webserver? I wouldn't think so... also, was it ok to add
administrators and service back? the desc did list them as defaults but
maybe they were removed from an update, or the dcpromo process, for a good
reason?

this is one of the craziest issues I've encountered...