|
Posted by Insub Chang on August 2, 2005, 8:07 pm
Please log in for more thread options I think your dcom case is not that doomed, yet. Definately it is
security issue not com interop compatibility issue by SP1.
The goal of troubleshooting should be what account was access denied to
run what from your component. Since the old dcomcnfg.exe is migrated to
component services in Windows 2003, you should check com+ first.
Then turn on audit on your machine from local security policy. Also
turn on file systems audit on c: and the local disk drive your app runs
from.
This will give you a starting point to identify why your app is working
with local admin but not work without local admin.
imuraca wrote:
> Hi,
> I have made the same changes in Windows 2003 SP1, made in Windows XP SP2
> and the problem persist. I have read all the documentation about Windows
> 2003 SP1 and I have not found the correct settings. Is there a check list
> for resolve DCOM communication problem in Windows 2003 SP1 ?
>
> Thank you,
> Ivan
>
>
> > I suggest that you research the MS website for the docs for W2k3 SP1,
> > specifically the changes in SP1 docs that cover RCP and COM support.
> > The security was adjusted similarly as was done with XP SP2 and as
> > a result things that were previously configured in a potentially unsafe
> > mannor will break.
> >
> > --
> > Roger Abell
> > Microsoft MVP (Windows Security)
> > MCSE (W2k3,W2k,Nt4) MCDBA
> > > Hi,
> > > I have installed W2003 SP1. My application components uses DCOM to
> > > communicate between W2003 server and Windows XP. After installing SP1 on
> > > W2003 all the components do not work correctly while accessing the
> > registry
> > > and don't communicate between them. Only if I use an Administor Group
> user
> > > is everything ok. Can I use a user with only Power User previlege ? How
> > can
> > > I set W2003 correctly?
> > > Thanks,
> > > Ivan
> > >
> > >
> > >
> >
> >
| 
XML Sitemap