Re: Named Pipes Restriction
- From: jetan@xxxxxxxxxxxxxxxxxxxx ("Jeffrey Tan[MSFT]")
- Date: Mon, 24 Jul 2006 02:59:05 GMT
Hi Vinzenz,
Thanks for your post!
Based on my understanding, your named pipe application runs under certain
user account on customer's machine which will cause your application to
fail with "Access is denied". You want to find the correct way to configure
the customer machine to grant the enough right to that account.
First, I assume the API you used to create named pipe that is failing with
"Access is denied" is CreateNamedPipe.
Normally, all the security settings for the user accessing account Named
pipe are listed in "Local Security Settings" MMC. You may open it in
Control Panel->Administritive Tools->Local Security Settings.
Then you may check "Local Policies"->"Security Options". In the right
panel, you may check all the security items starts with "Network Access:",
there are several items related to Named pipe.
From your reply, it seems that you have awared of the potential risk ofchanging the security policy. Do you find another workaround for the issue?
If so, please feel free to share with us.
Additionally, it seems there is another non-admin account which you can
create named pipe without any problem, why not run your application under
that account? This will save you a lot time to troubleshoot the security
problem.
Anyway, if you still can not find a workaround/solution to your problem,
please feel free to feedback, I will work with you. Thanks.
Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
.
- Follow-Ups:
- Re: Named Pipes Restriction
- From: Vinzenz Feenstra
- Re: Named Pipes Restriction
- References:
- Named Pipes Restriction
- From: Vinzenz Feenstra
- Re: Named Pipes Restriction
- From: James Brown
- Re: Named Pipes Restriction
- From: Vinzenz Feenstra
- Named Pipes Restriction
- Prev by Date: Re: setting SeDebugPrivilege privilege
- Next by Date: Re: setting SeDebugPrivilege privilege
- Previous by thread: Re: Named Pipes Restriction
- Next by thread: Re: Named Pipes Restriction
- Index(es):
Relevant Pages
|