That is the case with some Linux clients for example. The issue here is simple: Session Directory uses some sort of token to pass information back to the load balancer and/or RDP client therefore if your load balancer and/or RDP client does not know what to do with this token, reconnection will not work.
Limited to 32 servers (NLB limitation).You can have Session Directory with other load balancers – more in the following sections). Unpredictable behaviour (as in this example NLB is part of the whole deal note NLB is NOT required.Requires Windows 2003 Enterprise ($$$$).This means if your connection drops and you try to reconnect, the load balancing solution will check this database and find where you were and will then reconnect you back to the right server. It is basically a service that maintains a database with information regarding your users and on which TS they are working, updated at the time a new connection is made to any TS. And what is it? I am not going to explain it in detail (if you want that explanation, read it here) but will give you a good overview of it. First of all, Session Directory is only available on Windows 2003 Server Enterprise Edition and up (so you must pay the extra bucks to get it).
Now that you know what NLB means and how it works, it is time to add another Microsoft tool to the picture: Session Directory. Microsoft Network Load Balancing (NLB) with Session Directory If you missed the previous article in this series please read Load Balancing Terminal Services: All you wanted to know but were afraid to ask (Part 1).
0 kommentar(er)
