That is a good idea. The DLL is in C#, it is called from a VB .NET
application. How do I set it up to use an administration account, if I don't
know the PWD?
Not sure if you can do it without knowing the password. You could set up a
"service" account - an account explicitly for your application that has
limited admin privileges to allow the socket communication but restrict
other areas.
Thanks,
Sam

Signature
_______________________________
Sam Santiago
ssantiago@n0spam-SoftiTechture.com
http://www.SoftiTechture.com
_______________________________
> That is a good idea. The DLL is in C#, it is called from a VB .NET
> application. How do I set it up to use an administration account, if I don't
> know the PWD?
>
> > What environment/language are you developing in? With .NET you can
> > potentially set the thread identity:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlr
fSystemThreadingThreadClassCurrentPrincipalTopic.asp
> > Thanks,
> >
[quoted text clipped - 33 lines]
> > >
> > > I look forward to your replies!
Brad Simon - 18 Oct 2004 20:37 GMT
Unfortunately that is not an option. I am looking into the Impersonate
command, it looks quite tricky, but it may work.
It shouldn't be this hard, but who am I to say :)
> Not sure if you can do it without knowing the password. You could set up a
> "service" account - an account explicitly for your application that has
[quoted text clipped - 60 lines]
> > > >
> > > > I look forward to your replies!