Named pipes: Difference between revisions

From WikiWiki
Jump to navigation Jump to search
No edit summary   (change visibility)
Line 11: Line 11:
* Windows DFS -> netlogon
* Windows DFS -> netlogon
* [https://success.trendmicro.com/solution/1059081-error-connecting-to-server-open-pipe-failed-appears-when-connecting-to-serverprotect-for-network Seen trendmicro services]
* [https://success.trendmicro.com/solution/1059081-error-connecting-to-server-open-pipe-failed-appears-when-connecting-to-serverprotect-for-network Seen trendmicro services]
* [[netapp connects anonymously|https://support.symantec.com/en_US/article.TECH123400.html]]
* [https://support.symantec.com/en_US/article.TECH123400.html netapp connects anonymously]netapp connects anonymously

Revision as of 14:19, 23 December 2016

A named pipe is a Windows specific interprocess communication method that allows processes on the same or different systems to communicate with each other. This setting allows you to define exceptions to the "Network Access: Restrict anonymous access to Named Pipes and Shares" setting below. Pipes listed in this setting can still be accessed anonymously (aka Null Session) even if "Network Access: Restrict anonymous access to Named Pipes and Shares" is enabled. This setting is necessary since there are a few components of Windows with name pipes that must allow anonymous access in order to function. 


services making legit use of unauthenticated named pipes