命名管道上的FileNotFoundException

private static PipeSecurity PipeSecurity
    {
        get
        {
            var security = new PipeSecurity();
            security.AddAccessRule(new PipeAccessRule("Users", PipeAccessRights.ReadWrite, AccessControlType.Allow));
            security.AddAccessRule(new PipeAccessRule("SYSTEM", PipeAccessRights.FullControl, AccessControlType.Allow));
            security.AddAccessRule(new PipeAccessRule(WindowsIdentity.GetCurrent().User, PipeAccessRights.FullControl, AccessControlType.Allow));
            security.AddAccessRule(new PipeAccessRule(new SecurityIdentifier(WellKnownSidType.AuthenticatedUserSid, null), PipeAccessRights.ReadWrite, AccessControlType.Allow));
            return security;
        }
    }

            var pipeStream = new NamedPipeServerStream(PipeName, PipeDirection.InOut, MaxThreads, PipeTransmissionMode.Message, PipeOptions.WriteThrough, 1024, 1024, PipeSecurity);
            _logger.InfoFormat("CreatedServerInstance: {0}, Waiting for Connection.", _clientCount+1);
            pipeStream.WaitForConnection();

使用命名管道时必须考虑以下几点:

关于管道的命名，请看这里:https://msdn.microsoft.com/en-us/library/windows/desktop/aa365783(v=vs.85).aspx。它解释了当您在服务器上创建管道时，您必须使用''.'pipe'PipeName符号来标识本地机器(这是由. net包装器为您处理的)。但是，当您连接到管道时，您必须通过在管道URL中包含服务器名称来确保您连接到正确的服务器。''ServerName'pipe'PipeName

您必须考虑的另一个方面是访问控制。您必须确保管道的创建具有适当的权限，以允许远程客户端连接到它。https://msdn.microsoft.com/en-us/library/windows/desktop/aa365600 (v = vs.85) . aspx。请确保正确设置了管道的ACL。

---

根据你对问题的描述，听起来你的问题可能与命名有关。

这里是一些示例代码从服务器我写了一会儿:

private void SpawnServer()
{ 
    PipeSecurity pipeSa = new PipeSecurity();
    // let everyone read from the pipe but not write to it
    // this was my use case - others may be different
    pipeSa.SetAccessRule(new PipeAccessRule("Everyone", PipeAccessRights.Read, System.Security.AccessControl.AccessControlType.Allow));
    pipeSa.SetAccessRule(new PipeAccessRule(new SecurityIdentifier(WellKnownSidType.BuiltinUsersSid, null), PipeAccessRights.Read, System.Security.AccessControl.AccessControlType.Allow));
    pipeSa.SetAccessRule(new PipeAccessRule(new SecurityIdentifier(WellKnownSidType.BuiltinAdministratorsSid, null), PipeAccessRights.ReadWrite, System.Security.AccessControl.AccessControlType.Allow));            
    pipeSa.SetAccessRule(new PipeAccessRule(new SecurityIdentifier(WellKnownSidType.ServiceSid, null), PipeAccessRights.FullControl, System.Security.AccessControl.AccessControlType.Allow));
    pipeSa.SetAccessRule(new PipeAccessRule(WindowsIdentity.GetCurrent().Owner, PipeAccessRights.FullControl, System.Security.AccessControl.AccessControlType.Allow));            
    var pipeInstance = new NamedPipeServerStream(_pipeName, PipeDirection.InOut, 128, PipeTransmissionMode.Byte, PipeOptions.Asynchronous | PipeOptions.WriteThrough, 128, 128, pipeSa);
    PipeClient pipeClient = new PipeClient(pipeInstance, Interlocked.Increment(ref _totalclients));
    pipeInstance.BeginWaitForConnection(HandlePipeConnection, Tuple.Create(pipeInstance, pipeClient));
}
// this method asynchronously handles a new pipe connection and starts
// another server to handle other incoming connections
private void HandlePipeConnection(IAsyncResult ar)
{
    var pipeServer = (ar.AsyncState as Tuple<NamedPipeServerStream, PipeClient>).Item1;
    var pipeClient = (ar.AsyncState as Tuple<NamedPipeServerStream, PipeClient>).Item2;
    try
    {
        pipeServer.EndWaitForConnection(ar);
        // not shown here, I had the server
        //   send the new client a message upon connect    
        // if (!pipeClient.SendMessage(announceMessage))
        //      throw new Exception("Send message failed for new pipe client connection!");
        pipeClient.Error += PipeClient_Error;
        pipeClient.Disposed += PipeClient_Disposed;
        pipeClient.MessagesReceived += PipeClient_MessagesReceived;
        pipeClient.Read();
    }
    catch (Exception exc)
    {                   
        // Log Exception
        pipeClient.Dispose();
    }
    try
    {
        SpawnServer();
    }
    catch (IOException)
    {
       // if an IO error occurs, most likely it's because max pipe clients reached..
       // in my case I was raising an event here
    }
    catch (Exception exc)
    {
       // otherwise handle the error here (raise another event - not shown..)
    }
}

上面的代码使用了一个名为PipeClient的类，这是我编写的一个类，它包装了一个NamedPipeClientStream，以便以一种易于与客户端接口的方式公开它。该类包含用于读取和写入管道客户端流的助手方法，以及在接收(读取)数据和发生错误时引发的一些事件。我不打算粘贴完整的类实现因为它与问题没有直接关系但我将粘贴在构造函数

下面

public class PipeClient
    : IDisposable
{    
    private PipeStream _pipeInstance = null;
    private bool _disposed = false;
    private int _clientId = 0;
    public PipeClient(PipeStream pipeInstance, int clientid)
    {
        _pipeInstance = pipeInstance;
        // this class can be used both by clients and by the server to
        //   represent connected clients 
        // on the server, the clients are already connected; for clients code they are not and the stream will be of a different kind
        if (!_pipeInstance.IsConnected && _pipeInstance is NamedPipeClientStream)
            ((NamedPipeClientStream)_pipeInstance).Connect(100);
        _clientId = clientid;
        // more internals being set up here (not shown) 
        //   such as buffers for reads, queue for messages to send out etc.
    }
    // convenience constructor to create a pipe client from a pipe name 
    public PipeClient(string pipeName, bool readOnly)
        : this(new NamedPipeClientStream(".", pipeName, readOnly ? PipeDirection.In : PipeDirection.InOut, PipeOptions.Asynchronous), 0)
    {
    }
    // rest of the class not shown..
}