|
|
Welcome to Vista Banter. You are currently viewing our boards as a guest which gives you limited access to view most discussions, articles and access our other FREE features. By joining our free community you will have access to ask questions and reply to others posts, upload your own photos and access many other special features. Registration is fast, simple and absolutely free so please, join our community today! If you have any problems with the registration process or your account login, please contact contact support. |
|
|||||||
| Security and Windows Vista A forum for discussion on security issues with Windows Vista. (microsoft.public.windows.vista.security) |
|
|
LinkBack | Thread Tools | Display Modes |
October 12th 06, 04:11 PM
posted to microsoft.public.windows.vista.security
|
|||
|
|||
DCOM security problem again just like XP SP2
When XP SP2 was released alot of applications broke as they did not have
permissions under DCOM (dcomcnfg) Well lo and behold the application I am testing has broken again in Vista (RC2) even though I think I have set the DCOM settings correctly. Basically the application is calling a remote component I think successfully, but it is doing so asyncronously so the component is required to have security to call back to the client. So by adding security into dcomcnfg for the service account that the component is running as under XP SP2 allows it to call back, so why doesn't it in Vista? I don't know! Is there something else security wise I need to know about? Thanks in advance 
|
Linear Mode
