In Netscape Navigator my ocx in the HTML page can not be loaded and seen. What should I do with my OCX codes and Navigator setting respectively to enable OCX in Navigator? 3x

DLL-based Component CA is developed with ATL Object wizard. Its features including: 1. single-threaded 2. custom interface 3. no aggregation support CA has only one interface named IA which has a method GetData: STDMETHOD(Receive)(/*[out]*/ long* pDataLength, /*[out, size_is(*pDataLength)]*/ unsigned char** ppData); A confusing fact is that: When I use CA in a normal MFC EXE, it works well. Then I use CA in an ATL-based EXE. In that EXE I have another Componet say CB. CB creates a thread say WorkingThread(). In WorkingThread(), I call CreateInsantance() to create CA: IA* pIA = NULL; RESULT hr = CoCreateInstance(CLSID_A, NULL, CLSCTX_INPROC_SERVER, IID_IA, (void**)&pIA); It failed with a HRESULT indicating "The interface IA is not supported by CLSID_A". I have included A.h and two const definition of CLSID_A and IID_A in the ATL EXE's source, the same as I did in the normal MFC EXE. If CA is a dual interface, no such troubles. So I assume this is related to custom interface. But how to solve this problem?

First client creates an instance of a remote COM object via CoCreateInstanceEx, then calls one of its method remotely. In that method, assume Checker(), some information of the client is checked to see if he has the right to access things on Server further. If OK, the Checker() will create an instance of another COM object named CoreServer, and transfer the pointer to one of its Interface back to Client. How can I finish the procedure with DCOM library? I think there maybe 3 ways for the Checker() to create and transfer: 1.CoCreateInstance 2.CoCreateInstanceEX 3.Moniker but no way seems work :confused: please help me, thanks.

Register the Server.exe and its proxy.dll (if available) on the client machine too. Then you can delete those two files from the client machine. It maybe work.

Suppose a client connected with a remote DCOM component by creating its instance and then calling its methods, can the component know where the client comes from, or what IP the client has? If can, how? And when firewall exists in the client side, how is the situation then? Thanks a lot!