Server 2003 + Domain Controller + SP1 = Broke? - Page 2
Page 2 of 2 FirstFirst 1 2
Results 16 to 21 of 21

Thread: Server 2003 + Domain Controller + SP1 = Broke?

  1. #16
    Laptops/Notebooks/PDA Mod 3fingersalute's Avatar
    Join Date
    Jun 2001
    Location
    PA
    Posts
    3,880
    Quote Originally Posted by CeeBee
    Drivers get uninstalled too... remember how XP SP2 breaks Firewire drivers...
    Agreed.

    Try a different NIC.

  2. #17
    Registered User
    Join Date
    Aug 1999
    Location
    near the backdoor to hell
    Posts
    804
    NICs are there when SP1 is applied, but the system is not promoted to a DC.

  3. #18
    Laptops/Notebooks/PDA Mod 3fingersalute's Avatar
    Join Date
    Jun 2001
    Location
    PA
    Posts
    3,880
    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.

  4. #19
    Registered User
    Join Date
    Aug 1999
    Location
    near the backdoor to hell
    Posts
    804
    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.

  5. #20
    Laptops/Notebooks/PDA Mod 3fingersalute's Avatar
    Join Date
    Jun 2001
    Location
    PA
    Posts
    3,880
    Oh, my bad. I thought it was all the same make and model of NIC.

  6. #21
    Registered User
    Join Date
    Aug 1999
    Location
    near the backdoor to hell
    Posts
    804
    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.

Similar Threads

  1. Event Id: 1003 on Windows Server 2003 Std.
    By agalenia in forum Windows Server 2003 & Windows Home Server
    Replies: 2
    Last Post: August 22nd, 2005, 02:40 PM
  2. DOWNLOAD: BizTalk Server 2004 SP1
    By TechZ in forum Windows Server 2003 & Windows Home Server
    Replies: 0
    Last Post: January 28th, 2005, 05:07 AM
  3. NT4 member server in a 2003 domain
    By Ya_know in forum Tech-To-Tech
    Replies: 5
    Last Post: April 8th, 2004, 03:27 PM
  4. security for server 2003
    By jlreich in forum Windows Server 2003 & Windows Home Server
    Replies: 17
    Last Post: March 27th, 2004, 04:20 AM
  5. Domain Controller no longer on the network
    By imaeditedbysowulo in forum Windows NT/2000
    Replies: 5
    Last Post: May 25th, 2001, 03:21 PM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •