DCOM servers configuration tips
- Last UpdatedFeb 28, 2025
- 1 minute read
Here are some tips for configuring DCOM servers:
-
Users on Trusted Domains need to have an account created for them with matching usernames and passwords on the DCOM server’s domain. The purpose of this is to set up a matching SID (Security ID). Trusted Domain group members need to have remote DCOM servers initiated for them by a Primary Domain member.
A Trusted Domain is a setup that allows resources from one domain to access resources in another domain. Trusted Domains typically go in one direction, although they can be bi-directional. The process of one domain trusting another and passing user authentication to another domain is called pass-through authentication.
-
Workgroup machines are individual domains, so you must set up matching SIDs (usernames and passwords) to establish connections between the machines.
-
Always create a Global Group through NT Server’s User Manager, and add the members for whom you want to provide access to specific DCOM servers. Then, use DCOMCnfg to set the launch permissions to that group. This makes administration easy to manage, even if you have a group that contains everyone.
-
If the client application implements a sink (callback), the server must be able to call the client back .You must configure the client to accept calls from the server. Just because the client can connect to the server doesn’t mean the server can call the client back.