I am not sure the two errors are strictly related. This could be caused by
a new group policy or security template.
This issue may occur if the Network Service security account does not have
sufficient privileges to access the following registry subkeys when you
upgrade to Windows Server 2003:
Try this, assign the Network Service account full control access to the
following registry subkeys:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Dhcp
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Tcpip
To do this, follow these steps:
1. On the Windows Server 2003-based domain controller, start Registry
Editor (Regedit.exe).
2. Locate, and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Dhcp
3. Right-click "Dhcp", and then click "Permissions".
4. Click Add, type network service
See also:
-----------205069 The Microsoft Distributed Transaction Service Does Not
Start and Error
http://support.microsoft.com/?id=205069
---------
>
>This has happened over time to every Windows 2003 member
>server we have running in a Windows 2000 AD environment.
>Suddenly the dhcp client service will not start with the
>following error in event log:
>The DHCP Client service terminated with the following
>error:
>Access is denied.
>
>Followed by this error:
>The Distributed Transaction Coordinator service terminated
>with service-specific error 3221229584 (0xC0001010).
>
>We can set static ip addresses and continue using the
>servers, but now it has hit my SUS server and it is
>refusing to load.
>
__
Danny Slye
Microsoft Support Professional
MCSE
This posting is provided "AS IS" with no warranties and confers no rights.
Please reply to the newsgroup so that others may benefit. Thanks!