Your response is slightly discouraging...
Yes, we have verified all that.... We can use your component to write to a Matrikon (for example) OPC server on a remote host. And we can also use a different client component to wirte to remote SISCO server.
It's combination of OPC Labs component, and SISCO that's giving us a heartburn. And, without having that combination working, your component becomes rather moot to us.

When AXS4ICCP is on the same box, you are probably specifying "localhost" or "" as the machine name, right?

When AXS4ICCP is on a remote host, how are you specifying the machine name? Do you browse for it, or is it hard-coded? If it is hard-coded, you may want to verify that the name is exactly the same as on the remote host... Zeroes and "O"s, "I"s and "1"s and "l", and even "8"s and "B"s can look quite similar depending on the fonts used. If you're specifying an IP Address, verify it.
Hope this helps!

Yes, it is. We eatablished that need during our previous discussion a few weeks back.

Quick thought - is the AXS4ICCP on the remote host running as a service?

Hi,
I'm using QuickOPC to read/write to a SISCO's AXS4ICCP OPC server on a remote host.
I use simple calls to ReadItemValue and WriteItemValue.
I'm successfully able to execute read/write request using QuickOPC libraries to SISCO AXS4ICCP server when the client and the server are on the same box.
I'm successfully able to execute read and write from to a remote host using another type of OPC server ( Matrikon's OPC Simulation server). From that I conclude that all my firewall and DCOM configuration are set correctly as it succeed.
However when I'm trying the same read/write test to the remote SISCO's AXS4ICCP server I always get an "Access is denied." error.
Using alternate OPC test client (OPC Rescue, Kepware's Quick OPC Client, Matrikon Explorer) from my client machine all successfully establish a connection with the remote AXS4ICCP OPC server.
Even with my code modified with another OPC access library (Kepware's Client ACE) successfully establish a connection.
Based on previous Posts in this forum I also played with EasyDAClient.ClientParameters.TurnOffActivationSecurity and EasyDAClient.MachineParameters.TurnOffActivationSecurity on the client box without any success.
Any help/advise is welcome.