# OPC Connection to Another Ignition OPC UA Server on a different domain

**URL:** <https://forum.inductiveautomation.com/t/opc-connection-to-another-ignition-opc-ua-server-on-a-different-domain/30680>\
**Category:** Ignition\
**Created:** [December 12, 2019, 11:26pm UTC](https://forum.inductiveautomation.com/t/opc-connection-to-another-ignition-opc-ua-server-on-a-different-domain/30680 "2019-12-12T23:26:52Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![jpence](https://avatars.discourse-cdn.com/v4/letter/j/a183cd/32.png) [@jpence](https://forum.inductiveautomation.com/u/jpence)\
**Post date:** [December 12, 2019, 11:26pm UTC](https://forum.inductiveautomation.com/t/opc-connection-to-another-ignition-opc-ua-server-on-a-different-domain/30680/1 "2019-12-12T23:26:52Z")

</div>

I am creating a connection on an 8.0.6 ignition to another ignition server running 7.9.12

GIF steps

1. Endpoint Discovery
2. Choose A Server
3. Security setup
4. Left auth blank

 ![ignitionissue](https://us1.discourse-cdn.com/inductiveautomation/original/2X/d/d761839cadcc570a7d50e7e33940281ba39b9427.gif)

I created a new Client cert on the 8.0.6

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/2X/1/15df98381dfb4cc253341fa9ff114d2a53aedb70.png)

I then applied this to the 7.9.12 server

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/2X/c/cf4e4833fed27d5d50dab97648ea978d03b0aefb.png)

But the OPC Connection on 8.0.6 server shows Faulted.

Can someone point me in the right direction here?

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [December 12, 2019, 11:39pm UTC](https://forum.inductiveautomation.com/t/opc-connection-to-another-ignition-opc-ua-server-on-a-different-domain/30680/2 "2019-12-12T23:39:51Z")

</div>

Are these two servers running on the same machine? Your GIF shows you connecting to localhost…

And whatever you’re doing with that client certificate isn’t necessary. 7.9.x doesn’t have any kind of certificate handling.

---

<div class="post-metadata">

**Author:** ![jpence](https://avatars.discourse-cdn.com/v4/letter/j/a183cd/32.png) [@jpence](https://forum.inductiveautomation.com/u/jpence)\
**Post date:** [December 13, 2019, 12:37am UTC](https://forum.inductiveautomation.com/t/opc-connection-to-another-ignition-opc-ua-server-on-a-different-domain/30680/3 "2019-12-13T00:37:33Z")

</div>

No, not on the same server. I don’t see the localhost you refer to. The gif shows 127.x.x.x not localhost.

I was trying to follow the Kepware OPC connection article. Is there an article on how to connect one ignition opc ua server with another ?

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [December 13, 2019, 1:18am UTC](https://forum.inductiveautomation.com/t/opc-connection-to-another-ignition-opc-ua-server-on-a-different-domain/30680/4 "2019-12-13T01:18:46Z")

</div>

> [@jpence](#):
>
> The gif shows 127.x.x.x not localhost.

Say what? 127.x.x.x is defined (By IETF) to be only valid for localhost. It is never valid for anything else.

---

<div class="post-metadata">

**Author:** ![jpence](https://avatars.discourse-cdn.com/v4/letter/j/a183cd/32.png) [@jpence](https://forum.inductiveautomation.com/u/jpence)\
**Post date:** [December 13, 2019, 2:37am UTC](https://forum.inductiveautomation.com/t/opc-connection-to-another-ignition-opc-ua-server-on-a-different-domain/30680/5 "2019-12-13T02:37:07Z")

</div>

Ah. Not an expert network guy here. That explains why I got so far.

I kept on using the IP address of the machine and it wasn’t working ( error code to follow) so I did a netstat in power shell to look for which IP address was associated with port 4096… and yeah 127.x.x.x came up.

Back to the drawing board

---

<div class="post-metadata">

**Author:** ![jpence](https://avatars.discourse-cdn.com/v4/letter/j/a183cd/32.png) [@jpence](https://forum.inductiveautomation.com/u/jpence)\
**Post date:** [December 13, 2019, 2:04pm UTC](https://forum.inductiveautomation.com/t/opc-connection-to-another-ignition-opc-ua-server-on-a-different-domain/30680/6 "2019-12-13T14:04:07Z")

</div>

![image](https://us1.discourse-cdn.com/inductiveautomation/original/2X/b/bea40997927cb63d37bdaa5831cf60d7a6a2a49f.png)  
Here is the remote server, IP address 10.64.61.151, showing port 4096 for the OPC-UA service

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/2X/9/9bf1b9bba3e206d5d77118de8b3b7cf0de22cb97.png)  
when i try to connect from the main, I get this error

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [December 13, 2019, 2:42pm UTC](https://forum.inductiveautomation.com/t/opc-connection-to-another-ignition-opc-ua-server-on-a-different-domain/30680/7 "2019-12-13T14:42:53Z")

</div>

Connection Refused is typically due to a firewall along the way.

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [December 13, 2019, 2:45pm UTC](https://forum.inductiveautomation.com/t/opc-connection-to-another-ignition-opc-ua-server-on-a-different-domain/30680/8 "2019-12-13T14:45:09Z")

</div>

Or in this case, because the other server is clearly configured to bind to “localhost”.

Replace “localhost” in that configuration with the IP (10.64.61.151?) of that server and then restart Ignition.

If you don’t manage to get this working soon support would be able to walk you through it pretty quick. Just make sure you call, not email.

---

<div class="post-metadata">

**Author:** ![jpence](https://avatars.discourse-cdn.com/v4/letter/j/a183cd/32.png) [@jpence](https://forum.inductiveautomation.com/u/jpence)\
**Post date:** [December 13, 2019, 3:04pm UTC](https://forum.inductiveautomation.com/t/opc-connection-to-another-ignition-opc-ua-server-on-a-different-domain/30680/9 "2019-12-13T15:04:37Z")

</div>

Thank you Phil and Kevin

I changed the Endpoint Address to 10.64.61.151 and restarted the Ignition Gateway service

I then went back to the other server and attempted to connect again with the same result.

I’ll give support a call.

---

<div class="post-metadata">

**Author:** ![jpence](https://avatars.discourse-cdn.com/v4/letter/j/a183cd/32.png) [@jpence](https://forum.inductiveautomation.com/u/jpence)\
**Post date:** [December 13, 2019, 7:33pm UTC](https://forum.inductiveautomation.com/t/opc-connection-to-another-ignition-opc-ua-server-on-a-different-domain/30680/10 "2019-12-13T19:33:06Z")

</div>

Joe R in support helped me out here

The server and client certs on the remote side were wrong ( had odd looking ip address)

Once we fixed that I was connected
