>>
>>I don't have anything else to add, other than to see some KB articles: Q197814, Q186818.
>> If it was a security thing, the administrative user account should have taken care of that. If it is something on MTS hosted object code, try writing a text file with error info in the Error event of the class. Check if the MTS component being called becomes active at all on the MTS Explorer.
>
>We've been through the KB and didn't find anything helpful. It kept referring to things on the server, but I don't see how this can be the case. Some client computers can instantiate the object and others can't. Something is different on the clients, but we can't figure out what.
>
>We've checked things out on the server and the component does not become active in MTS Explorer.

This is just a SWAG, but do all of the Win95 clients have the same version of DCOM installed?