# Configured Thinlinc Server but new installed second network card no access

**URL:** https://community.thinlinc.com/t/configured-thinlinc-server-but-new-installed-second-network-card-no-access/138
**Category:** Community Support
**Tags:** dns, networking, tlserver, dhcp
**Created:** [29 March 2021 21:13 UTC](https://community.thinlinc.com/t/configured-thinlinc-server-but-new-installed-second-network-card-no-access/138 "2021-03-29T21:13:18Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![aaron](https://dub1.discourse-cdn.com/flex005/user_avatar/community.thinlinc.com/aaron/32/13_2.png) [@aaron](https://community.thinlinc.com/u/aaron)
#### Post date: [31 March 2021 17:20 UTC](https://community.thinlinc.com/t/configured-thinlinc-server-but-new-installed-second-network-card-no-access/138/4 "2021-03-31T17:20:16Z")

</div>

@gwagon

If `agent_hostname` is empty, it will default to the IP address of the primary network interface.

There are probably a number of ways you could configure your network to achieve what you’re after, however I suspect the easiest way is to run ThinLinc in cluster mode, with multiple agents to spread the load across.

---

_[View the full topic](https://community.thinlinc.com/t/configured-thinlinc-server-but-new-installed-second-network-card-no-access/138)._