# Setup with initial connections

**URL:** <https://forum.inductiveautomation.com/t/setup-with-initial-connections/6955>\
**Category:** Archived Topics\
**Created:** [July 31, 2013, 9:21am UTC](https://forum.inductiveautomation.com/t/setup-with-initial-connections/6955 "2013-07-31T09:21:15Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![neramdaman](https://avatars.discourse-cdn.com/v4/letter/n/a183cd/32.png) [@neramdaman](https://forum.inductiveautomation.com/u/neramdaman)\
**Post date:** [July 31, 2013, 9:21am UTC](https://forum.inductiveautomation.com/t/setup-with-initial-connections/6955/1 "2013-07-31T09:21:15Z")

</div>

I am a bit new to OPC, and so I am trying to test some connections and see how they run. Inside an internal network (home based lan), I have the Ignition OPC server running on a desktop. The IP address for the desktop is 192.168.254.115. I have started a project using the simulated PLC driver.

By the way, I have installed this on a linux desktop, running openSUSE 12.3. The networking issues should be basically the same, I think, as any other platform.

When I open the gateway and go to Configure -\> OPC-UA -\> Certificates, under “This Gateway”, it has my ip address listed as:

```auto
IP Address 192.168.1.101
```

At one time, I think before I installed ignition, I did have the local network with the ip addresses using 192.168.1.xxx instead of 192.168.254.xxx.

My ifconfig status shows:

`eth0 Link encap:Ethernet HWaddr 48:5B:39:38:8A:57  
          inet addr:192.168.254.115 Bcast:192.168.254.255 Mask:255.255.255.0
          inet6 addr: fe80::4a5b:39ff:fe38:8a57/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:138343 errors:0 dropped:0 overruns:0 frame:0
          TX packets:193719 errors:0 dropped:0 overruns:0 carrier:5
          collisions:0 txqueuelen:1000 
          RX bytes:48261869 (46.0 Mb) TX bytes:81755684 (77.9 Mb)
`

My goal is to be able to connect to the gateway from a remote pc on the same lan. My laptop, which connects by wireless, has an ip address of 192.168.254.118.

Is it possible to connect to the gateway by the lan? I have been assuming that I should do this before I try and connect a client remotely through the lan.

Do I need to force the OPC-UA server to be set up on the correct ip address? I don’t know why it picked up the old addressing scheme.

Thanks for your help in advance.

---

<div class="post-metadata">

**Author:** ![Dravik](https://avatars.discourse-cdn.com/v4/letter/d/e274bd/32.png) [@Dravik](https://forum.inductiveautomation.com/u/Dravik)\
**Post date:** [July 31, 2013, 2:47pm UTC](https://forum.inductiveautomation.com/t/setup-with-initial-connections/6955/2 "2013-07-31T14:47:26Z")

</div>

Neramdaman:

Under opc-ua - settings , check what the IP is set too.

Also check to see what your /etc/hosts file contains. It may still have an old 192.168.1.101 entry.

-Mike

---

<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:** [July 31, 2013, 2:57pm UTC](https://forum.inductiveautomation.com/t/setup-with-initial-connections/6955/3 "2013-07-31T14:57:24Z")

</div>

[quote=“Dravik”]Neramdaman:

Under opc-ua - settings , check what the IP is set too.

Also check to see what your /etc/hosts file contains. It may still have an old 192.168.1.101 entry.

-Mike[/quote]

In addition to this, you can regenerate the certificates on the certs page and they will include the currently configured hostname/IP address.

---

<div class="post-metadata">

**Author:** ![neramdaman](https://avatars.discourse-cdn.com/v4/letter/n/a183cd/32.png) [@neramdaman](https://forum.inductiveautomation.com/u/neramdaman)\
**Post date:** [August 8, 2013, 2:00pm UTC](https://forum.inductiveautomation.com/t/setup-with-initial-connections/6955/4 "2013-08-08T14:00:54Z")

</div>

Thank you. Refreshing my ip address and then regenerating the certificates did the trick!
