|
Service Running as System Account Fails Accessing Network
When an application is started using the system account, it logs on with null credentials.
If it attempts to access a remote shared resource (using a null session), it fails.
Service operations attempting to access server resources over the network receive errors
such as the following:
Error 5: Access is denied.
When an application using the system account uses a UNC name to access a shared resource,
the following error message is returned:
File Not Found
To workaround this, you can modify the registry of each remote resource computer as follows:
WARNINGS:
- A shared resource configured in this manner is not secure. Microsoft does not recommend this configuration if null session security is a consideration.
- Using the Registry Editor incorrectly can cause serious, system- wide problems that may require you to reinstall Windows NT to correct them. Microsoft cannot guarantee that any problems resulting from the use of the Registry Editor can be solved. Use this tool at your own risk.
- 1. Start the registry editor, REGEDIT.EXE
- 2. From the HKEY_LOCAL_MACHINE subtree, go to the following key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters\NullSessionShares
NOTE: NullSessionShares is type REG_MULTI_SZ
- 3. On a new line within the NullSessionShares key, type in the share you want to access with a null session (for example: "PUBLIC")
- 4. If your application uses Named Pipes and requires null session support.
- a. From the HKEY_LOCAL_MACHINE subtree, go to the following key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters\NullSessionPipes
NOTE: NullSessionPipes is type REG_MULTI_SZ
- b. On a new line within the NullSessionShares key, type in the pipe you want to access with a null session.
- 5. Stop and restart the server.
See also Q124184 at Microsoft Support:
http://support.microsoft.com/kb/q124184/
|
