This is most likely a DCOM configuration issue.

See e.g.:
- www.opclabs.com/forum/com-connections/1345-dcom-for-opc-configuration-tutorial#1796
- www.opclabs.com/resources/technology-opc/opc-videos/opc-dcom
- www.google.com/search?q=dcom+opc
- www.opclabs.com/forum/connections-reconnections-com-dcom/124...ng-to-remote-machines-via-code

It should also be noted that the screenshot you attached is from a kind of "pre-connection" step: At that moment, the client is not trying to connect to any specific OPC server. It is trying to obtain a list of servers available on a remote machine, using so-called OpcEnum service (which should be installed on the remote machine; usually this is automatic with an OPC Server). This is just to let you know when you will be doing the DCOM stuff, that besides the OPC Server there is actually yet another component in play.

Can you do the same thing using some other OCP client, from the same client machine to the same server machine?

Regards

Are you sure you have the server identification correct? Machine name etc. The error looks like that the target computer cannot be reached by DCOM.

Can you post the piece of code that shows it (i.e. how you identify the server for QuickOPC), and at the same time, a screenshot from the other client where the connection is specified?

Thank you

Hello.

Can you *ever* connect with QuickOPC, or is it so that it has worked previously, but suddenly the error appeared (and does it then go away)?

Thank you