Found this, see if it helps:
CAUSE
This behavior can occur when a service that requires the NTLM Security Service Provider (NTMLSSP) service to operate is loaded before NTLMSSP has started. To prevent the Service Control Manager from locking, the service is temporarily unable to make remote calls. The service can be manually started without error after the NTLMSSP has loaded.
RESOLUTION
WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.
For information about how to edit the registry, view the "Changing Keys and Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it. If you are running Windows NT or Windows 2000, you should also update your Emergency Repair Disk (ERD).
To resolve this behavior, follow these steps:
Start Registry Editor (Regedt32.exe).
Locate and click the key for the service name indicated in the Event Viewer error messages:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\FailedServiceName
NOTE: Match the .exe file listed in the Type field of the Event Viewer message to the ImagePath value of the registry key.
Add the following value:
Value Name: DependOnService
Data Type: REG_MULTI_SZ
Value: NtLmSsp
Click OK to save the values.
When you add this value, the service waits until the NTLMSSP service starts. If the NTLMSSP service has not started, this configuration starts the NTLMSSP service before it starts the other services.
