How to set Named Pipe permssions for non-admin access?
From: Mark McWiggins (mark_at_printcop.com)
Date: 03/17/04
- Next message: cyberninja: "Re: loopback interface/Firewall/Winsock"
- Previous message: qfel: "Re: loopback interface/Firewall/Winsock"
- Next in thread: cyberninja: "RE: How to set Named Pipe permssions for non-admin access?"
- Reply: cyberninja: "RE: How to set Named Pipe permssions for non-admin access?"
- Reply: Eugene Gershnik: "Re: How to set Named Pipe permssions for non-admin access?"
- Messages sorted by: [ date ] [ thread ]
Date: 17 Mar 2004 15:45:15 -0800
I'm revising a chat application to use named pipes.
I have it working fine from two command lines running as administrator
on both machines. But in production it will be launched from a service
running as "Local System account" (under 'Log On' in the 'properties'
page
of its service). It also have "Allow service to interact with desktop"
checked.
When I invoke the chat program from this service (via 'spawn') I get
ERROR_ACCESS_DENIED (code 5). For completeness I tried command line
invocation from a limited user account and got error 1326 (logon
error).
How do I set the permissions of the named pipe to allow the service to
connect?
I've seen various descriptions of security tokens and ACLs, but
haven't seen a good description of doing this sort of thing.
Thanks much for any guidance whatsoever.
Mark McWiggins
425-369-8286
- Next message: cyberninja: "Re: loopback interface/Firewall/Winsock"
- Previous message: qfel: "Re: loopback interface/Firewall/Winsock"
- Next in thread: cyberninja: "RE: How to set Named Pipe permssions for non-admin access?"
- Reply: cyberninja: "RE: How to set Named Pipe permssions for non-admin access?"
- Reply: Eugene Gershnik: "Re: How to set Named Pipe permssions for non-admin access?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|