Control.com - Nerds in Control

We have an exaopc gateway in a CS3000 DCS network configured for the APC controller from Honeywell. EXAOPC and APC controller systems are sitting over the DCS control LAN (ethernet IP scheme 172.17.1.xxx). we have tried to change the n/w configuration with keeping the exaopc in the DCS LAN & APC controller connected to EXAOPC(defined a different IP schemed for EXAOPC & APC systems while keeping the EXAOPC connected to the DCS with old IP scheme). we have tried with a simple hub connecting b/w exaopc & apc controller. Tested the connectivity with matrikon. but failed & it says, couldn't find any exaopc server.

1) what may be the reason?

2) can any body suggest the corrective action?

3) is it require a domain controller for EXAOPC server-client connectivity?

Dear Rajeeb Answers to your questions:

1. The reason could be the firewall setting between the ExaOPC and the LAN

3. No domain controller is required for ExaOPC, since it is only an OPC server (not a windows machine)

The easiest way is to get the honeywell engineer to coordiante with local yokogawa engineer. Together, they would be able to solve the problem is a very short time.

Could also be a DCOM or Domain issue. Have you tested the connection using MatrikonOPC Tunneller? If you can browse/connect using OPC Tunneller then it narrows down to DCOM problems.

Eric Murphy
OPC Exchange
http://blog.matrikonopc.com

Dear Shahid & Murphy,

Thank you so much for taking enough time to reply my thread.

I have switched off the Microsoft Firewall at both the systems. Also given complete acess to the DCOM at both the systems. I have been using the matrikon OCP Explorer. Now i shall make a try with the Tunneller.

Rajeeb A