DCOM security
WinXPTalk.com Forum Index WinXPTalk.com
Forums for Windows XP users.
 
 FAQFAQ   MemberlistMemberlist     RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 
 
Google
 
Web winxptalk.com
DCOM security

 
Post new topic   Reply to topic    WinXPTalk.com Forum Index -> Network
Author Message
Andrew Jarvis
Guest
Posted: Tue Dec 21, 2004 12:23 pm    Post subject: DCOM security Reply with quote
I am having problems creating a DCOM component under Windows XP SP2.

I am creating the component locally to eliminate any remote access issues.

When I set the identity to "The interactive user" I can create the component
okay so I know that its registered okay and all its dependencies are
present.

When I set the identity to the logged on user but specified explicitly under
"This user" I get VB error "ActiveX component can't create object".

What is the difference between "interactive user" and specifying the same
user under "This user"?

I have tried adding "Everyone" with full control under each security section
to no avail.

I have checked for any DCOM restrictions in "Local Security Settings\Local
Policies\Security Options" but none are set.

Where else should I look?

O my own computer there are only six policies in "Local Security
Settings\Local Policies\Security Options" - four "Accounts", a "Network
access" and a "Network security". On the problem computer there are
sixty-four.

What has added these additional policies?
Back to top
Andrew Jarvis
Guest
Posted: Tue Dec 21, 2004 12:23 pm    Post subject: Re: DCOM security Reply with quote
PS. This is part of a distributed application that worked adequately until
we installed SP2.
Back to top
Roger Abell
Guest
Posted: Thu Dec 23, 2004 1:18 pm    Post subject: Re: DCOM security Reply with quote
Hey, no apollogies needed nor expected :-)
Glad you sorted it.

--
Roger Abell
Microsoft MVP (Windows Security)
MCSE (W2k3,W2k,Nt4) MCDBA
"Andrew Jarvis" <someone@somewhere> wrote in message
news:%23SXlwtC6EHA.2788@TK2MSFTNGP15.phx.gbl...
Quote:
Finally figured it out.

In the environment path variable, the drive letter for the path of the
dependent DLL was assigned by "cmd /c subst ..." in the Startup folder!
Therefore it did not exist in the new user context.

Apologies for wasting your time.

AJ

Back to top
 
Post new topic   Reply to topic    WinXPTalk.com Forum Index -> Network All times are GMT
Page 1 of 1

 
 You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Office Forums Access Forums Windows Server Exchange Server Help
New Topics Powered by phpBB