# Connecting to Cimplicity HMI OPC Server on remote PC

**URL:** <https://forum.inductiveautomation.com/t/connecting-to-cimplicity-hmi-opc-server-on-remote-pc/1340>\
**Category:** Archived Topics\
**Created:** [October 19, 2009, 9:00am UTC](https://forum.inductiveautomation.com/t/connecting-to-cimplicity-hmi-opc-server-on-remote-pc/1340 "2009-10-19T09:00:47Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![cjd1965](https://avatars.discourse-cdn.com/v4/letter/c/3d9bf3/32.png) [@cjd1965](https://forum.inductiveautomation.com/u/cjd1965)\
**Post date:** [October 19, 2009, 9:00am UTC](https://forum.inductiveautomation.com/t/connecting-to-cimplicity-hmi-opc-server-on-remote-pc/1340/1 "2009-10-19T09:00:47Z")

</div>

Hi  
I have a GE Cimplicity system with an OPC server running on a remote machine. I try to connect using

Host : \PCName  
Name : CIMPLICITY.HMI.OPCServer.1  
clsid: b01241e8-921b-11d2-b43f-204c4f4f5020

THe log says it cannot connect to the server.

If I run a kepware quick client to connect to cimplicity, it connects, no problem.

Anyone run into this?

---

<div class="post-metadata">

**Author:** ![cjd1965](https://avatars.discourse-cdn.com/v4/letter/c/3d9bf3/32.png) [@cjd1965](https://forum.inductiveautomation.com/u/cjd1965)\
**Post date:** [October 19, 2009, 7:04pm UTC](https://forum.inductiveautomation.com/t/connecting-to-cimplicity-hmi-opc-server-on-remote-pc/1340/2 "2009-10-19T19:04:38Z")

</div>

Thought… Does Factory SQL need to be connecting using a domain authentication. I have windows admin priveledges on both PC’s

---

<div class="post-metadata">

**Author:** ![Colby.Clegg](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/colby.clegg/32/3282_2.png) [@Colby.Clegg](https://forum.inductiveautomation.com/u/Colby.Clegg)\
**Post date:** [October 19, 2009, 8:30pm UTC](https://forum.inductiveautomation.com/t/connecting-to-cimplicity-hmi-opc-server-on-remote-pc/1340/3 "2009-10-19T20:30:19Z")

</div>

Hi,

One thing that often comes into play in situations like this is the fact that all OPC communication is handled by the FactorySQL service, which is a windows service running under the SYSTEM account by default.

Quick clients run under the logged in user, so they’ll appear different to the remote machine. You can try a few different things to verify this:  
A) Change the account that FactorySQL runs under by going to Services (Control Panel-\>Administrative tools), right clicking FactorySQL Service, selecting “properties”, and then going to the “Log On” tab.  
-OR-  
B) Search the forum for how to run FactorySQL as an application instead of a service.

If those work, you can either leave it like that, or open up the dcom settings on both machines to allow the service access. There are a few posts around here that talk about basic DCOM settings, and how to turn on DCOM logging in order to help track down the problem.

Regards,