Re: Windows Firewall blocking LSASS, causing DCOM launch error
- From: "Paul Baker [MVP, Windows Desktop Experience]" <paulrichardbaker@xxxxxxxxxxxxxxxx>
- Date: Fri, 2 May 2008 09:26:24 -0400
Jeffrey,
Yes, I have read about these changes in Windows Server 2003 SP1 and checked
the permissions. The user is not a member of the Distributed COM Users
group, but is a member of the Administrators group which gives them the
launch, activation and access permissions needed. I tried adding the user to
the Distributed COM Users group anyway, and it made no difference.
I think you missed the point that this is a firewall issue. If I disable the
Windows Firewall service, it works as expected.
Paul
""Jeffrey Tan[MSFT]"" <jetan@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:Pe6%23YNDrIHA.1784@xxxxxxxxxxxxxxxxxxxxxxxxx
Hi Paul,
Does the 2003 SP1 server have more than one network adapter, even if it is
disabled? Is Routing and Remote access enabled on the server?
Have you checked your DCOM security configuration on Win2003 SP1? Win2003
SP1 introduced the new "Distributed COM Users (Built in Group)". I see one
internal similar case was resolved by adding the user into the
"Distributed
COM Users" group so that the user has the "remote activation" permission.
Can you give it a try?
The article below contains more details of the default DCOM security
setting for various users and the security enhancement of Win2003 SP1:
"DCOM Security Enhancements in Windows XP Service Pack 2 and Windows
Server
2003 Service Pack 1"
http://msdn.microsoft.com/en-us/library/ms679714(VS.85).aspx
I will wait for your further information. Thanks.
Best regards,
Jeffrey Tan
Microsoft Online Community Support
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msdnmg@xxxxxxxxxxxxxx
==================================================
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: Windows Firewall blocking LSASS, causing DCOM launch error
- From: "Jeffrey Tan[MSFT]"
- Re: Windows Firewall blocking LSASS, causing DCOM launch error
- References:
- Windows Firewall blocking LSASS, causing DCOM launch error
- From: Paul Baker [MVP, Windows Desktop Experience]
- RE: Windows Firewall blocking LSASS, causing DCOM launch error
- From: "Jeffrey Tan[MSFT]"
- Windows Firewall blocking LSASS, causing DCOM launch error
- Prev by Date: Re: Non-interactive process launched by DCOM does not have network access
- Next by Date: Re: Getting all security groups without a token?
- Previous by thread: RE: Windows Firewall blocking LSASS, causing DCOM launch error
- Next by thread: Re: Windows Firewall blocking LSASS, causing DCOM launch error
- Index(es):
Relevant Pages
|
