Re: Load balancing problem in w2k3
- From: Asperitas <Asperitas@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 23 Sep 2005 00:47:04 -0700
We are already running one, and it would be troublesome to use another, if
the load is balanced, everything's fine for me. I don't need all those extra
supports (we won't use them anyway).
I will try Benny's solution out, I hope it works. Thanks for the reply!
"Cláudio Rodrigues" wrote:
> Or WTSGateway Pro, by far a better option than Microsoft NLB and the ONLY
> resource based load balancer for Terminal Services. Now coming with
> SSL/HTTPS support, hopefully next week. :-)
>
> --
>
> Cláudio Rodrigues
>
> Microsoft MVP
> Windows Server - Terminal Services
> http://www.terminal-services.NET, a 2X Company.
> http://www.2x.com
> "Benny Tritsch" <bt@xxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:O173fy0vFHA.1256@xxxxxxxxxxxxxxxxxxxxxxx
> >I guess you are using NLBS (Network Load Balancing Services) for you TS
> >load
> > balancing. The configuration of NLBS can be done by the Network Load
> > Balancing Manager, which is found under the Start | Administrative Tools
> > menu group and is used to establish and enable a Network Load Balancing
> > Service (NLBS) cluster. If the configuration is to be done without the
> > Network Load Balancing Manager, the properties of the Internet protocol
> > (TCP/IP) are modified manually for the network adapter of each terminal
> > server under Start | Control Panel | Network connections | LAN
> > connections.
> > Additionally, the Network Load Balancing Service for the network adapter
> > must be enabled and properly configured. This must include the cluster
> > parameters such as virtual IP address, subnet mask, Internet name, host
> > parameters, and port rules.
> >
> > The port rules in a Network Load Balancing Service cluster determine
> > values
> > for affinity and load weight within the filtering mode. Using the Single
> > or
> > Class C affinity options for multiple hosts, you can determine a rule
> > requiring multiple requests of a particular client IP address to be always
> > redirected to the same server in a cluster. Obviously, this makes sense
> > for
> > Web servers, but is not very useful for terminal servers. With terminal
> > servers, the None option with regard to affinity should be used to select
> > the server experiencing the lightest load. I guess that you didn't change
> > the default value of the affinity from Single to None, which explains the
> > behaviour you describe.
> >
> > IMPORTANT: Load with respect to NLBS means load of the network adapter and
> > NOT the number of users logged in or CPU load! If you have two servers
> > with
> > different network adapters, the one with the fastest network adapter will
> > get all the users. NLBS was not specifically designed for terminal
> > servers.
> > If you want your load balancer to be aware of numbers of users, you need
> > to
> > buy additional products, such as Citrix Presentation Server.
> >
> > Hope this helps.
> >
> > Benny
> >
> > --
> > Dr. Bernhard Tritsch, WTSTEK.COM
> > Author of "Windows Server 2003 Terminal Services", Microsoft Press
> > Microsoft MVP Windows Server - Terminal Server
> >
> > "Asperitas" <Asperitas@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> > news:79710466-518A-43C0-8122-ECA66D4DB4C2@xxxxxxxxxxxxxxxx
> >> Hello, I've got a question about some load balancing problems.
> >>
> >> SITUATION:
> >> At my work we use load balancing with two terminal servers, however I
> > think
> >> there's something wrong with it. When someone logs in for the very first
> >> time, it will be send to either ts1 or ts2 (depends on the loads,
> > ofcourse).
> >> But from now on this person is stuck on that server, when she logs in
> > again
> >> she will also be sent to the terminal server she logged in at at the
> >> first
> >> time. When I turn that terminal server off (with every user offline), and
> > she
> >> wants to log in again, she will get errors in stead of being redirected
> >> to
> >> the other terminal server. You can forcefully let her log in on the other
> > ts,
> >> but when she logs out again, it will always try to log her in at her
> > original
> >> terminal server.
> >>
> >> QUESTION:
> >> Now here is my question: how can I make load balancing actually load
> >> balances, at that moment (so if there are 12 users in TS1, and 10 in TS1,
> > the
> >> next user will log in at TS1, no matter on which TS he/she logged in at
> >> at
> >> first.
> >> Yesterday I did that chat session with microsoft and I got the answer to
> >> look here, and he also said: "It might be a problem with the NLB setup".
> > But
> >> I don't have an idea what that is (something with Load Balancing I guess)
> >
> >
>
>
>
.
- References:
- Re: Load balancing problem in w2k3
- From: Cláudio Rodrigues
- Re: Load balancing problem in w2k3
- Prev by Date: Re: Event ID 1219 logging into terminal server
- Next by Date: Re: 1920x1200 resolution?
- Previous by thread: Re: Load balancing problem in w2k3
- Next by thread: The terminal server has exceeded ...
- Index(es):
Relevant Pages
|
