Server 2003 + Domain Controller + SP1 = Broke?

Printable View

August 24th, 2005, 03:16 PM
3fingersalute

Quote:

Originally Posted by CeeBee

Drivers get uninstalled too... remember how XP SP2 breaks Firewire drivers...

Agreed.

Try a different NIC.
August 25th, 2005, 09:15 AM
kannibul

NICs are there when SP1 is applied, but the system is not promoted to a DC.
August 25th, 2005, 09:18 AM
3fingersalute

Quote:

Originally Posted by kannibul

NICs are there when SP1 is applied, but the system is not promoted to a DC.

I still think trying another NIC is worth a shot.
August 25th, 2005, 09:32 AM
kannibul

Quote:

Originally Posted by 3fingersalute

I still think trying another NIC is worth a shot.

Two different servers, two different NIC's - actually, 4 different NIC's between the two servers.

it's not a problem with the nic.
August 25th, 2005, 09:42 AM
3fingersalute

Oh, my bad. I thought it was all the same make and model of NIC.
August 29th, 2005, 04:58 PM
kannibul

The $100 resolution:

1. Open Default Domain Controller policy.

2. Expand to "Computer Configuration\Windows Settings\Security Settings\Local Policies\User Right Assignment".

3. In the right pane, find the policy "Impersonate a client after authentication". Please check if the "SERVICE" or "Administrators" accounts are included in the setting

===

This wasn't set in the policy (it had the IIS_WPG and a SID listed), and when set, things started working again after the security policy refreshed. I demoted and rebuilt the machine, and all works fine.