Many Windows server products, such as SQL Server, not to mention Windows itself), use named pipes for communicating with other servers and processes. Pipes are usually invisible and silent; you don't interact with them and you don't generally learn a lot about them.
But there are times that's not necessarily a good thing—for instance, if you inherit someone else's server, and you don't know which services might be opening named pipes, which could constitute an attack vector. If you don't know about the existence of a named pipe that anyone can connect to, or don't know what the available permissions are on a named pipe, it can be difficult to find out.
Programmer Craig Peacock has written a utility to get to the bottom of the named-pipe puzzle:
The program's basic mode consists of a simple dump of the local pipe list, which you can obtain
by running the program without any switches. If you want to bring up the access control list for a
given pipe, type pipesec \\.\pipe\
To examine or edit the ACL for a pipe on another computer, use pipesec
About the author: Serdar Yegulalp is editor of the Windows Power Users Newsletter. Check it out for the latest advice and musings on the world of Windows network administrators. He is also the author of the book Windows Server Undocumented Solutions.
More information from SearchWinSystems.com
- Tip: FAQ: Server
- Topics: Server
- RSS: Sign up for our RSS feed to receive expert advice every day.
This was first published in June 2006