Configured Thinlinc Server but new installed second network card no access

Dear folk,

I have a thinlinc server on a ubuntu computer which is working and reachable from network with dhcp server 1 such that all clients can work with the thinlinc client software. I have installed a second network card on the server with its own dhcp server 2 on the network

When a client is on the second network he or she can build a ssh connection to the ubuntu server via terminal but, now the problem is, if I try to build a connection via the thinlinc client it tries to reach the thinlinc server at but this fails and the thinlinc client doesnt change and it stays frozen.

How do I have to set the thinlinc server OR the ubuntu network configuration such that clients on the second network will get through the second nic a connection to the thinlinc server which was initally configured on the network???

We need this due to network balance reasons such that many users are can work on both network cards.

Please give me a help I would be very thankful.


@gwagon what is your agent_hostname parameter (see here) set to in vsmagent.hconf? You can check like this:

$ tl-config /vsmagent/agent_hostname

The ThinLinc client makes two connections per login, one to the master and one to the agent. In your case, both master and agent are on the same machine. The agent is identified to the client using this agent_hostname parameter, and if this parameter is set to your address, this is what the client will try to use for the second connection, regardless of which network it is on.

If I understand your setup correctly, you would need to use some kind of split-DNS configuration. For example, you would need to set agent_hostname to a resolvable hostname (e.g., and make sure that this hostname resolves correctly for each client. That is, it would need to resolve to for clients on the network, and for clients on the network.

Another option would be to run ThinLinc in cluster mode (see here). So you would have one master server and several agents, all on the same network, but each with their own network interface. ThinLinc will then load-balance sessions across each agent in the cluster.


Dear Aaron,

thank you very much for your reply and friendly statement.

I looked up and tl-config /vsmagent/agent_hostname gives me empty message and after I looked up in /opt/thinlinc/etc/conf.d/vsmagent.hconf there is no entry in agent_hostname=

I agree the dns split configuration is apparently the solution OR my guess, not sure about this, maybe I need to configure a linux route rule for traffic which comes from 192.168.1. to 192.168.0. where the vsm server and agent are located such that they also reply and use the correct network 192.168.0. for clients of second network.

I would be very happy if you have further suggestions and I am looking forward to your reply.

Do you need further information?

Best Regards


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.

I’m not sure how a cluster configuration would help in this case ?
The split DNS or static routes on the client should absolutely work. The split DNS is of course the best way to handle this, if possible.
The static route options on all clients also works, but is not that nice.
You probably could assign static host routes via DHCP.

Hello together,

I am interested with dns split or static route solution.

What for example do I have to configurate at the ububtu server for static route solutions?

Do I need a separate DNS Server for the dns split solution?

What are the steps for both solutions?

King Regards

If the thinlinc server requires you to connect to
A static host route could solve the problem. This is not a scalable solution but might work for you.
In this setup i don’t think you need to enable IP forwarding on the thinlinc server.

A better way is to setup split DNS. The short version is that if your thinlinc servers is named “thinlinc”. Clients on network should resolve “thinlinc” to and the clients on the network should resolve thinlinc to This can be done in a single DNS server. Google “split dns”