Remote COM Access

[Malli_S]

Can some one help... I'm trying to acces a remote COM from local machine. I've a in-proc COM server (DLL), and want to acces it remotely. I was getting an error, when I tried with CoCreateInstanceEx(), i.e. "Class Not Registerd" from remote machine. so, I've exported (Registerd) it using 'Component Manager Snapp-in'. Right now I'm able to get the class access(because Class constructor gets called on remote machine), but it fails to get Interface pointer from class. And Interfaces implemented by class is also not shown in the snapp-in under 'Interfaces' Tag. Am I laggin somewhere? Is there any other way to do so? Please reply for the same. Thanks for anykind of help...... !! -Malli......!

[Siva Sankar Koyi]

Could you please try by registring the Proxy/Stub stuff on both machines... Thanks & Regars, Siva

[Malli_S]

Hi ! Thanks for answering, we did the same. we created proxy/stub dll and regeistered on both the machines. I would like to add one more query. I build 3 COM Servers(as a service, exe, and dll). we tested all the three for their performance. when we fire number of requests from remote machins(approximatly 100 requests, 10 requests per process, like such there are 10 process makin requests), every type of server behaved differently. Exe type COM server took almost 1 min 40 sec. Service type COM Server took almost 1 min 42 sec(appro same as exe server). But DLL type COM server took only 16 Sec. How this has happend. Can you explain the working of all these remote servers.... Is the object shared by the clients? - Malli... !

[Siva Sankar Koyi]

Need bit clarification.. How did you access the DLL from Remote machine, Did you run as a Surrogate process in Remote server ?? or you registered(copied) the source DLL to client machine.. Thanks, Siva Sankar

[Malli_S]

Hello Siva ! Actully I've registerd the proxy/stub dll. And using MMC-Component Services, I put that COM dll into COM Applications. this would make your COM dll to be used from remote machin. (this inturn make use of DLLHOST.exe as a surrogate). This is what the scenario.... -Malli...!