By default DCOM for Windows 95 does not allow remote machines to connect to running objects. By default, the EnableRemoteConnect named-value is set to "N". To enable remote connections, change this value to "Y". The OLE/COM Object Viewer has a user interface that you can use to do this in the File.System Configuration... dialog box. Changing this value requires a reboot.
If EnableRemoteConnect is not set to "Y" then all incoming calls will be rejected. (The caller will, typically, get an RPC_S_SERVER_UNAVAILABLE return code.) Remote calls from the machine will work (assuming the EnableDCOM registry named-value is set to "Y").
All processes on Windows 95 run with the same security settings—those belonging to the currently logged on user. Because it would, therefore, not be possible to securely launch a process from another machine, DCOM on Windows 95 does not support remote activation and will never launch a process. Remote clients can still make connections to COM servers running under Windows 95, however, as long as the process is already running, CoRegisterClassObject has been called, and the EnableRemoteConnect registry key has been set to "Y". Also, remote connects are allowed on file moniker binds.
The DefaultLaunchPermission and LaunchPermission registry values have no effect on Windows 95.