# Client connections to server with multiple NICs

**URL:** <https://forum.inductiveautomation.com/t/client-connections-to-server-with-multiple-nics/90473>\
**Category:** Ignition\
**Tags:** vision, ignition81\
**Created:** [May 16, 2024, 6:50am UTC](https://forum.inductiveautomation.com/t/client-connections-to-server-with-multiple-nics/90473 "2024-05-16T06:50:46Z")\
**Posts on this page:** 1\
**Showing post:** 4

<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:** [May 17, 2024, 11:38am UTC](https://forum.inductiveautomation.com/t/client-connections-to-server-with-multiple-nics/90473/4 "2024-05-17T11:38:11Z")

</div>

> [@taglias](#):
>
> it tries to connection to both the HMI network and the redundancy network

That is a design error. The redundant gateway needs to be on the exact same networks as the primary gateway. And both primary and redundant gateways need to be set to use their names as their public addresses.

If you are connecting remotely, put entries in your own `/etc/hosts` file with the appropriate names if you cannot make your local DNS provide them.

(In most cases, there should not **be** a redundancy network. It can lead to "split brain" situations.)

---

_[View the full topic](https://forum.inductiveautomation.com/t/client-connections-to-server-with-multiple-nics/90473)._