The IPC$ share is created by the Windows Server service. This special share exists to allow for subsequent named pipe connections to the server. The server's named pipes are created by built-in operating system components and by any applications or services that are installed on the system. When the named pipe is being created, the process specifies the security that is associated with the pipe, and then makes sure that access is only granted to the specified users or groups.
Although Windows Server 2003 no longer prevents anonymous access to IPC$ share, there is a Network access: Let Everyone permissions apply to anonymous users security policy setting that defines whether the Everyone group is added to an anonymous session. If this setting is disabled, the only resources that can be accessed by an anonymous user are those that are specifically granted to the Anonymous Logon group.
Additionally, in Windows Server 2012 or a later Windows Server-based operating system, there is a feature to determine whether anonymous sessions should be enabled on file servers. It is determined by checking if any pipes or shares are marked for remote access.
Article ID: 3034016 - Last Review: Feb 4, 2015 - Revision: 1