A system service on a Windows Vista-based computer uses named pipes to connect to a system service on another Windows Vista-based computer. Both services run under the local system account. However, when the system service on the first computer tries to connect to the system service on the second computer, you receive one of the following error messages:
Error message 1Server1_name: cannot connect to machine "Server2_name" (0x00000005)!
Server1_name: cannot connect to machine "Server2_name" (0x00000035)!
Warning This workaround may make a computer or a network more vulnerable to attack by malicious users or by malicious software such as viruses. We do not recommend this workaround but are providing this information so that you can implement this workaround at your own discretion. Use this workaround at your own risk.
To resolve this issue, follow these steps on the first computer:
- Click Start
Collapse this imageExpand this image
- Right-click Local Security Policy, and then click Run as administrator.
- Expand Local Policies.
- Click Security Options.
- In the Policy list, double-click Network Access: Named Pipes that can be accessed anonymously.
- On the Local Policy Setting tab, type the name of the second computer. This is the Server2_name name in the error message that you received.
- Click OK.
- Double-click Network access: Let Everyone permissions apply to anonymous users.
- Click Enabled, and then click OK.
By default, the
Network access: Let Everyone permissions apply to anonymous users policy setting is disabled.
Windows Vista lets anonymous users perform certain activities, such as enumerating the names of domain accounts and the names of network shares. For example, Windows Vista lets an administrator grant access to users in a trusted domain that does not maintain a reciprocal trust. By default, the Everyone security identifier (SID) is removed from the token that is created for anonymous connections. Therefore, permissions that are granted to the Everyone group do not apply to anonymous users. Anonymous users may access only those resources for which the anonymous user has been explicitly granted permissions.
By default, the
Network access: Named pipes that can be accessed anonymously policy setting is None. This security setting determines whether named pipes have attributes and permissions that enable anonymous access. If the
Network access: Named pipes that can be accessed anonymously policy is enabled, the Everyone SID is added to the token that is created for anonymous connections. In this case, an anonymous user may access any resource for which the Everyone group has been granted permissions.
For more information about network persmissions, click the following article number to view the article in the Microsoft Knowledge Base:
823659Â
(http://kbalertz.com/Feedback.aspx?kbNumber=823659/
)
Client, service, and program incompatibilities that may occur when you modify security settings and user rights assignments