# Why does ThinLinc try to connect to a different IP address than the one specified?

**URL:** <https://community.thinlinc.com/t/why-does-thinlinc-try-to-connect-to-a-different-ip-address-than-the-one-specified/618>\
**Category:** Knowledge Base\
**Tags:** networking, tlclient\
**Created:** [30 May 2023 02:25 UTC](https://community.thinlinc.com/t/why-does-thinlinc-try-to-connect-to-a-different-ip-address-than-the-one-specified/618 "2023-05-30T02:25:54Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![psuter](https://avatars.discourse-cdn.com/v4/letter/p/ed655f/32.png) [@psuter](https://community.thinlinc.com/u/psuter)\
**Post date:** [18 May 2026 18:58 UTC](https://community.thinlinc.com/t/why-does-thinlinc-try-to-connect-to-a-different-ip-address-than-the-one-specified/618/4 "2026-05-18T18:58:11Z")

</div>

thanks for this useful article. i actually ran into this on my host where docker was running as well, suddenly thinlinc agent thought that one of the virtual docker interfaces was the primary one.

may I add, that i had to restart the vsmagent systemd service after changing the agent\_hostname setting for it to take effect:

```auto
$ sudo su -
# tl-config /vsmagent/agent_hostname=10.10.0.100
# systemctl restart vsmagent.service

```

where 10.10.0.100 was the ip of the agent host.

---

_[View the full topic](https://community.thinlinc.com/t/why-does-thinlinc-try-to-connect-to-a-different-ip-address-than-the-one-specified/618)._