Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

CSS Terminal Services load balancing


I have configured load-balancing for terminal services running on windows servers. All works fine, but sometimes (ones per 1-3 days) is session to terminal server dropped. tcpdump shows reason - communication to client is coming not from VIP address, but from real server address (in other words: session is running 2, or 5 hours and suddenly is session dropped, because tcp issue and load-balanced to other server). Real server is operational during this issue.

here is a configuration:

server side:

client side:

(the same config for other services)

service trkat-tsapp7

port 3389

protocol tcp

keepalive type tcp

keepalive frequency 30

ip address


content trkat-tsapp

vip address

protocol tcp

port 3389

sticky-inact-timeout 660

advanced-balance sticky-srcip

add service trkat-tsapp7

add service trkat-tsapp6

add service trkat-tsapp5

add service trkat-tsapp4

add service trkat-tsapp3


clients are remote office workers, therefore sticky time 660min. tcp session is handshakes only ones by connecting client to terminal server and sticky timer is initiated. customer requires connecting to the same server after network connectivity problem.

There are around 20-100 users per real server.

I think this configuration is ok. Or it's well know problem with terminal services load balancing?


  • Application Networking

Re: CSS Terminal Services load balancing

You should remove the 'application ssl' and 'advanced-balance ssl' command from your content rule.

With these commands you will reduce the performance of the CSS and they are useless anyway.

The CSS will reestablish a session with the new server, but since the server does not know this client it does request a new login. They would need to have some inter-servers synchronization for this to work and this is not very common.

This widget could not be displayed.